What happens to expired domains: the expiration timeline

On the morning a domain expires, the registrant's website stops resolving, their email bounces back with delivery errors, and their registrar — frequently the same one that cheerfully renewed the registration twelve months earlier — sends a polite renewal notice. By the time that email lands in an inbox, the Auto-Renew Grace Period has already begun, the countdown is irreversible, and the domain is technically no longer yours to use. What follows is not a simple deletion but a multi-stage administrative process regulated by ICANN policy and shaped, at every step, by registrar behavior that has very little to do with customer goodwill.

The expiration timeline for a generic top-level domain runs through at least four distinct statuses over roughly seventy to eighty days, with extensions past one hundred twenty days depending on the registrar and the TLD. Understanding each phase — and, more importantly, the trap doors built into each one — is the difference between a recoverable lapse and a name that surfaces months later in someone else's auction cart.

The first 45 days: Auto-Renew Grace Period and the silent suspension

The Auto-Renew Grace Period begins the instant a domain's registration term ends without a successful renewal transaction. For most gTLDs this phase runs roughly 0 to 45 days, with thirty days as the de facto industry norm. During this window the domain is, in the strict contractual sense, expired — the registry has terminated the registration — but ICANN policy and the registrar's terms of service still allow the original registrant to recover the name at the standard renewal rate.

What the Auto-Renew window does not do is keep the domain working. Website hosting, email routing, and DNS resolution are typically suspended or redirected to a registrar-controlled landing page within hours of expiration. The registrant retains a property claim, but not a functioning service. This is the first small piece of fee-driven theater: the registrar collects the renewal fee but strips functionality during the very period in which the renewal option is presented as the easy fix.

Auto-renew is enabled by default at most major registrars. That sounds helpful until you examine the failure modes: an expired credit card, a closed PayPal account, or a billing address that no longer matches will cause the renewal attempt to silently fail. The registrant may never see an error — only the eventual expiration email — and by then, depending on the registrar, the original registration may already have been pushed toward auction. There is no requirement that a registrar attempt to notify a registrant before the grace period ends. The terms of service reserve the right, but reserve it loosely.

Auto-renew is sold as a convenience. In practice it is an unattended billing pipeline with no failure alerting — which is precisely how good domains end up on auction blocks.

Redemption Grace Period: paying to recover your own property

When the Auto-Renew Grace Period closes without a successful renewal, the domain moves into the Redemption Grace Period (RGP), a thirty-day window defined under the ICANN Registrar Accreditation Agreement and the Expired Domain Deletion Policy. The name is removed from the registry's zone files, meaning it no longer resolves to any server on the public internet. It is, in functional terms, dead.

Recovery during RGP is technically permitted, but the cost structure is punitive. Registrars charge a "redemption" or "restore" fee on top of the standard renewal price and the ICANN fee — typically between $80 and $270 or more, depending on the TLD and the registrar pricing tier. The arithmetic is deliberately unpleasant: a one-year renewal that originally cost $12 can require $100 or more to execute during redemption, and the registrar will frame this as a "recovery service."

This is the second piece of fee-driven theater, and the most cynical. The domain is still contractually tied to the original registrant; the registry has not released it; no third party can yet acquire it. Yet the registrar charges a ransom to return the name to the person whose lapse caused the situation in the first place. The RGP was created because ICANN recognized that registrants occasionally fail to renew through no fault of their own, and the original policy intent was a brief safety window. Modern registrar pricing has converted a consumer protection mechanism into a monetization event.

Registrar auctions: where most expired domains actually change hands

This is the part of the timeline that the industry marketing tends not to mention. Many registrars — GoDaddy being the most prominent example — divert expiring domains to internal auction inventory before the registry deletion process completes. On GoDaddy's system, an expiring domain is automatically listed on GoDaddy Auctions twenty-six days after expiration for a ten-day bidding window. If no bid is placed by day thirty-six, the domain proceeds to what GoDaddy calls a Final Closeout Auction.

The mechanism is not advertised in renewal reminder emails. The auction listing is a separate transaction running in parallel to the redemption process, and the two interact in ways that are quietly consequential. If a bid is placed on an expired domain during this window, the original registrant can no longer renew the domain from their own account — the auction path takes precedence. So a lapsed registrant who finally opens the renewal email on day thirty-one, intending to recover the name, may find the renewal button disabled because GoDaddy's auction system has already claimed it.

Other registrars run similar schemes, though with different timing. NameJet operates a backorder and auction platform that several large registrars feed into. Dynadot runs its own expired-domain marketplace. DropCatch sells direct catch rights. The structural reality is that an expiring name of any meaningful value does not drift through the system passively — it is actively harvested by the registrar or its auction partner before the registry ever gets a chance to drop it.

This is the heart of the administrative minefield. The industry sells expired domains as "digital real estate" flowing through orderly channels. In practice, the order is enforced unilaterally by the registrar, and the original owner is the last party to learn that the channels have been redirected.

The numbers in the table are deliberately not pinned to the day. Each registrar runs its own internal clock against ICANN's outer limits, and ccTLDs operate outside the gTLD framework entirely —.de,.eu,.nl, and others have their own grace and redemption structures, often with zero-day grace periods that leave registrants no recovery window at all.

Pending Delete: the five-day window where no one has keys

If the domain is not restored during redemption and not sold through a registrar auction, it enters Pending Delete status. This is a precisely five-day window — not approximate, not "around five days," but exactly five days by ICANN registry protocol. During Pending Delete, the domain is locked at the registry level. No registrar can renew it, restore it, or modify its status. The name sits in the registry's purge queue, waiting for release.

Pending Delete is the quiet phase of the lifecycle, and for an investor watching a target name it is the part of the calendar that determines whether they have a realistic chance or are simply observing. The five-day countdown is a hard stop; whoever is connected to the registry the moment the timer expires is the only party with a chance of catching the name.

There is one important exception. ICANN's Expired Domain Deletion Policy generally requires registrars to delete expired registrations within 45 days of termination, but it carves out extenuating circumstances that can hold a name in extended status. UDRP proceedings — the Uniform Domain-Name Dispute-Resolution Policy under which trademark holders can challenge a registration — can place a hold on a contested name. Active litigation involving the domain can also delay release. A registrar-facing bankruptcy proceeding can pause the process further. These are edge cases, but they matter: a name that disappears into Pending Delete on a Tuesday may not actually drop on Sunday if a UDRP complaint was filed on Wednesday.

The drop and the catchers: how domains return to the public pool

When the Pending Delete window closes, the registry purges the domain from its zone and releases it back to the public registration pool — the "drop." At this moment, a small set of well-capitalized drop-catching services compete to register the name within milliseconds of release. DropCatch, SnapNames, and NameJet maintain direct multi-registrar connections to multiple registries, allowing them to submit registration requests the instant a name becomes available.

For most domain names, the drop is a non-event. The name will be caught by whichever catcher is fastest, held for a brief auction or backorder cycle, and either sold to a backorder customer or relisted at a market price. The catcher's economics depend on volume: each backorder covers dozens of missed attempts on names that nobody actually wanted.

But this is also where the "public pool" myth breaks down. The "public pool" is theoretical. In practice, a name that drops has roughly one to two seconds of genuine accessibility before being claimed by automated infrastructure. A retail user with a browser tab open at the right moment has functionally zero chance of catching a meaningful name, even if they happen to know the precise drop second in advance.

The public pool is not a pond. It is a sluice gate, and three companies own the keys.

The ccTLD caveat deserves emphasis. Country-code registries —.de,.fr,.nl,.eu,.uk — set their own deletion policies outside ICANN's jurisdiction, and several of them implement zero-day grace periods. A name in those zones can move from active registration to release within hours of expiration, bypassing redemption entirely. The expiration timeline described above applies to standard gTLDs; treating it as universal is one of the more common mistakes novice investors make.

Defensive tactics for registrants and investors

The expiration timeline is not really about the calendar. It is about who controls each phase and at what price. A registrant who understands the structure can avoid losing a name through ordinary inattention; an investor who understands it can target the right phase of the lifecycle for the names they actually want.

1. Audit auto-renew payment methods on a fixed quarterly schedule. Expired credit cards and stale PayPal authorizations are the single most common cause of accidental expiration, and registrars do not flag a failed renewal attempt with anything more prominent than a generic expiration email sent days later.

2. Track expiration dates independently of registrar notifications. Use a calendar, a domain portfolio tool, or both. Treat registrar reminder emails as a back-up, not a primary source — they are unreliable, frequently delayed, and sometimes suppressed entirely when an auction listing is in progress.

3. For domains that matter, register for the maximum ten-year term. The annual renewal fee is the same regardless of term length, but a multi-year registration removes the auto-renew failure mode from the equation.

4. For high-value names, consider registry lock. Most major registries offer a lock service that requires registrar-level authentication for any change, including accidental deletion. The cost is modest and the protection is significant.

5. If a name has slipped into registrar auction, do not assume the auction path is the only option. Some registrars will allow direct buy-now purchases at a posted price that is lower than the eventual auction close. Monitor the listing.

6. Treat ccTLDs as a separate system. If you hold names in.de,.eu,.fr, or any other country-code zone, study that registry's specific lifecycle. A zero-day grace period means there is no recovery window at all — only a redemption fee at best, and immediate drop at worst.

7. If you are buying, do not chase the drop. Place a backorder with a reputable catcher (DropCatch, SnapNames, NameJet) rather than attempting manual registration. The backorder fee is a small fraction of what a failed attempt will cost you in time, and the catcher infrastructure is the only realistic path to acquisition at release.

The expiration timeline looks, on a marketing slide, like a tidy lifecycle moving from grace to redemption to release. In the operational reality, it is a series of administrative choke points, each governed by a separate set of rules and each monetized by a different party. The registrant who pays attention to the fine print retains their name. The registrant who relies on auto-renew and good intentions provides inventory for the next auction cycle — which, depending on the registrar, may have already been scheduled before the renewal email was ever sent.