Home Guides Webmaster & Technical SEODomain Expiry Monitoring: Never Lose a Domain
Webmaster & Technical SEO9 minPublished 2026-03-01

Domain Expiry Monitoring: Never Lose a Domain

A domain expiring is rarely a surprise on the registrar's end — it's a surprise on yours, usually the day your site, email, and every subdomain under it stop resolving. Domain expiry monitoring closes that gap by tracking a domain's expiration date against WHOIS/RDAP records and alerting you weeks before the registrar's own reminders would.

Quick Answer
Domain expiry monitoring is the automated tracking of a domain's registration expiration date via WHOIS or RDAP lookups, with alerts sent before renewal deadlines. Most gTLDs give you a 30–45 day grace period after expiry, then a 30-day Redemption Grace Period at a much higher fee — after that, the domain is deleted and open to anyone. Check any domain's current expiry date with the WHOIS Lookup tool.

What Is Domain Expiry Monitoring?

Domain expiry monitoring is the practice of tracking a domain's registration expiration date — typically pulled from WHOIS or RDAP records — and generating alerts before that date arrives. It exists because domain renewal is opt-in and manual by default: registrars send reminder emails, but those emails bounce, land in spam, or go to an inbox that's itself hosted on the domain that's about to expire.

The mechanism is simple. A monitor queries WHOIS or RDAP for a domain on a schedule (daily is typical), parses the Registry Expiry Date field from the response, and compares it to the current date. When the remaining time crosses a threshold — commonly 30, 14, and 7 days — it fires a notification through email, SMS, or a webhook. Some monitors also track registrar and nameserver changes in the same pass, since those fields sit in the same WHOIS/RDAP record and unexpected changes there are often the first sign of a hijack or an accidental transfer.

This matters more than it looks like on paper. A domain isn't just a URL — it's the anchor for DNS records, MX records for email, SSL certificates issued against that hostname, and every subdomain built on top of it. When a domain lapses, all of that goes dark simultaneously: the website returns NXDOMAIN, inbound and outbound email stops (including the renewal notice itself, if it routes through that domain), and any SSL certificate becomes irrelevant because there's no DNS resolution to serve it over. Domain expiry monitoring is the cheapest insurance against that cascade — a single WHOIS check costs nothing, an outage costs uptime, SEO ranking, and customer trust.

Registrars are not solely responsible for catching this either. Per ICANN's Expired Registration Recovery Policy, registrars must send at least two renewal notices before expiration — one about a month out, one about a week out — plus one more notice within 5 days after expiration if the domain is deleted. Three notices sound like enough, but they all go to a single contact email, and if that address is unreachable for any reason, every notice fails silently. Independent monitoring doesn't rely on that single point of failure.

What Happens When a Domain Expires

Expiration isn't a single event — it's the start of a multi-stage timeline defined partly by RFC 3915, which specifies the EPP grace-period statuses registries use, and partly by ICANN's Expired Registration Recovery Policy (ERRP), which sets the minimum consumer protections registrars must follow for generic TLDs (.com, .net, .org, and similar).

Auto-renew grace period. Most registries auto-renew a domain on its expiry date and give the registrant a grace period — commonly 30–45 days depending on the TLD — to pay the renewal at the normal rate with no penalty. During this window the domain typically keeps resolving, though policies vary by registrar.

Redemption Grace Period (RGP). If the domain isn't renewed during the grace period, it's deleted and enters RGP. ERRP requires a minimum 30-day RGP for gTLDs. During RGP, DNS resolution is disabled — the site and any email tied to the domain go offline — and only the original registrant can restore it, at a redemption fee that's substantially higher than a normal renewal (often in the $80–$300 range depending on registrar, on top of the standard renewal cost).

Pending Delete. If RGP passes with no restoration, the domain enters a short pending-delete window (around 5 days) during which it can't be restored or registered by anyone. After that, it's released and any party — including domain-squatting services that actively monitor drops — can register it.

The practical upshot: from the moment a domain expires, you typically have 30–75 days of recoverable window depending on TLD and registrar, but every day past the initial grace period gets more expensive and every day past RGP is unrecoverable. Monitoring exists to make sure you act inside the free window, not the expensive one.

Domain Expiration Timeline Reference

StageTypical DurationDNS/Email StatusCost to Recover
Auto-renew grace period0–45 days (TLD-dependent)Usually still resolvingStandard renewal price
Redemption Grace Period (RGP)30 days (ERRP minimum for gTLDs)Disabled — site and email offlineRedemption fee (often $80–$300+) plus renewal
Pending Delete~5 daysDisabled, unrecoverable by anyoneNot recoverable
Released / AvailableN/AOpen registration — often caught by drop-catch services within minutes

Once a domain clears the Redemption Grace Period, recovery odds fall to effectively zero — the domain is released to open registration and competitively caught by automated drop-catching services within seconds of release. Everything before that line is recoverable; everything after it isn't.

How to Check a Domain's Expiry Date

The fastest way to check any domain's current expiry date, registrar, and nameservers is a direct WHOIS/RDAP query. Run one through the WHOIS Lookup tool, or from the command line:

Code
# Query WHOIS directly for expiry date, registrar, and status codes
whois example.com | grep -i "expir\|registrar\|status"
Code
# RDAP is the modern, structured replacement for WHOIS (JSON output)
curl -s "https://rdap.org/domain/example.com" | jq '.events[] | select(.eventAction=="expiration")'

Watch the status codes in the output too — clientTransferProhibited is normal, but pendingDelete or redemptionPeriod means the domain is already past expiration and running against the clock.

For checking more than a handful of domains, a small script beats repeated manual lookups:

Code
# Loop a domain list and flag anything expiring within 30 days
for d in $(cat domains.txt); do
  exp=$(whois "$d" | grep -im1 "expir" | grep -oE '[0-9]{4}-[0-9]{2}-[0-9]{2}')
  [ -n "$exp" ] && echo "$d expires $exp"
done

That's fine for a handful of domains checked occasionally. For anything you actually depend on, a scheduled service is the better answer — see the automated option below.

How to Set Up Domain Expiry Monitoring

1. Identify every domain you're responsible for. This includes primary domains, defensive registrations (common misspellings, alternate TLDs), and any domain a subdomain or CNAME points at — a dangling reference to an expired domain is a common dangling-DNS security issue on its own.

2. Pull the current expiry date for each one. Use the WHOIS Lookup tool or the whois/RDAP commands above to establish a baseline and confirm the registrar's records match what you expect.

3. Set alert thresholds at 30, 14, and 7 days out — not just one. A single 30-day warning gets lost; three warnings at decreasing intervals mean at least one lands when you're actually available to act on it.

4. Route alerts somewhere that isn't the domain itself. If your monitoring alert email is admin@thedomain.com and that domain expires, the alert never arrives. Use a separate domain or a service-based alert channel (SMS, Slack webhook, a different registrar account's email).

5. Automate the check on a recurring schedule. DNSnexus Monitor polls WHOIS/RDAP daily and tracks expiry, registrar, and nameserver changes across your domains without needing you to run manual lookups.

Stop checking manually. DNSnexus Monitor watches your DNS records, SSL expiry, email auth, and blacklist status — and alerts you before things break. Free tier covers one domain.

6. Verify DNS is intact after every renewal. A renewal that happens through a different registrar interface (auto-renew billing failure resolved manually, for instance) occasionally resets nameservers to defaults. Re-check with the DNS Lookup tool after any renewal event, planned or emergency.

Common Issues & Troubleshooting

Problem: Renewal notice never arrived. Cause: Registrant contact email is outdated, filtered as spam, or hosted on the expiring domain itself. Fix: Update WHOIS contact info immediately, whitelist the registrar's sending domain, and set an independent monitor so notices aren't the only line of defense.

Problem: Auto-renew failed silently. Cause: Expired card on file, or auto-renew was disabled during a past account change. Fix: Confirm auto-renew status and a valid payment method directly in the registrar dashboard — don't assume enabling it once keeps it enabled after a card expires.

Problem: Domain shows as expired but site still loads. Cause: Browser or resolver cache, or the domain is still inside the auto-renew grace period where resolution hasn't been cut yet. Fix: Flush local DNS cache and re-check with the WHOIS Lookup tool for the authoritative registry status — cached pages are not proof the domain is safe.

Problem: Trying to renew an expired domain and the registrar wants a large fee. Cause: The domain has already entered the Redemption Grace Period, where redemption pricing (not standard renewal pricing) applies. Fix: Pay the redemption fee if the domain is business-critical — waiting risks it passing into pending delete, after which it's unrecoverable at any price.

Frequently Asked Questions

Q: How long before a domain expires should I renew it?

Renew at least 30 days before expiration. That's inside the standard grace window at normal pricing, and it gives time to fix payment issues without risking the Redemption Grace Period's higher fees.

Q: Can I get an expired domain back after it's deleted?

Only during the Redemption Grace Period (typically 30 days for gTLDs per ICANN's ERRP), and only the original registrant can restore it, at a redemption fee. After RGP and the ~5-day pending-delete window, it's released and unrecoverable.

Q: What happens to my email when a domain expires?

Email tied to that domain (MX records, mailboxes, and any account-recovery email address using that domain) stops working the moment DNS resolution is disabled — usually once the domain enters the Redemption Grace Period.

Q: Does an expired domain affect SEO?

Yes. Once resolution stops, search engines see the site as unreachable and will drop indexed pages over time. Even a same-day recovery can cause a temporary ranking dip; a multi-week outage can require significant re-crawling to recover.

Q: How do I check a domain's expiry date without logging into the registrar?

Run a WHOIS or RDAP query. The WHOIS Lookup tool returns the registry expiry date, registrar, and status codes for any public domain in seconds.

Q: What's the difference between the grace period and the redemption period?

The grace period follows expiration and lets you renew at the normal price with the domain typically still resolving. The redemption period follows the grace period, disables DNS resolution, and requires a much higher redemption fee to restore — per RFC 3915's grace-period model as implemented under ICANN's ERRP.

Free Newsletter

Get guides like this by email

DNS, email auth, and security playbooks delivered when they publish. No spam.