Website Uptime Monitor
Monitor website availability and server information for any domain
0x0f.info
Uptime & Server Information
Current Status
Observed Changes
| Date | Status | Server |
|---|---|---|
| 9/23/2026, 2:37:17 AM | Active | Apache/2.4.62 (Debian) |
| 9/21/2026, 2:27:40 AM | Inactive | Unknown |
| 8/15/2026, 4:24:18 AM | Active | Apache/2.4.62 (Debian) |
| 7/15/2026, 7:04:18 AM | Active | Apache/2.4.62 (Debian) |
| 7/5/2026, 11:14:43 AM | Active | Apache/2.4.62 (Debian) |
| 7/2/2026, 4:59:30 AM | Active | Apache/2.4.62 (Debian) |
| 6/30/2026, 7:29:19 AM | Active | Apache/2.4.62 (Debian) |
| 6/28/2026, 2:07:12 PM | Active | Apache/2.4.62 (Debian) |
| 6/20/2026, 11:50:18 AM | Active | Apache/2.4.62 (Debian) |
| 6/15/2026, 4:43:09 PM | Active | Apache/2.4.62 (Debian) |
| 6/12/2026, 2:08:19 AM | Active | Apache/2.4.62 (Debian) |
| 6/9/2026, 3:04:08 AM | Active | Apache/2.4.62 (Debian) |
| 6/7/2026, 4:35:16 AM | Active | Apache/2.4.62 (Debian) |
| 5/31/2026, 1:38:42 AM | Active | Apache/2.4.62 (Debian) |
| 5/29/2026, 12:20:18 PM | Active | Apache/2.4.62 (Debian) |
| 5/28/2026, 9:17:14 AM | Active | Apache/2.4.62 (Debian) |
| 5/22/2026, 9:11:03 PM | Active | Apache/2.4.62 (Debian) |
| 5/19/2026, 6:45:27 PM | Active | Apache/2.4.62 (Debian) |
| 5/18/2026, 2:32:36 AM | Active | Apache/2.4.62 (Debian) |
| 5/12/2026, 1:11:40 AM | Active | Apache/2.4.62 (Debian) |
| 5/5/2026, 10:36:29 PM | Active | Apache/2.4.62 (Debian) |
| 4/30/2026, 2:23:33 PM | Active | Apache/2.4.62 (Debian) |
| 4/29/2026, 2:50:48 AM | Active | Apache/2.4.62 (Debian) |
| 4/21/2026, 8:35:06 PM | Active | Apache/2.4.62 (Debian) |
| 4/18/2026, 8:36:31 PM | Active | Apache/2.4.62 (Debian) |
| 3/27/2026, 6:27:43 PM | Active | Apache/2.4.62 (Debian) |
| 3/20/2026, 5:20:44 PM | Active | Apache/2.4.62 (Debian) |
| 3/17/2026, 5:12:16 PM | Inactive | Unknown |
| 3/13/2026, 3:21:24 AM | Inactive | Unknown |
| 2/27/2026, 12:53:07 AM | Active | Apache/2.4.62 (Debian) |
| 2/21/2026, 1:48:00 PM | Active | Apache/2.4.62 (Debian) |
| 2/11/2026, 6:49:29 PM | Inactive | Unknown |
| 1/24/2026, 5:52:21 AM | Active | Apache/2.4.62 (Debian) |
| 1/19/2026, 12:15:07 AM | Inactive | Unknown |
| 1/16/2026, 8:08:30 AM | Active | Apache/2.4.62 (Debian) |
| 1/13/2026, 3:54:00 PM | Inactive | Unknown |
| 1/7/2026, 1:52:57 PM | Inactive | Unknown |
| 1/2/2026, 5:28:54 PM | Inactive | Unknown |
| 12/29/2025, 2:56:47 AM | Inactive | Unknown |
| 12/21/2025, 11:49:08 PM | Inactive | Unknown |
| 12/15/2025, 4:23:43 AM | Inactive | Unknown |
| 12/9/2025, 4:21:15 AM | Active | Apache/2.4.62 (Debian) |
| 12/2/2025, 7:10:29 AM | Active | Apache/2.4.62 (Debian) |
| 11/30/2025, 4:23:20 AM | Active | Apache/2.4.62 (Debian) |
| 11/18/2025, 8:30:17 PM | Active | Apache/2.4.62 (Debian) |
| 11/6/2025, 4:38:10 PM | Active | Apache/2.4.62 (Debian) |
| 11/4/2025, 11:13:04 PM | Active | Apache/2.4.62 (Debian) |
| 10/17/2025, 10:53:03 PM | Active | Apache/2.4.62 (Debian) |
| 10/8/2025, 9:13:39 AM | Active | Apache/2.4.62 (Debian) |
| 10/2/2025, 6:51:02 PM | Active | Apache/2.4.62 (Debian) |
| 10/1/2025, 7:21:19 AM | Active | Apache/2.4.62 (Debian) |
| 9/30/2025, 1:33:16 AM | Active | Apache/2.4.62 (Debian) |
| 9/18/2025, 3:17:46 PM | Active | Apache/2.4.62 (Debian) |
| 8/23/2025, 7:23:49 PM | Active | Apache/2.4.62 (Debian) |
| 8/5/2025, 1:01:31 PM | Active | Apache/2.4.62 (Debian) |
| 7/24/2025, 3:48:49 PM | Active | Apache/2.4.62 (Debian) |
| 7/13/2025, 1:27:15 AM | Active | Apache/2.4.62 (Debian) |
| 7/3/2025, 8:36:57 PM | Active | Apache/2.4.56 (Debian) |
| 6/3/2025, 12:31:05 PM | Active | Apache/2.4.56 (Debian) |
| 6/2/2025, 7:32:39 AM | Active | Apache/2.4.56 (Debian) |
| 5/2/2025, 4:05:20 AM | Active | Apache/2.4.56 (Debian) |
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.