Skip to content
AdminKit

What happens when a domain expires, and how do you check before it does?

AdminKit's domain expiry check reads a domain's registry expiry date and status codes directly from WHOIS/RDAP. A missed renewal doesn't delete a domain immediately: ICANN's Expired Registration Recovery Policy requires reminder notices, then a renewal window, then a 30-day redemption period at a steep fee — only after that does the name become available for anyone else to register.

By AdminKit team, Netbase JSC · Updated

Key takeaways

  • An expired gTLD domain is not released straight away. It passes through an auto-renew grace period (0 to 45 days in ICANN’s lifecycle chart), a 30-day Redemption Grace Period and a 5-day pending delete before anyone else can register it.
  • Every stage after the expiry date costs more or breaks more: DNS is switched off before deletion, and redemption carries a separate restore fee.
  • The status codes in a whois/RDAP lookup tell you which stage a domain is in. redemptionPeriod or pendingDelete means act today.
  • The real fix is process: auto-renew with a valid card, a registrant email you read, the expiry date in your own calendar, and a lock against unwanted transfers.

What happens to a domain after its expiry date?

It moves through a fixed sequence of grace periods, and only at the end is it released. Domain expiry sits alongside WHOIS/RDAP lookups and other registration-data topics in AdminKit’s DNS cluster. A domain’s expiration date is set by its registry, but what happens around that date for a generic top-level domain (.com, .net, .org, and most others) is standardized by ICANN’s Expired Registration Recovery Policy (ERRP), which every ICANN-accredited registrar’s contract requires it to follow. ERRP sets a floor, not a fixed script — exact grace-period lengths and extra reminders are still up to each registrar — but the sequence is consistent:

  1. At least two pre-expiration notices. One roughly 30 days out (26-35 days is the allowed window) and a second roughly 7 days out (4-10 days). Both must go to the registrant’s contact email on file — which is exactly why keeping that address current matters more than most people realize. ERRP section 2.1.2 adds a third notice within five days after expiration if the name has been neither renewed nor deleted.
  2. A post-expiration renewal window. Under ERRP section 2.2, the registrant can renew from the moment of expiration until the registrar deletes the name. If the registrar keeps the name for eight days or more, the domain’s DNS must be interrupted for at least the last eight consecutive days it is still renewable; if it deletes sooner, DNS is interrupted from expiry until deletion. ICANN’s gTLD lifecycle chart shows this auto-renew grace period lasting 0 to 45 days. During it the registration itself hasn’t been deleted and a renewal still works.
  3. A 30-day Redemption Grace Period (RGP), if it actually gets deleted. If nobody renews during the grace window above and the registrar deletes the name, ERRP section 3.1 requires every gTLD registry except sponsored ones to offer a 30-day RGP. RFC 3915 defines the redemptionPeriod status used during it, and leaves the length to registry policy. Only the original registrant can recover the name, through the registrar that deleted it, usually for a redemption fee well above a normal renewal because the registry itself charges registrars to reverse a deletion.
  4. Deletion and public release. Once the Redemption Grace Period lapses without recovery, the name enters pendingDelete for 5 days, according to ICANN’s registrant FAQ, and is then released for anyone to register — first-come-first-served, with no further claim for the previous owner. ICANN’s Expired Domain Deletion Policy governs the deletion step. ICANN’s lifecycle chart marks the release point as where “drop catch” activity happens: services that try to register expiring names the moment they free up.

Put together, a domain typically has somewhere between a few weeks and a couple of months of recoverable window after its listed expiry date — but every stage after the first renewal reminder costs more or risks more than simply renewing on time, and the final step is irreversible.

StageLength (ICANN chart / policy)Does the domain resolve?Who can recover it
Registered1-10 year termYesOwner renews normally
Auto-renew grace0-45 daysInterrupted for at least the last 8 renewable daysOwner, usually at the normal renewal price
Redemption Grace Period30 daysNo; ERRP 3.2 requires the registry to disable DNSOwner only, through the same registrar, with a restore fee
Pending delete5 daysNoNobody
Released—Not registeredAnyone, first come first served

What do the status codes in a domain lookup mean?

They tell you which stage of the lifecycle a domain is in, and whether anything blocks a change. Registries set them through EPP, the protocol registrars use to talk to registries, and RDAP shows the same values in a readable form: RFC 8056 maps each EPP code to an RDAP string, so clientTransferProhibited appears as client transfer prohibited. ICANN’s EPP status codes page explains each one for registrants. The ones relevant to expiry:

EPP codeRDAP formWhat it means
okactiveNo pending operations or prohibitions
clientTransferProhibitedclient transfer prohibitedRegistrar lock against transfers; normal and protective
autoRenewPeriodauto renew periodRegistration expired and was auto-renewed by the registry; still in grace
clientHoldclient holdRegistrar has told the registry not to put the domain in DNS, so it doesn’t resolve
redemptionPeriodredemption periodDeleted; 30 days to restore
pendingRestorepending restoreRegistrar has asked the registry to restore it
pendingDeletepending deleteRestore window over; the domain will be purged

ICANN’s page says a domain is held in redemptionPeriod for 30 days and is purged five calendar days after that period ends. It also notes that some registry operators offer a Registry Lock service, which sets server-level codes such as serverTransferProhibited and serverUpdateProhibited as an extra layer on top of the registrar’s own lock.

How do you read the expiry date in an RDAP response?

Look in the events array for the entry whose eventAction is expiration. RFC 9083 (Section 4.5) defines events as objects with a required eventAction and eventDate, and notes that events can be dated in the future, with expiry as the example use case. Section 10.2.3 registers the action values, including registration, last changed, expiration and transfer.

Example RDAP domain response, trimmed (illustrative, documentation names):

{
  "objectClassName": "domain",
  "ldhName": "example.com",
  "status": ["client transfer prohibited", "auto renew period"],
  "events": [
    { "eventAction": "registration", "eventDate": "2016-03-14T09:12:00Z" },
    { "eventAction": "last changed", "eventDate": "2026-10-28T04:01:17Z" },
    { "eventAction": "expiration",   "eventDate": "2027-10-27T09:12:00Z" }
  ],
  "nameservers": [
    { "ldhName": "ns1.example.net" },
    { "ldhName": "ns2.example.net" }
  ]
}

Read the status array together with the dates. In this example the expiration date is a year away, which looks healthy, but auto renew period says otherwise. RFC 3915 defines that grace period as following an expiry that the registry has already extended automatically. The registry has rolled the date forward, but the registrar can still delete the name during this period and, under RFC 3915, receive a credit for the renewal. The rolled-forward date is no guarantee that you still hold the name. redemption period in the status means the name has been deleted and the restore clock is running, whatever the date says.

The examples in RFC 9083 give eventDate values in UTC, marked with a trailing Z. A domain listed as expiring at 2027-10-27T09:12:00Z may expire on the evening of the 26th or the afternoon of the 27th in your local time.

What AdminKit’s whois tool actually shows you

The whois/RDAP lookup is a point-in-time check, not a monitoring service: enter a domain and it fetches the live RDAP record — the structured, JSON successor to the old text-based whois protocol, defined by RFC 9083 (also on the IETF Datatracker) — directly from your browser via the public rdap.org proxy. For a domain, that includes the registrar, the registration and expiration dates (with a plain “expires in N days” or “expired” readout), the last-changed date, status codes such as clientTransferProhibited, and the authoritative nameservers.

What it does not do: it does not send you a reminder before the date it shows, it does not know which grace period (if any) a given registry applies after that date, and it does not distinguish “expired but still in the free renewal window” from “expired and in the expensive redemption period” — RDAP only reports the dates and status codes a registry chooses to publish, and grace-period timing itself is registrar/registry policy rather than something RDAP encodes. Treat the expiry date as the fact worth checking regularly yourself, not as a filed-away deadline — a quick lookup before you expect it to lapse tells you whether you’re still looking at a normal renewal or already in grace-period territory. The status codes shown alongside the date, read with the table above, are what tell those stages apart. For a field-by-field walkthrough of the full result, see how to read a whois/RDAP lookup result.

What breaks when a domain expires?

Everything that depends on the name resolving. ERRP requires the registrar to interrupt the domain’s DNS during the post-expiration window, and during the Redemption Grace Period the registry must disable DNS resolution entirely. ICANN’s lifecycle chart labels that stage plainly: the domain is no longer in the zone, and website and email no longer function.

ServiceEffect once DNS is interruptedWhat to check after renewal
WebsiteVisitors see an error or the registrar’s expiry pageThe site loads on its own nameservers again
Inbound emailSenders can no longer look up your MX records, so mail stops arrivingMX records answer again via MX lookup
CertificatesA CA cannot validate a name that doesn’t resolve, so issuance and renewal failThe live certificate via SSL/TLS check
Subdomains and APIsEvery name under the domain stops resolving with itKey records via DNS lookup

ERRP section 2.2.6 requires the registrar to restore your DNS settings immediately, or as soon as is commercially reasonable, after you renew. Resolvers that cached a negative answer while the domain was down may keep returning it until that cache entry expires. A lapsed domain is also a risk to other people’s zones: if a nameserver hostname or a CNAME target sits on a domain that gets released, whoever registers it next can answer for those records, the scenario covered in finding a dangling CNAME.

What should you do if a domain has already expired?

Contact your registrar today, and use the status code to judge how urgent and how expensive it is:

Status you seeStageAction
auto renew periodAuto-renew graceRenew now if you want to keep it; the registrar decides when it deletes
client holdTaken out of DNS by the registrarAsk the registrar to remove the hold, as ICANN’s status page advises
redemption periodDeleted, 30-day restore windowAsk for a restore; the registrar must allow it under ERRP 3.3
pending deletePurge scheduledNothing reliable; ask the registrar, then watch for release

You can move an expired domain to another registrar: ICANN’s FAQ says registrars cannot refuse a transfer because of expiration or non-renewal. Once the name is in Redemption Grace Period, though, the current registrar has to restore it first, which may mean paying a redemption fee.

How do you make sure a renewal is never missed?

There isn’t a clever technical fix for a missed renewal — the actual fix is process, not configuration:

  • Keep the domain’s registrant and billing contact email current with the registrar, since every ERRP notice goes there.
  • Turn on auto-renewal and keep the payment method on file valid; most unwanted expirations are a failed card, not a forgotten decision. Even then, Cloudflare Registrar’s renewal documentation warns that there is no guarantee an automatic renewal will succeed, naming billing failures and registry downtime as causes, and recommends reviewing your account regularly.
  • Calendar the expiry date itself, not just the first reminder — reminder emails can land in spam, get filtered, or simply go unread.
  • If a domain unexpectedly shows as expired or already in a grace/redemption status, contact the registrar immediately; every day that passes moves it toward a more expensive, and eventually irreversible, stage.
  • Read your registrar’s renewal, post-expiration and redemption fees before you need them. ERRP section 4.1 requires registrars to display all three on their website.
  • Renew for more than one year where it makes sense. ICANN’s FAQ notes registrations typically run from one to ten years.
  • Ask about Registry Lock for domains you cannot afford to lose. It protects against unauthorized transfers and updates, not against non-renewal, so it complements auto-renewal rather than replacing it.

Tracking this across more than one domain is its own problem — see our domain portfolio owners and buyers page for the free checks AdminKit offers domain owners; a watchlist across many domains at once is something to talk to our team about.

This guide is general information, not a security audit of your specific network — see our disclaimer for what AdminKit's guidance does and does not commit to.

Frequently asked questions

Exactly how many reminder emails does a registrar have to send before my domain expires?

Under ICANN's Expired Registration Recovery Policy (ERRP), a registrar must send at least two separate notices: one 30 days before expiration (allowed to land anywhere from 26 to 35 days out) and a second 7 days before expiration (allowed 4 to 10 days out). That's a floor, not a ceiling — many registrars send more, including a notice on the expiration date itself — but two is the contractual minimum, and spam filters or an outdated contact email can still mean you never see them.

Can I still renew a domain after it expires?

Usually yes, for a while. ERRP lets the registrant renew from the moment of expiration until the registrar deletes the name, and if the registrar keeps the name eight or more days, the last eight consecutive renewable days must have the domain's DNS switched off as a warning sign. ICANN's gTLD lifecycle chart shows this auto-renew grace period lasting anywhere from 0 to 45 days. The exact grace-period length is set by each registrar/registry, not by ERRP itself, so check your own registrar's policy rather than assuming a number.

What is the 'redemption period' and why is it expensive?

If the registrar actually deletes the expired name (rather than just holding it in grace), ICANN still requires a further 30-day Redemption Grace Period during which only the original registrant can get it back, through the same registrar, before anyone else can register it. Registries charge registrars a redemption fee for pulling a name out of this state, and registrars pass that cost on, which is why a redemption-period renewal often costs far more than a normal one — it is recovering a deleted registration, not renewing an active one.

Once a domain is released, can I just register it again myself?

Only if nobody else does first. After the Redemption Grace Period ends, the registry deletes the name outright and it becomes available to the public — at that point it is first-come-first-served like any unregistered domain, and automated "drop-catching" services specifically watch for popular expiring names to register the instant they free up. There is no reliable way to reclaim a domain once it reaches this stage.

Does AdminKit's whois tool warn me automatically before my domain expires?

No — it is an on-demand lookup, not a monitoring service. Run the whois/RDAP check whenever you want today's expiry date and status codes for a domain; it does not watch a domain over time or send you a reminder. Your registrar's own renewal notices and calendar reminders are the actual safety net.

Want AdminKit to watch this for you?

Free checks tell you the state today. Protective DNS and monitoring tell you when it changes.

Huy Nguyen (David), Founder and CEO of Netbase JSC

Talk to an expert

Huy Nguyen (David), Founder & CEO, Netbase JSC

Ask whether this fix applies to your setup, or get a second pair of eyes on your DNS and mail records.