What actually happens when a domain expires

The moment people go looking for this information is almost always the same moment: the site is down, the renewal email is three weeks old and unread, and the question typed into a search bar is some version of "how screwed am I." So it is worth saying the true answer before the mechanics, because the true answer runs against the panic. You almost certainly have more time than the dead site suggests. The catch is that the extra time comes with an escalating price tag attached to it, and the escalation happens on a schedule nobody tells you about until you are already on it.

The site can go dark weeks before the domain is actually lost

The first thing that breaks is not the registration. It is resolution — the record that tells the internet which server to send visitors to. Registrars routinely stop pointing an unrenewed domain at your host, or park it on a holding page carrying ads for domain-related services, before the hard expiry date, sometimes the moment a renewal charge fails rather than waiting for the deadline itself. That gap between "the site is down" and "the domain is gone" is the single most common source of unnecessary panic in this whole process, because the two events look identical from the outside and are not remotely the same.

This is also why the fastest fix, when you catch it early, is boring: log into the registrar account and pay the renewal. If you are inside the grace window, that is genuinely all it takes. The site comes back once the DNS record is restored, on the same timetable as any other DNS change — not instant, but not a negotiation either. The guide to domains and hosting covers this directly: registering, hosting and pointing are three separate systems, and an expired domain is a registration problem that temporarily breaks the pointing, not a hosting problem. Your files are sitting untouched wherever they were.

If the site in question is a one-page site built through reach, this schedule has a wrinkle worth knowing before it matters. reach registers a custom domain in your name, one year at a time, with auto-renew off by default — so the expiry clock above only starts because a renewal decision genuinely wasn't made, not because a system defaulted you into a lapse. That is deliberate, but the responsibility for noticing still sits with you every year. Custom domains require Premium — $4.99 a month or $49 a year. Prices checked August 2026. Buying through reach is the only route to one: you cannot connect a domain you already own to a reach site, so a name registered somewhere else already plays out this whole mechanism at the other registrar. None of it touches the free yourname.joinreach.app subdomain, which carries no independent renewal date to forget.

The stages, in the order they actually happen

A domain that lapses does not go from "yours" to "gone" in one step. It moves through a sequence, and the sequence is where all the advantage in this article lives.

Expiry is the date on the record. Nothing dramatic happens on this date by itself beyond the resolution problems already described — it is a marker, not a cliff.

Grace period follows immediately. For most of the major generic extensions this runs several weeks, and during it the domain behaves, from a recovery standpoint, exactly like an ordinary renewal. You pay the normal renewal price, the registration extends, nothing else changes. This is the entire window in which the panic in that first search result is unwarranted.

Redemption period starts when the grace window closes without payment. The registry pulls the domain out of active status and hands it to the registrar in a locked state. It is still technically recoverable, but a normal renewal no longer works — recovery now requires a restoration request, and restoration is priced as a penalty rather than a service.

Pending delete is a short, fixed window — around five days is typical across the generic extensions — during which nothing can be done at all. Not by you, not by the registrar, not by anyone. The domain is frozen while the registry prepares to release it back into the general pool.

Drop is the release itself. The domain becomes available to register again, to anyone, first-come or through the auction and pre-registration mechanisms built specifically for this moment. Once a domain drops, "recovering it" stops being a recovery and becomes a fresh registration you are competing for like everyone else — which, for a name that ever had real traffic, is a genuinely competitive process rather than a formality.

Country-code extensions do not promise any of this. Some run shorter timetables, some skip redemption entirely, and a few delete on the expiry date itself. The generic extensions are the forgiving end of the spectrum, not the norm.

The redemption fee is where "more time than you think" turns punitive

Here is the sentence worth remembering out of the whole schedule above: the price does not rise gradually. It has one step, and the step is large. Inside the grace period you pay what you always would have paid. The moment redemption starts, the same domain costs a restoration fee set unilaterally by the registrar, and that figure is consistently described across the industry as an order of magnitude above the ordinary renewal price — not a late fee in the sense of ten or twenty percent tacked on, but a different pricing tier entirely, applied the instant the calendar crosses one specific line.

That structure is the whole argument of this article. The redemption fee is not compensation for work the registrar did — restoring a domain from redemption is a routine, largely automated action — it is priced as what it functionally is, which is the price of not having planned ahead, charged to someone with no standing to negotiate it down. Registrars vary in what they charge, which is one more reason the comparison of what registrars actually charge at renewal matters more than the signup price ever will: the same comparison logic applies to what they charge you back for a mistake, and the spread between providers is real.

The practical upshot is that the grace period is not a safety net you should plan to use. It is a safety net you should be glad exists and never need. Treat every day inside it as a day you already lost time you didn't have to lose, because the fee waiting at the far end of it is structured to make sure you notice.

Drop-catching exists because an expired name is not empty, it is inherited

A domain that never had traffic dropping quietly is not interesting to anyone. A domain that did — one with years of backlinks, an established search history, maybe an old audience still typing it into a browser out of habit — is a different situation entirely, and there is an industry built specifically around catching it the instant it drops.

Drop-catching services monitor the pending-delete queue for exactly this kind of domain and compete, often through automated high-speed registration attempts or pre-arranged auction systems, to grab it within seconds of release. What they are buying is not the string of characters. It is the accumulated authority attached to it — the links, the age, sometimes residual traffic from people who bookmarked the old site or still search the old brand name. None of that value belongs to you once the domain drops, even though you built it. This is also the mechanism behind names that look abandoned but are actually owned by someone who bought them this way on purpose, which is its own topic covered in buying a domain someone already owns — the flip side of this article, for the domain you want rather than the one you lost.

If your site gets any meaningful traffic or has any link history worth protecting, this is the argument for taking the grace period seriously rather than treating it as free insurance. The name you let lapse is not sitting there waiting patiently for you to notice. It is sitting in a queue that other people are watching more closely than you are.

Two settings decide whether you ever experience any of this

Everything above is avoidable, and it is avoidable through exactly two settings, both boring, both usually configured once and forgotten.

The first is auto-renew, and the thing worth checking is not whether it exists but whether it is actually on. Some sellers, including several website builders that resell domains, default it off as a deliberate consumer-protection choice — reasonable in principle, and the reason a surprising number of expirations happen to people who assumed the setting was already handled for them. Auto-renew paired with an expired card on file is functionally identical to having it switched off, so the setting and the payment method have to be checked together, not separately.

The second is the registrant email address on file — the one every expiry notice, renewal receipt and restoration warning actually goes to. An address at a job you might leave, a university account, or an inbox tied to a service you are only trialling is a single point of failure sitting quietly underneath an otherwise well-run site. Point it at an address that will still exist and still get checked in five years, and almost everything in the stage-by-stage schedule above becomes something you read about rather than something you live through.