Website Uptime Monitor
Monitor website availability and server information for any domain
00000000000000000000000000000000000000000000000000000000.org
Uptime & Server Information
Current Status
Observed Changes
| Date | Status | Server |
|---|---|---|
| 9/2/2026, 8:43:53 AM | Active | Apache/2.4.68 (Unix) |
| 8/27/2026, 4:51:48 AM | Active | Apache/2.4.68 (Unix) |
| 8/16/2026, 1:49:56 PM | Active | Apache/2.4.68 (Unix) |
| 8/14/2026, 6:54:22 AM | Active | Apache/2.4.68 (Unix) |
| 7/8/2026, 2:06:30 AM | Active | Apache/2.4.68 (Unix) |
| 6/25/2026, 3:09:56 AM | Active | Apache/2.4.68 (Unix) |
| 6/1/2026, 2:47:35 AM | Active | Apache/2.4.67 (Unix) |
| 5/21/2026, 3:44:21 AM | Active | Apache/2.4.67 (Unix) |
| 5/18/2026, 12:05:03 AM | Inactive | Unknown |
| 5/14/2026, 2:15:54 AM | Active | Apache/2.4.67 (Unix) |
| 5/12/2026, 7:08:04 AM | Active | Apache/2.4.67 (Unix) |
| 4/29/2026, 12:50:07 PM | Active | Apache/2.4.66 (Unix) |
| 4/25/2026, 11:42:41 AM | Active | Apache/2.4.66 (Unix) |
| 4/23/2026, 9:44:57 PM | Active | Apache/2.4.66 (Unix) |
| 4/20/2026, 9:41:54 AM | Active | Apache/2.4.66 (Unix) |
| 4/13/2026, 2:27:40 AM | Active | Apache/2.4.66 (Unix) |
| 4/7/2026, 4:34:26 AM | Active | Apache/2.4.66 (Unix) |
| 4/5/2026, 8:34:21 PM | Active | Apache/2.4.66 (Unix) |
| 3/27/2026, 9:19:12 AM | Inactive | Unknown |
| 3/9/2026, 7:36:15 PM | Active | Apache/2.4.66 (Unix) |
| 3/6/2026, 8:46:11 AM | Active | Apache/2.4.66 (Unix) |
| 2/24/2026, 9:56:02 AM | Active | Apache/2.4.66 (Unix) |
| 2/22/2026, 3:32:07 AM | Active | Apache/2.4.66 (Unix) |
| 2/13/2026, 9:20:42 AM | Inactive | Unknown |
| 1/24/2026, 10:04:06 PM | Inactive | Unknown |
| 1/20/2026, 8:35:24 AM | Inactive | Unknown |
| 1/15/2026, 6:34:47 PM | Inactive | Unknown |
| 1/15/2026, 6:34:47 PM | Inactive | Unknown |
| 1/14/2026, 4:35:04 AM | Inactive | Unknown |
| 1/14/2026, 4:35:02 AM | Inactive | Unknown |
| 1/12/2026, 3:14:06 PM | Inactive | Unknown |
| 1/11/2026, 1:37:39 PM | Inactive | Unknown |
| 1/5/2026, 3:31:45 AM | Inactive | Unknown |
| 1/1/2026, 12:06:33 AM | Inactive | Unknown |
| 12/24/2025, 10:13:25 AM | Inactive | Unknown |
| 12/21/2025, 1:59:27 PM | Inactive | Unknown |
| 12/16/2025, 8:44:27 AM | Inactive | Unknown |
| 12/8/2025, 9:12:27 PM | Active | Apache/2.4.65 (Unix) |
| 12/4/2025, 10:41:59 AM | Inactive | Unknown |
| 11/30/2025, 9:30:57 AM | Active | Apache/2.4.65 (Unix) |
| 11/27/2025, 6:12:54 AM | Active | Apache/2.4.65 (Unix) |
| 11/25/2025, 12:13:19 PM | Active | Apache/2.4.65 (Unix) |
| 11/19/2025, 5:43:39 PM | Active | Apache/2.4.65 (Unix) |
| 11/5/2025, 10:46:37 PM | Active | Apache/2.4.65 (Unix) |
| 10/27/2025, 12:56:39 AM | Active | Apache/2.4.65 (Unix) |
| 10/22/2025, 8:04:29 PM | Active | Apache/2.4.65 (Unix) |
| 10/21/2025, 7:02:44 AM | Active | Apache/2.4.65 (Unix) |
| 10/10/2025, 12:58:42 PM | Active | Apache/2.4.65 (Unix) |
| 10/1/2025, 1:08:37 AM | Active | Apache/2.4.65 (Unix) |
| 9/25/2025, 5:15:17 PM | Active | Apache/2.4.65 (Unix) |
| 9/23/2025, 6:16:11 PM | Active | Apache/2.4.65 (Unix) |
| 9/17/2025, 4:14:04 AM | Active | Apache/2.4.65 (Unix) |
| 9/10/2025, 6:27:14 AM | Active | Apache/2.4.65 (Unix) |
| 8/23/2025, 8:48:36 PM | Active | Apache/2.4.65 (Unix) |
| 7/24/2025, 5:30:47 AM | Active | Apache/2.4.64 (Unix) |
| 7/10/2025, 4:31:18 PM | Inactive | Unknown |
| 7/4/2025, 10:42:26 PM | Active | Apache/2.4.63 (Unix) |
| 7/1/2025, 6:16:27 PM | Active | Apache/2.4.63 (Unix) |
| 6/15/2025, 8:07:56 AM | Active | Apache/2.4.63 (Unix) |
| 6/10/2025, 6:24:44 PM | Active | Apache/2.4.63 (Unix) |
| 5/21/2025, 12:48:02 PM | Active | Apache/2.4.63 (Unix) |
| 5/17/2025, 2:18:54 AM | Active | Apache/2.4.63 (Unix) |
| 5/6/2025, 4:11:45 PM | Active | Apache/2.4.63 (Unix) |
| 5/5/2025, 3:40:26 PM | Active | Apache/2.4.63 (Unix) |
| 5/3/2025, 9:27:49 AM | Active | Apache/2.4.63 (Unix) |
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.