Never lose a domain to a missed renewal.
Domains expire because a card lapsed or a registrar email went to a dead inbox. UptimeStatus reads the WHOIS record and warns you weeks ahead.
Companies have vanished over a renewal email.
Domains lapse for boring reasons: the card on file expired, the renewal notice went to an inbox nobody reads, auto-renew got switched off during a registrar transfer. By the time customers see a parking page, you are deep in redemption-fee territory.
UptimeStatus looks up the WHOIS record for your domain, stores the registrar and expiry date, and counts down so the renewal is never a surprise.
Warnings at 30, 14, 7, and 1 day out.
The countdown escalates as the date approaches, spaced closely enough that a broken auto-renewal cannot slip through a vacation week.
If the registration expires anyway, an incident opens immediately with how many days ago it lapsed, because at that point every hour matters.
What domain monitoring includes.
- WHOIS expiry tracking the registry expiry date, registrar, and registration date stored on every check.
- Warnings at 30, 14, 7, and 1 day a warning notification goes to the monitor's channels at each threshold, once per crossing, before the registration lapses.
- Incident on expiry an expired registration opens an incident that says exactly how many days ago it lapsed.
- Subdomain aware point a monitor at app.yourcompany.com and the check runs WHOIS against yourcompany.com, the registrable domain.
- Messy WHOIS handled field names differ by registrar and TLD, so the parser checks the common variants instead of assuming one format.
- Registry quirks included even the malformed timestamps some registries emit for .com and .net parse correctly.
One call per domain.
A domain monitor takes a bare hostname or a full URL, your choice. Create one for every domain your company owns, including the defensive registrations everyone forgets about.
Everything in the dashboard sits on the same API, so anything you can click, you can automate.
curl -X POST https://uptime-status.org/api/monitors \ -H 'Content-Type: application/json' \ -d '{ "name": "Company domain", "url": "yourcompany.com", "type": "domain" }'
Open source, MIT licensed.
The WHOIS check, quirky timestamp parsing and all, is a small readable job in the repo. Use the hosted version, or self-host the same code with no feature gates.
Domain monitoring, answered.
I have auto-renew on. Why monitor this?
Auto-renew fails silently: the card on file expires, a registrar transfer resets settings, renewal notices go to an inbox nobody reads anymore. The monitor is the backstop that does not depend on your registrar reaching you.
Which domains and TLDs are supported?
Any domain whose registry publishes an expiry date over WHOIS, which covers the common TLDs. Field names vary wildly between registries, so the parser checks the usual variants. If no expiry date can be found, the check records nothing rather than guessing.
Can I monitor a subdomain or a full URL?
Yes, point the monitor at whatever you have. WHOIS operates on registrations, not hostnames, so the check extracts the registrable domain: app.yourcompany.com becomes yourcompany.com, and that is what gets tracked.
How often should this check run?
Registration dates change rarely and WHOIS servers rate limit aggressively, so a relaxed interval is the right call. Save the tight intervals for your uptime checks.
What do I get warned about, and when?
A warning notification reaches the channels attached to the monitor at 30, 14, 7, and 1 day before expiry, once per threshold, then an incident opens the moment the registration has actually lapsed. The registrar and registration date are stored too, so the dashboard shows the whole picture, not just a countdown.
Pairs well with.
SSL monitoring
Certificate expiry countdowns, fingerprint change detection, and incidents when a handshake fails.
Learn moreDNS monitoring
Snapshots A, AAAA, MX, TXT, NS, and CAA records on every check and opens an incident when they change.
Learn moreUptime monitoring
Checks as often as every 30 seconds from six regions, with full diagnostics on every failure.
Learn moreStart monitoring in under 2 minutes.
No credit card required for the self-hosted, open-source version.