When a Domain Expires: Grace Periods, Redemption, and How Not to Lose Your Name
Domains
October 30, 2026
Some outages start with a server. Others start with a renewal email nobody read. When a domain expires, the website and email that rely on it can stop working, and if nobody steps in, you can lose the name itself. The timeline is longer than most people think, which is exactly why the name gets lost: everyone assumes there's still time.
Who sets the rules
For generic top-level domains such as .com, .net, and .org, the Internet Corporation for Assigned Names and Numbers (ICANN) sets policies that accredited registrars have to follow. Country-code domains, such as .uk or .ca, follow their own registry rules, so check those separately.
Reminders you should receive
ICANN's Expired Registration Recovery Policy (ERRP) requires registrars to send renewal reminders to the registered name holder at least twice before expiration, and once more within five days after expiration if the domain hasn't been renewed.
Those reminders go to the email address on the registration. If that address is out of date, or sits on the same domain that's expiring, you may never see them.
What happens after expiry
The timeline varies by registrar and registry, but generally it goes like this:
- Expiration. Under ERRP, the registrar has to interrupt the DNS resolution path for the domain at some point after expiration, so the website and email stop working, often replaced by a parking or renewal notice page. This is often the first moment anyone notices.
- Renewal grace period. Many registrars let you renew at the normal price for a while after expiration. ICANN's policy gives the registrant at least eight days after expiration to renew for many gTLDs, and registrars often allow longer.
- Redemption grace period. For many gTLDs, once the registrar deletes the name, the registry holds it in a redemption period, typically 30 days. During that window the original registrant can usually restore it, often for an extra fee.
- Pending delete and release. After redemption, the name sits in pending delete, typically 5 days. Then the name is released and anyone can register it.
Each registrar's terms set the exact durations and fees, so read yours.
The reminder schedule in detail
ICANN's policy is more specific than "at least twice." Registrars must send one notice approximately one month before expiration and another approximately one week before. ICANN's compliance guidance treats 26 to 35 days and 4 to 10 days before expiration as meeting those targets. A third notice must go out within five days after expiration if the name has not been renewed. ICANN also requires that these notices arrive in a way that does not require the registrant to opt in, such as email.
If you never received them, ICANN accepts complaints through its Domain Renewal Complaint Form. That will not bring back a lost name by itself, but it is the formal route if a registrar skipped its obligations.
What the expired page must say
When a registrar interrupts DNS for an expired name and points it to a page of its own while the name can still be renewed, ERRP requires that page to say clearly that the registration has expired and to give renewal instructions. If visitors report an unfamiliar parking page on your domain, check the registration first, before assuming the site was hacked.
WHOIS is gone; RDAP replaced it
As of January 28, 2025, ICANN made RDAP the definitive source of registration data for generic top level domains, retiring the older WHOIS service for gTLDs. RDAP returns structured data, which makes it easier for monitoring tools to read expiration dates reliably. Many fields that once showed owner contact details are now redacted for privacy, but the expiration date, registrar and status codes are normally still visible.
Status codes are worth watching too. A domain showing redemptionPeriod or pendingDelete is already past the point of simple renewal. A domain showing clientTransferProhibited has registrar lock turned on, which is what you want for an important name.
Keep your contact data current
A separate ICANN rule, the Registration Data Reminder Policy, requires registrars to show registrants their registration data at least once a year and remind them that false contact information can be grounds for cancellation. Treat that annual email as a prompt to check that the address still reaches someone who will act on it.
Country code domains are different
Rules for .uk, .ca, .io and other country code domains are set by each registry, not by ICANN policy, and grace periods vary widely. Some registries suspend a name soon after expiry, others hold it for months. If a country code name is important to your business, read that registry's expiry policy and set reminders based on it rather than on the gTLD timeline.
How to protect your domains
- Turn on auto-renew and keep a valid payment card on file.
- Use a contact email on a different domain from the one you're protecting.
- Renew for multiple years for critical names.
- Consolidate your domains at fewer registrars so nothing slips through.
- Enable registrar lock to make unauthorized transfers harder.
Keep a simple domain register
List every domain the business owns, including old campaign names and typo domains that redirect to the main site. For each, record the registrar, expiry date, auto renew status, lock status and the account owner. Review it twice a year. Forgotten redirect domains are a common source of surprise, because nobody notices when they lapse until a link in an old email stops working.
Store the register somewhere more than one person can reach, so a holiday or a departure does not leave renewals unattended.
Monitor expiry dates
Registration data is public through RDAP, which replaced WHOIS for gTLDs in January 2025. A monitoring tool can read each domain's expiry date and warn you well ahead of time, for instance 30 and 7 days out. That pairs well with uptime checks, which only tell you once the site is already down. How those uptime percentages convert into minutes is in what 99.9 percent uptime means.
Sources
- ICANN, Expired Registration Recovery Policy: https://www.icann.org/en/contracted-parties/consensus-policies/expired-registration-recovery-policy/expired-registration-recovery-policy-21-02-2024-en
- ICANN, "Domain Name Renewal and Expiration FAQs": https://www.icann.org/resources/pages/domain-name-renewal-expiration-faqs-2018-12-07-en
- ICANN, Registration Data Access Protocol (RDAP): https://www.icann.org/rdap
- IETF, RFC 3915, Domain Registry Grace Period Mapping (redemption): https://www.rfc-editor.org/rfc/rfc3915
- ICANN, Expired Registration Recovery Policy (2013 text with reminder timing): https://www.icann.org/en/contracted-parties/consensus-policies/expired-registration-recovery-policy/expired-registration-recovery-policy-28-02-2013-en
- ICANN, "About Not Receiving Renewal Reminders": https://www.icann.org/resources/pages/reminders-2013-05-03-en
- ICANN, "ICANN Update: Launching RDAP; Sunsetting WHOIS" (January 27, 2025): https://www.icann.org/en/announcements/details/icann-update-launching-rdap-sunsetting-whois-27-01-2025-en
- ICANN, Registration Data Reminder Policy: https://www.icann.org/en/contracted-parties/consensus-policies/registration-data-reminder-policy/registration-data-reminder-policy-21-02-2024-en