Domain Expiration Monitoring and Domain Expiry Alerts for Every Domain You Run
A lapsed domain takes down your website, your email and every API that uses it, all at once. UptimeHub reads the registry record for each domain and warns you while renewal is still a two minute job.
Checked from regions with auto-retry. No single-location false alarms.
All systems operational. Steady pulse across every region.
api.example.com returned no response from all 2 regions. Auto-retry confirmed the outage, then we alerted your team.
api.example.com is back up. The incident is logged to your status page history automatically.
90-day uptime · branded · your domain
Live demo · drive it, no signup needed
In short
Domain expiration monitoring watches the registration end date of your domain names and alerts you before the registry lets them lapse. UptimeHub looks up the expiry date of each domain from the registry itself over RDAP, refreshes it at least every 12 hours, and raises an alert when a domain is within 14 days of expiring, already expired, or no longer registered. Alerts go to Slack, email, SMS or webhook. It is a read-only check from outside your accounts, so it works even when the person who bought the domain left the company years ago and the registrar reminders go to a dead inbox.
What you get
Domain expiration monitoring for developers, SaaS teams and agencies
Reads the registry, not the registrar
The expiry date comes from the registry record for the domain, so it stays correct even if the registrar emails never reach anyone.
Alerts 14 days ahead
A domain inside 14 days of expiry raises an alert, and an expired or unregistered domain raises one immediately.
Covers the whole portfolio
Add every domain, including the parked, redirect and legacy ones nobody remembers, and see all expiry dates in one list.
Same alerts as uptime
Domain alerts use the Slack, email, SMS and webhook channels you already set up for your website checks.
How it works
From URL to alert in four steps
Add the domain
Create a domain expiry monitor and enter the domain name. Subdomains are reduced to the registrable domain automatically.
We read the registry
UptimeHub looks up the expiration date from the registry and refreshes it at least every 12 hours.
Get the warning
Inside 14 days of expiry, or if the domain is already lapsed or unregistered, an alert goes to your chosen channels.
Renew and see it clear
Once the registrar extends the term, the new date shows up on the next lookup and the monitor returns to healthy.
On this page
What actually happens after a domain expires
People imagine a domain expiring as a switch that flips off on the date. In practice there is a sequence, and knowing it explains why an alert 14 days ahead matters. The exact lengths vary by registrar and extension, so treat the middle column as typical for generic domains such as .com, not a promise.
| Stage | Typical length | What you see | What it costs to fix |
|---|---|---|---|
| Before expiry | Up to the end date | Everything works | The normal renewal price |
| Registrar grace period | 0 to 45 days, set by the registrar | Site and email often stop, or show a parking page | Usually the renewal price, sometimes plus a late fee |
| Redemption period | About 30 days | Domain is held, not resolving | A redemption fee that is often many times the renewal price |
| Pending delete | About 5 days | Domain cannot be recovered | Nothing can be done |
| Released | After that | Anyone can register it | You may have to buy it back from a new owner |
The expensive stages are the late ones, and the cheap fix is the first one. A warning 14 days before the end date sits entirely inside the cheap window. For the rules that apply to your own extension, read the registry documentation, and see ICANN's explanation of how RDAP registration data is published, which is the source UptimeHub reads.
A worked example with a portfolio of 40 domains
Take an agency that manages websites for clients and holds 40 domains across three registrars. Say 30 are on auto-renew with a company card, 6 were bought by freelancers who have since left, and 4 are old campaign domains that still redirect to live pages. Renewal reminders for the 6 go to inboxes that no longer exist. The 4 campaign domains are on a card that expired last spring.
Without monitoring, the first sign of trouble is a client calling to say the site is down and email bounces. By then the domain is in its grace period, and getting it back means finding who owns the registrar account. With a domain expiry monitor on all 40, the 10 risky ones show an alert 14 days ahead. Someone updates the card or transfers the name, and nobody outside the team ever knows there was a problem.
The same list also answers a question that is surprisingly hard to answer otherwise: which domains do we hold, and when does each one end. Agencies running client work can pair this with the agency monitoring setup, so domain, uptime and certificate alerts for one client land in one place.
Why registrar reminders are not enough
Every registrar sends expiry emails, and that is exactly the weakness. The email goes to the contact address on the domain, which is often a personal address of whoever registered it, an old company mailbox, or a privacy forwarding address that nobody reads. It is also one sender among hundreds of automated messages and tends to land in spam or in a shared inbox where each person assumes someone else handled it.
An external monitor fixes three separate problems. It does not depend on the contact address, because it reads the public registry record. It alerts the on-call channel your team already watches, not an inbox. And it also checks that the domain is still registered at all, so a domain that has been deleted and released raises an alert instead of silently resolving to nothing. If you also send renewal notices to clients on a timer, a scheduling tool such as schedulesend.com can deliver those by email, SMS or WhatsApp at the right moment, while the monitor keeps watching the expiry date itself.
Domain expiry, DNS and certificates are three separate clocks
A site can go dark for three unrelated expiry reasons, and each has its own owner. The domain registration ends at the registrar. The TLS certificate ends at the certificate authority, a clock that is getting shorter, as covered in our breakdown of the new certificate lifetimes. The DNS records themselves can be edited or deleted at any time by anyone with access to the zone.
Watching only one leaves the other two open. Domain expiry monitoring pairs naturally with SSL certificate monitoring and DNS record monitoring, and with ordinary uptime checks that confirm the site actually answers. Domain expiry checks are included on the Pro plan and above, and you can compare plans on the pricing page. If you want to read a certificate on a specific host right now, the free SSL certificate checker does that in a few seconds.
What to set up so a domain never lapses silently
Start with a complete list. Add every domain you own, not only the production ones, because the forgotten domain that redirects traffic or carries an old email address is the one that lapses. Send domain alerts to a channel with an owner, ideally the same one that receives your downtime alerts, so the warning is not competing with a quiet inbox. Check the alert channels and make sure at least two people can act on a domain alert, since renewing needs access to the registrar account.
Then keep auto-renew on and treat the monitor as the independent check on it. If the monitor alerts, auto-renew failed, and the cause is nearly always a card or an account contact. Fixing that cause once usually fixes it for every domain on the same account. For a comparison of what other tools bundle for certificate and domain checks, see our review of SSL certificate monitoring tools, and if you currently run Zabbix, Nagios or PRTG, read the self-run script versus hosted monitor comparison.
FAQ
Questions buyers ask about Domain expiration monitoring
It is an automated check of the date your domain registration ends, with an alert before that date arrives. It reads the expiry from the registry, so it does not depend on registrar emails reaching a person. The point is to turn a silent, calendar-driven failure into a notification someone sees weeks ahead of time.
Add the domain as a domain expiry monitor and choose your alert channels. UptimeHub reads the registry expiry date and alerts you when the domain is within 14 days of expiring, then again if it actually lapses. Renewing at the registrar clears the alert automatically on the next lookup.
The website, email and any API on that domain stop resolving, usually within hours to days. Most registrars then hold the name for a grace period and a redemption period during which recovery is possible but often costs a redemption fee. After that the name is released and anyone can register it.
No. Auto-renew fails when the card on file expires, the payment is declined, the account owner changed, or the registrar flags a verification problem. Monitoring is the independent check that tells you the renewal did not happen, while there is still time to fix it by hand.
Domains whose registry publishes expiry dates over RDAP are supported, which covers the large majority of common extensions. A few country registries do not publish expiry dates in RDAP. For those, UptimeHub tells you the date cannot be read rather than showing a number it cannot verify.
Yes. A certificate expires on its own date and is renewed with a certificate authority, while the domain registration is renewed at a registrar. Both can take a site down, and they are owned by different accounts, which is why they are monitored separately.
More monitor types
Start monitoring in two minutes
Add a URL or endpoint and UptimeHub checks it every minute from 2 regions, alerts you in seconds, and updates your branded status page. Read-only checks that never touch your servers.