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