Website Uptime Monitor
Monitor website availability and server information for any domain
2046.bio
Uptime & Server Information
Current Status
Observed Changes
| Date | Status | Server |
|---|---|---|
| 9/21/2026, 9:39:15 PM | Inactive | Unknown |
| 8/31/2026, 2:32:32 AM | Active | nginx/1.24.0 (Ubuntu) |
| 8/16/2026, 1:22:50 AM | Active | nginx/1.24.0 (Ubuntu) |
| 8/8/2026, 9:36:29 PM | Active | nginx/1.24.0 (Ubuntu) |
| 7/17/2026, 2:47:36 PM | Active | nginx/1.24.0 (Ubuntu) |
| 6/26/2026, 10:35:40 AM | Active | nginx/1.24.0 (Ubuntu) |
| 5/28/2026, 1:51:32 AM | Active | nginx/1.24.0 (Ubuntu) |
| 5/24/2026, 5:27:50 PM | Active | nginx/1.24.0 (Ubuntu) |
| 5/23/2026, 3:40:53 AM | Active | nginx/1.24.0 (Ubuntu) |
| 5/17/2026, 8:52:29 PM | Active | nginx/1.24.0 (Ubuntu) |
| 4/27/2026, 12:38:28 AM | Active | nginx/1.24.0 (Ubuntu) |
| 4/12/2026, 3:41:49 PM | Active | nginx/1.24.0 (Ubuntu) |
| 4/8/2026, 6:15:50 PM | Active | nginx/1.24.0 (Ubuntu) |
| 4/6/2026, 5:16:26 PM | Active | nginx/1.24.0 (Ubuntu) |
| 3/31/2026, 2:26:37 PM | Active | nginx/1.24.0 (Ubuntu) |
| 3/28/2026, 12:37:19 PM | Active | nginx/1.24.0 (Ubuntu) |
| 3/25/2026, 4:57:46 AM | Active | nginx/1.24.0 (Ubuntu) |
| 3/20/2026, 12:01:29 AM | Active | nginx/1.24.0 (Ubuntu) |
| 3/18/2026, 3:43:15 PM | Active | nginx/1.24.0 (Ubuntu) |
| 3/14/2026, 12:14:59 AM | Active | nginx/1.24.0 (Ubuntu) |
| 3/11/2026, 6:25:46 PM | Active | nginx/1.24.0 (Ubuntu) |
| 2/14/2026, 5:25:10 PM | Inactive | Unknown |
| 2/7/2026, 10:05:33 AM | Inactive | Unknown |
| 2/3/2026, 3:22:47 AM | Active | nginx/1.24.0 (Ubuntu) |
| 1/19/2026, 10:08:42 PM | Inactive | Unknown |
| 1/13/2026, 6:58:56 AM | Inactive | Unknown |
| 1/12/2026, 2:20:37 AM | Inactive | Unknown |
| 1/7/2026, 11:35:27 AM | Inactive | Unknown |
| 1/5/2026, 2:58:37 PM | Inactive | Unknown |
| 12/31/2025, 2:25:38 PM | Inactive | Unknown |
| 12/30/2025, 12:46:45 PM | Inactive | Unknown |
| 12/24/2025, 12:04:39 AM | Inactive | Unknown |
| 12/19/2025, 1:15:45 AM | Inactive | Unknown |
| 12/18/2025, 1:04:25 AM | Inactive | Unknown |
| 12/9/2025, 11:20:24 PM | Inactive | Unknown |
| 12/7/2025, 3:26:39 PM | Inactive | Unknown |
| 12/2/2025, 10:02:33 AM | Active | nginx/1.18.0 (Ubuntu) |
| 11/27/2025, 7:35:25 PM | Active | nginx/1.18.0 (Ubuntu) |
| 11/15/2025, 1:37:04 AM | Active | nginx/1.18.0 (Ubuntu) |
| 11/8/2025, 1:53:08 PM | Active | nginx/1.18.0 (Ubuntu) |
| 11/6/2025, 8:01:36 PM | Inactive | Unknown |
| 11/5/2025, 2:11:03 PM | Active | nginx/1.18.0 (Ubuntu) |
| 11/2/2025, 11:25:48 PM | Active | nginx/1.18.0 (Ubuntu) |
| 11/1/2025, 7:40:57 PM | Active | nginx/1.18.0 (Ubuntu) |
| 10/23/2025, 10:48:30 AM | Active | nginx/1.18.0 (Ubuntu) |
| 10/13/2025, 7:02:19 AM | Active | nginx/1.18.0 (Ubuntu) |
| 9/27/2025, 9:25:17 PM | Active | nginx/1.18.0 (Ubuntu) |
| 9/19/2025, 1:14:33 AM | Active | nginx/1.18.0 (Ubuntu) |
| 8/30/2025, 12:55:00 PM | Inactive | Unknown |
| 8/19/2025, 5:53:35 PM | Active | nginx/1.18.0 (Ubuntu) |
| 8/17/2025, 3:08:01 AM | Active | nginx/1.18.0 (Ubuntu) |
| 7/28/2025, 5:17:44 AM | Inactive | Unknown |
| 7/11/2025, 12:09:07 PM | Active | nginx/1.18.0 (Ubuntu) |
| 7/4/2025, 10:31:19 PM | Active | nginx/1.18.0 (Ubuntu) |
| 7/3/2025, 9:17:19 PM | Active | nginx/1.18.0 (Ubuntu) |
| 6/30/2025, 8:18:13 PM | Active | nginx/1.18.0 (Ubuntu) |
| 6/20/2025, 12:54:21 PM | Inactive | Unknown |
| 6/13/2025, 4:11:57 PM | Active | nginx/1.18.0 (Ubuntu) |
| 6/5/2025, 10:10:24 PM | Active | nginx/1.18.0 (Ubuntu) |
| 5/7/2025, 1:44:45 AM | Active | nginx/1.18.0 (Ubuntu) |
| 5/2/2025, 2:34:58 PM | Active | nginx/1.18.0 (Ubuntu) |
| 3/24/2025, 12:33:08 AM | Active | nginx/1.18.0 (Ubuntu) |
| 2/1/2025, 12:24:20 AM | Active | nginx/1.18.0 (Ubuntu) |
Don't just check uptime once — watch it 24/7
This is a one-time check. Turn on monitoring and we'll watch the domains that matter to you continuously, notifying you the moment anything moves across all three signals:
Uptime
We visit the site from multiple regions worldwide and email you within minutes if it goes down, with a per-region breakdown so a real outage stands out from a regional blip.
DNS changes
We watch NS, MX, CAA, DNSSEC, CNAME and A/AAAA records, and identify the host, network, and ASN behind them, so a real migration or hijack stands out from routine noise.
TLS certificate
We warn you 30, 14, 7, and 1 days before it expires, and flag it if the issuing authority changes or the certificate is unexpectedly replaced.
Free for your first domain: uptime, DNS, and certificate together. No credit card.
About Website Uptime Monitoring
Use the Who.is uptime information to track the availability and server information of websites. This helps track:
- Website availability and response status
- Server software and configuration
- Meta information including titles and descriptions
- Historical uptime patterns
This information is valuable for website owners, system administrators, and anyone interested in monitoring website reliability and performance.
What this page reports
- Last status change: When we last saw a site switch between reachable and unreachable
- Last downtime: When a site was most recently seen down, and whether it has come back
- Server and meta information: The server software, page title and meta tags we last observed
We check a domain at most once a day and record an observation only when something changes, so these are the times a change was seen rather than the exact moment it happened. For continuous, minute-by-minute checks with alerting, use website monitoring.
Disclaimer: Who.is is not affiliated with, endorsed by, or connected to any of the domains displayed on this page. We provide this information as a public service for informational purposes only.