Website Uptime Monitor
Monitor website availability and server information for any domain
mplay13.cc
Uptime & Server Information
Current Status
Historical Data
| Date | Status | Server |
|---|---|---|
| 7/28/2026, 1:20:10 PM | Active | nginx/1.24.0 (Ubuntu) |
| 7/13/2026, 10:43:02 PM | Active | nginx/1.24.0 (Ubuntu) |
| 6/28/2026, 1:59:27 PM | Active | nginx/1.24.0 (Ubuntu) |
| 6/12/2026, 4:02:17 PM | Active | nginx/1.24.0 (Ubuntu) |
| 6/11/2026, 2:11:12 AM | Active | nginx/1.24.0 (Ubuntu) |
| 6/9/2026, 3:27:56 PM | Active | nginx/1.24.0 (Ubuntu) |
| 6/7/2026, 11:10:55 PM | Active | nginx/1.24.0 (Ubuntu) |
| 5/16/2026, 8:34:06 AM | Inactive | Unknown |
| 5/10/2026, 7:24:12 AM | Active | nginx/1.24.0 (Ubuntu) |
| 5/3/2026, 4:03:41 PM | Active | nginx/1.24.0 (Ubuntu) |
| 4/30/2026, 6:42:59 PM | Active | nginx/1.24.0 (Ubuntu) |
| 4/26/2026, 11:44:49 AM | Active | nginx/1.18.0 (Ubuntu) |
| 4/25/2026, 4:21:08 AM | Active | nginx/1.18.0 (Ubuntu) |
| 4/19/2026, 8:20:51 PM | Active | nginx/1.18.0 (Ubuntu) |
| 4/17/2026, 9:17:17 PM | Active | nginx/1.18.0 (Ubuntu) |
| 4/15/2026, 5:26:48 PM | Active | nginx/1.18.0 (Ubuntu) |
| 4/10/2026, 4:01:58 PM | Inactive | Unknown |
| 4/8/2026, 5:33:42 AM | Active | nginx/1.18.0 (Ubuntu) |
| 4/5/2026, 11:29:55 AM | Inactive | Unknown |
| 4/2/2026, 2:15:02 PM | Inactive | Unknown |
| 3/30/2026, 4:55:18 PM | Inactive | Unknown |
| 3/27/2026, 11:48:39 AM | Active | nginx/1.18.0 (Ubuntu) |
| 3/17/2026, 8:30:31 PM | Active | nginx/1.18.0 (Ubuntu) |
| 3/9/2026, 7:19:23 AM | Inactive | Unknown |
| 2/27/2026, 1:57:23 AM | Active | nginx/1.18.0 (Ubuntu) |
| 2/22/2026, 5:22:19 AM | Active | nginx/1.18.0 (Ubuntu) |
| 2/20/2026, 3:49:36 PM | Active | nginx/1.18.0 (Ubuntu) |
| 2/19/2026, 11:34:49 AM | Inactive | Unknown |
| 2/18/2026, 5:19:48 AM | Inactive | Unknown |
| 2/16/2026, 12:18:30 PM | Inactive | Unknown |
| 2/14/2026, 3:09:28 PM | Inactive | Unknown |
| 2/12/2026, 12:15:07 PM | Inactive | Unknown |
| 2/8/2026, 6:00:23 AM | Inactive | Unknown |
| 2/5/2026, 9:54:33 PM | Inactive | Unknown |
| 2/4/2026, 12:14:11 PM | Active | nginx/1.18.0 (Ubuntu) |
| 1/31/2026, 12:06:30 PM | Inactive | Unknown |
| 1/24/2026, 9:03:38 PM | Inactive | Unknown |
| 1/23/2026, 2:41:44 PM | Inactive | Unknown |
| 1/18/2026, 1:51:39 PM | Active | nginx/1.18.0 (Ubuntu) |
| 1/16/2026, 10:41:59 AM | Inactive | Unknown |
| 1/15/2026, 12:38:16 AM | Inactive | Unknown |
| 1/13/2026, 1:49:40 PM | Inactive | Unknown |
| 1/11/2026, 6:47:36 PM | Inactive | Unknown |
| 1/10/2026, 12:47:03 PM | Inactive | Unknown |
| 1/9/2026, 11:04:06 AM | Inactive | Unknown |
| 1/5/2026, 11:04:27 AM | Inactive | Unknown |
| 12/28/2025, 11:03:33 AM | Inactive | Unknown |
| 12/26/2025, 11:59:53 PM | Inactive | Unknown |
| 12/25/2025, 1:58:24 AM | Inactive | Unknown |
| 12/19/2025, 5:58:45 PM | Inactive | Unknown |
| 12/17/2025, 10:43:18 AM | Inactive | Unknown |
| 12/12/2025, 3:25:56 PM | Active | nginx/1.18.0 (Ubuntu) |
| 12/7/2025, 12:06:17 PM | Inactive | Unknown |
| 12/5/2025, 1:25:15 PM | Active | nginx/1.18.0 (Ubuntu) |
| 11/20/2025, 8:41:04 PM | Active | nginx/1.18.0 (Ubuntu) |
| 11/15/2025, 1:46:05 PM | Active | nginx/1.18.0 (Ubuntu) |
| 11/12/2025, 9:18:46 PM | Inactive | Unknown |
| 10/31/2025, 7:28:02 PM | Inactive | Unknown |
| 10/23/2025, 6:05:11 PM | Active | nginx/1.18.0 (Ubuntu) |
| 10/19/2025, 12:58:02 PM | Active | nginx/1.18.0 (Ubuntu) |
| 10/18/2025, 5:53:26 AM | Active | nginx/1.18.0 (Ubuntu) |
| 10/16/2025, 9:23:44 AM | Active | nginx/1.18.0 (Ubuntu) |
| 10/14/2025, 1:28:55 AM | Active | nginx/1.18.0 (Ubuntu) |
| 9/29/2025, 1:10:21 PM | Active | nginx/1.18.0 (Ubuntu) |
| 9/28/2025, 9:55:15 AM | Active | nginx/1.18.0 (Ubuntu) |
| 9/22/2025, 1:50:54 PM | Active | nginx/1.18.0 (Ubuntu) |
| 9/9/2025, 6:39:57 AM | Inactive | Unknown |
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.
Metrics we monitor
- Uptime percentage: The percentage of time your website is accessible
- Response time: How quickly your server responds to requests
- Status codes: HTTP response codes indicating server status
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.