Domain Expiry: The Outage Nobody Sees Coming

Domain expiry monitoring means keeping track of the registration expiry date of every domain you are responsible for, and getting warned well before it passes. When a domain lapses, the website, the email and every DNS record under it stop working together, and getting the name back gets more expensive with each week that goes by.

Server outages at least produce an error someone investigates. An expired domain is an administrative failure that looks like a technical one, and it tends to hit long-standing clients whose registrar account nobody has logged into for years.

What happens after the expiry date

The exact timeline depends on the registrar and the extension, but for common generic TLDs such as .com the stages look like this:

Stage	Typical length	What it means for the client
Expired, auto-renew grace	Often up to 30 days or more, set by the registrar	Site and email can stop resolving; renewal usually at the normal price
Redemption grace period	30 days	Domain shows redemptionPeriod; restoring it costs a redemption fee on top of renewal
Pending delete	5 days	Status pendingDelete; it can no longer be restored
Released	n/a	Anyone can register it, including drop-catch services

Country-code domains follow their own registry rules. Nominet's .uk process, for instance, suspends and later cancels a domain on a different schedule, so do not assume the .com timeline applies to every client.

The part clients feel first is email. MX records live in the domain's DNS, so inbound mail starts bouncing at the same moment the website disappears, which often means the client cannot reach you by their usual address to report it.

How renewals get missed by people who are not careless

Almost always, the person who owns the domain and the people who maintain the website are different people. Auto-renew was on, but the card on file expired and the payment failed. The registrant contact is an employee who left, so the reminders go to a dead mailbox. For gTLDs, ICANN's expired registration rules require registrars to send reminders roughly a month and a week before expiry, but that only helps if the email address still works and the message is not filtered as bulk mail.

Migrations cause their own version. Auto-renew is switched off before a registrar transfer to avoid paying twice, and the transfer stalls. Or a previous agency registered the domain in its own account, and nobody on the client side has access.

Reading the expiry date yourself

You can check any domain from a terminal. The older way is WHOIS:

whois example.com | grep -i "expiry"

For .com this returns a line such as Registry Expiry Date: 2027-08-13T04:00:00Z. WHOIS output is free text, its format varies between registries, and contact details are now mostly redacted.

RDAP is the structured replacement. It returns JSON over HTTPS with consistent field names:

curl -s https://rdap.verisign.com/com/v1/domain/example.com

Look in the events array for the entry with "eventAction": "expiration". The same response lists the registrar under entities and the EPP status codes under status. A status such as client transfer prohibited is a normal lock. redemption period, pending delete or client hold mean the problem has already started.

Two things neither protocol shows: whether auto-renew is switched on at the registrar, and whether the payment method behind it still works. Those need a login to the registrar account, which is a good reason to find out who has one before you need it.

Putting expiry next to the rest of the site checks

Checking one domain takes a minute. Checking forty every month means a spreadsheet and a recurring reminder, which lasts until the person who owns the reminder changes jobs. Domain expiry is more reliable when it lives with the other things you already watch on each site, as covered in our website monitoring checklist for agencies.

Deltio monitors domain expiry for every site you add, alongside SSL certificate expiry, uptime, sitemap URLs and on-page SEO signals. Alerts go to Slack and email for that site, so the warning reaches the account owner rather than a registrar inbox nobody reads. It is one of the changes you did not make that still needs someone to act, and an alert that arrives in time is what makes it cheap to fix.

What monitoring cannot do is renew the domain. Somebody still needs working registrar access and a valid card, so treat the first alert as the moment to confirm both.

If you want to see expiry dates for your own client list, you can start a 14-day trial and add the domains you are least sure about first.