Your website
What happens if my domain expires?
The short answer
Nothing happens all at once. A domain that expires moves through named registry states, and one of them exists specifically so the name can be restored. It is not available to anyone else during that time. What the standard deliberately does not say is how long you get, because each registry sets that itself.
An expired domain does not evaporate at midnight. It enters a documented sequence of states, and one of those states exists for no other purpose than letting you undo this.
The sequence is published in an internet standard rather than invented by your registrar. That matters, because it means you can check what is true instead of taking a sales email at its word.
What the standard does not give you is a deadline. That part is left to whoever runs the registry, and it is the single most common thing people get wrong about expiry.
One of the states exists purely so you can undo this
The domain does not go straight to available. It moves through a defined path.
RFC 3915 names the state that matters and says what it is for: "redemptionPeriod: This status value is used to describe a domain for which a <delete> command has been received, but the domain has not yet been purged because an opportunity exists to restore the domain and abort the deletion process."
Read that carefully. The domain is not deleted. It is held, deliberately, with an opportunity to reverse the deletion built into the design.
If nothing happens, the path continues. The standard describes the end of it plainly: "The domain name is purged once the pending delete period elapses", and then "The domain name is available for re-registration."
So there are three genuinely different situations, and people collapse them into one word. The name has lapsed but is recoverable. The name is in final processing and is not recoverable. The name is gone and anyone may register it. Only the third is what most people mean by expired, and it is the last of the three to arrive.
There is also a stage before any of this, and it explains the case that baffles people most: the domain that looked renewed and disappeared anyway.
RFC 3915 describes it: "autoRenewPeriod: This grace period is provided after a domain name registration period expires and is extended (renewed) automatically by the registry. If the domain name is deleted by the registrar during this period, the registry provides a credit to the registrar for the cost of the renewal."
So the registry may renew the name automatically while the registrar can still delete it and be refunded. A domain can show as renewed at one layer and be surrendered at another, which is why the status a registrar shows you is worth less than the status the registry holds.
The standard sets no deadline, and that is the point
Here is the part worth knowing before you read a number anywhere else.
RFC 3915 states the duration the same way twice. Of the redemption state: "The domain name remains in this state for a period of time defined by the Registry." And of the final state, again, a period defined by the registry.
So the standard specifies the states and refuses to specify the clock. Any figure you are quoted, thirty days or otherwise, is a registry policy for one particular kind of name, not a universal rule.
That has a practical consequence. If your domain has lapsed, the honest answer to how long you have is not a number from an article. It is a number your registrar or the registry publishes for that specific extension. Two domains in the same account can sit under different registries with different windows.
Be precise about what this source does and does not tell you. RFC 3915 is a protocol specification. It tells you the states exist and that registries own the timing. It says nothing about pricing, and restoration fees are typically far above a renewal.
Restoring is a procedure, not a button
This is where the delay usually comes from, and it surprises people who expect to pay and be done.
The standard describes a state in the middle of the restore: "pendingRestore: This status value is used to describe a domain that is in the process of being restored after being in the redemptionPeriod state."
It is not instantaneous because paperwork is part of the design. After a restore is requested, "the Registry waits to receive a restore report from the registrar for a period of time defined by the Registry."
Two things follow. The request goes through your registrar rather than around it, so whoever holds the account has to act. And if the report does not arrive, the standard sends the domain back to the redemption state rather than completing the restore.
The lesson for a business is about access rather than money. If the person who controls the registrar login is unreachable, the fee is not your problem. The signature is.
Your search presence runs on a clock nobody can hurry
The name is recoverable on a defined path. Your position in search is not, and Google is unusually blunt about it.
Its guidance on taking a site offline calls it "an extreme measure that should only be taken for a very short period of time (a few days at most)".
On recovery it removes any hope of a fast fix: there is no "fixed time for a recovery from a complete removal", and no mechanism to speed that up. Google also warns that "Ramping back up after a prolonged period of time will be significantly harder if your website needs to be reindexed first."
The disappearance itself is documented too. For pages that return client errors, "URLs that are already indexed and return a 4xx status code are removed from the index."
There is an administrative sting as well: "Search Console verification will fail, and you will lose all access to information about your business in Search." So the period when you most want data is the period you cannot see any.
Put the two processes side by side. The registry gives you a defined window and a defined procedure. Search gives you neither, and it is the one you cannot buy back.
What to check, in order
Five checks, and the first four are free.
- Find out which state the name is actually in, rather than assuming. Lapsed, in redemption, in final processing and released are four different answers with four different options.
- Get the window for that specific extension from the registry or registrar, not from an article. The standard deliberately leaves it to them.
- Confirm who can sign. Restoration runs through the registrar account, so the blocker is usually access rather than cost.
- Check what your site is returning to visitors and crawlers in the meantime, because that determines what happens to your indexing rather than the domain status does.
- Set renewal to automatic afterwards, and put the payment card expiry in the same calendar note. A lapsed card is the most common cause of a lapsed domain.
Work the exposure out rather than guessing at it, because the shape is counterintuitive. Suppose a business gets most of its enquiries through search and the domain lapses for three weeks before anyone notices. The registry side is bounded: there is a window, a fee and a procedure, and you can find out today exactly what each one is.
The search side has no published duration at all. Google says recovery from a complete removal has no fixed time and no way to accelerate it. So the recoverable part is the part with a price tag, and the expensive part is the one nobody will quote you. The three weeks is an illustration, but the asymmetry is the thing to remember: the bounded cost is visible, and the unbounded one is not.
Keeping renewals, DNS and hosting in view so a lapse never happens quietly is part of what we do on websites.
Terms used on this page
Sources
- RFC 3915, Domain Registry Grace Period Mapping for EPP (RFC Editor, Standards Track)
- Temporarily pause or disable a website (Google Search Central)
- How HTTP status codes affect Google's crawlers (Google Search Central)
Last reviewed 2026-09-11.