The domain registration lifecycle, from registry to redemption
Jaime Guerrero · · 6 min read
You don't own a domain name. You hold a registration for a fixed term, one to ten years, and it has to be renewed or it goes back into the pool. Most of the time that's invisible, until a renewal fails and the site, the email and every account tied to that email address go with it.
This is how the system around a registration works, and what happens day by day after one expires.
Who's involved
| Role | Who | What they do |
|---|---|---|
| ICANN | One organization | Sets the policies for generic TLDs like .com, .org and .net |
| Registry | Verisign for .com and .net, others for each TLD | Runs the TLD's database and its DNS servers. The authoritative record of who holds what. |
| Registrar | IONOS, Namecheap, Cloudflare, GoDaddy and many more | Sells and manages registrations, and talks to the registry on your behalf |
| Registrant | You, or your company | The holder of the registration |
Country-code TLDs like .uk or .de follow their own national rules, not ICANN's. Everything below about grace periods applies to generic TLDs such as .com. Check your ccTLD's registry for its timeline.
Looking a domain up: RDAP, not WHOIS
For generic TLDs, WHOIS was officially retired on January 28, 2025. RDAP (Registration Data Access Protocol) replaced it: same purpose, but it returns structured JSON over HTTPS instead of free-form text, so tools can read it reliably. Many ccTLDs still run WHOIS.
rdap.org redirects you to the right registry:
$ curl -sI https://rdap.org/domain/example.com | grep -i location
location: https://rdap.verisign.com/com/v1/domain/example.com
And the registry's answer, trimmed to the fields that matter:
{
"ldhName": "EXAMPLE.COM",
"status": [
"client delete prohibited",
"client transfer prohibited",
"client update prohibited"
],
"events": [
{ "eventAction": "registration", "eventDate": "1995-08-14T04:00:00Z" },
{ "eventAction": "expiration", "eventDate": "2027-08-13T04:00:00Z" },
{ "eventAction": "last changed", "eventDate": "2026-08-14T08:01:43Z" }
],
"secureDNS": { "delegationSigned": true },
"nameservers": [
{ "ldhName": "ELLIOTT.NS.CLOUDFLARE.COM" },
{ "ldhName": "HERA.NS.CLOUDFLARE.COM" }
]
}
The expiration date here is the registry's. Your registrar's dashboard may show a slightly different date or its own renewal deadline, and when they disagree, the registry is the record that counts.
What the status codes mean
The status list uses EPP status codes, the protocol registrars use to talk to registries. RDAP writes them as words (client transfer prohibited). In other tools you'll see the same thing in camel case (clientTransferProhibited).
The prefix tells you who set it:
client…statuses are set by the registrar, usually through a toggle in your dashboard.server…statuses are set by the registry, either for its own reasons or as part of a paid registry lock service.
The ones worth knowing:
| Status | Meaning |
|---|---|
clientTransferProhibited | The transfer lock. The domain can't be moved to another registrar until it's removed. It should be on. |
clientUpdateProhibited, clientDeleteProhibited | Changes or deletion are blocked until the registrar removes the flag |
serverTransferProhibited and the other server… statuses | The registry blocks the action. With registry lock, removing it needs a manual, out-of-band verification, which protects high-value domains from a compromised registrar account. |
clientHold, serverHold | The domain is taken out of DNS. Nothing resolves. Often seen after expiry or in an abuse or payment dispute. |
autoRenewPeriod | The registry just auto-renewed the domain at expiry, see below |
redemptionPeriod | Deleted, but can still be restored |
pendingDelete | Being deleted. Can't be restored anymore. |
A domain that suddenly loses its transfer lock, gains a hold status or changes nameservers without anyone on your team doing it is worth investigating that day. These are also the first signs of a hijack attempt.
What happens when a .com expires
This is the timeline for generic TLDs under ICANN's rules. The exact length of some steps depends on the registrar.
- Before expiry. ICANN's Expired Registration Recovery Policy (ERRP) requires the registrar to send renewal reminders about one month and about one week before the expiration date. They go to the registrant contact email, so if that's an old address, nobody sees them.
- Expiration day. For
.com, the registry automatically renews the domain and charges the registrar, then gives the registrar an auto-renew grace period of up to 45 days to either keep it or delete it for a refund. You see this asautoRenewPeriod. - Shortly after. The registrar must send another notice within five days after expiration. It also must interrupt DNS resolution, typically by replacing your nameservers with a parking page, for at least the final eight days during which you can still renew. Your website and email stop working here, while the registration technically still exists.
- Renewal at the normal price. As long as the registrar hasn't deleted the domain, you can usually still renew it for the regular fee. How long that lasts is the registrar's choice, from a few days to the full 45.
- Redemption grace period, 30 days. Once the registrar deletes the domain, the registry holds it for 30 days in
redemptionPeriod. It doesn't resolve, can't be transferred, and can only be restored by the original registrant through the registrar, for a restore fee that's often much higher than a renewal. - Pending delete, 5 days. No more restores. The status is
pendingDelete. - The drop. The name is released and anyone can register it. Drop-catching services register valuable names within seconds of release.
So from expiration to losing the name for good is roughly 75 days at most for .com, and the outage starts much earlier than that, at step 3.
Why losing a domain is worse than an outage
When the domain lapses, the website going down is the obvious part. The less obvious part is that whoever registers it next controls its email. They can receive password resets for every account registered with an address at that domain: your cloud provider, your code host, your payment processor, the SaaS tools former employees signed up for. They can also get valid TLS certificates for it, since they now pass domain validation.
That's why expiry matters even for domains you've stopped using. An old company domain with years of accounts tied to it is worth more to an attacker than to you.
Transfers and locks
Moving a domain to another registrar needs an authorization code (often called the EPP or auth code) from the current registrar, and the transfer lock must be off. Most registrars and registries also block transfers for 60 days after a domain is registered or transferred. Changing the registrant can trigger a similar lock, which some registrars let you opt out of. Plan registrar moves well before an expiry date, not during one.
DNSSEC: the expiry nobody expects
"delegationSigned": true in the RDAP output above means the domain uses DNSSEC: the registry publishes a DS record that tells resolvers which key signs the domain's DNS. If you move DNS to a new provider and the old DS record stays at the registry, validating resolvers can't verify your new answers and return SERVFAIL. For many visitors the domain simply stops resolving. Turn DNSSEC off, or update the DS record, through your registrar as part of any DNS migration.
What I'd set up
- Auto-renew, with a card that won't expire before the domain does. Most lapsed domains had auto-renew on and a dead card.
- A registrant and account email that isn't on the domain itself. If
you@yourdomain.comis where renewal notices go, those notices stop arriving at exactly the moment the domain stops resolving. - Multi-year registration for anything important. It costs the same per year and moves the deadline far out.
- Transfer lock on, and registry lock for the domains you can't afford to lose.
- Monitoring from the registry's side. Check the RDAP expiration date and statuses on a schedule, independent of the registrar's emails.
The free check reads a domain's registration from RDAP, including the expiry date, registrar and transfer lock: