DOMAIN EXPIRY
A domain does not warn you. It works for years, and then on one specific morning the registry stops publishing its records and your website and your email stop in the same moment.
Almost everything written about this is either a registrar telling you to renew, or a reseller trying to sell you the domain afterwards. Neither explains what actually happens, how long you really have, or why organised businesses lose domains more often than disorganised ones.
This guide covers the whole sequence, from the notice nobody read to the moment recovery stops being possible.
In this guide you will learn:
The registry, the registrar, and why the two disagree about the date.
From the moment records stop publishing to the moment anyone can register it.
Contact addresses, expired cards, and the failure of absence.
gTLDs, Nominet, DENIC and the rest do not agree on anything here.
Grace, redemption, release, and the point where price stops being the issue.
Drop-catching, and what makes a domain worth catching.
The three changes that work, and the four that only feel like they do.
Why the renewal date belongs somewhere other than a registrar email.
Chapter 1
The registry, the registrar, and why the two disagree about the date.
Your domain has an expiry date at the registry, which is the authoritative record every resolver on the internet acts on. It also has a date in your registrar's control panel, which is what you see when you log in.
Most of the time these agree. Around renewals, failed payments and transfers they do not, and the gap between them is where most confusion about domain expiry lives.
At the moment of expiry the registry stops publishing the domain's delegation. Not the website, not the mail server, not anything you control. The pointer that tells the internet where to look for your nameservers simply stops being served.
The consequence is that your website and your email stop in the same instant, because both depend on the same delegation. Your server is still running. Your mailboxes still exist. Everything is intact and unreachable.
From the registrar's point of view the domain is not gone. It has entered a period during which they can still take your money and restore it, so their interface describes it as expired-but-recoverable rather than as offline.
From everyone else's point of view it is already gone, because the registry stopped answering. Both descriptions are accurate and they lead to opposite conclusions about how urgent the situation is.
Trust the registry date, not the panel. A lookup against the registry tells you what the rest of the internet believes, and that is the only date that determines whether your customers can reach you.
Chapter 2
From the moment records stop publishing to the moment anyone can register it.
The delegation stops being published. Lookups fail. The site becomes unreachable and inbound mail starts bouncing at the sender's end, which means your correspondents see a delivery failure and you see nothing at all.
This is the window where the wrong thing usually gets investigated. The registrar panel says active, the server is up, and the obvious conclusion is that the problem is somewhere in hosting. It is not.
If a domain has stopped resolving and you have not made a DNS change, check the registry expiry date before anything else. It takes ten seconds and it is the single most common cause.
Most registrars offer a period during which you can renew at the ordinary price. The length varies far more than people expect: generous at some registrars, close to nothing at others, and set by the registrar rather than the registry for generic extensions.
Throughout all of this the domain is still not resolving. You are not in a comfortable grace period. You are offline with an option to recover.
Redemption. The domain is still recoverable but the fee rises sharply, typically to somewhere between eighty and two hundred against a renewal of ten or fifteen. The process slows down too, often requiring a support ticket rather than a button.
Pending delete. Nothing can be done. The domain is queued for release and the outcome is already fixed regardless of what you are willing to pay.
The domain returns to the available pool and anyone can register it. In practice this is not a scramble among interested humans; it is automated services that monitor the release queue, which is covered properly in chapter six.
Chapter 3
Contact addresses, expired cards, and the failure of absence.
They are not the reason domains lapse. The address the warnings arrive at is.
To the registrant contact, which is whoever registered the domain. For a business of any age that is frequently a person who has left, an agency the relationship with ended, or a personal address belonging to someone who now ignores anything from that registrar.
More often than it should be, the contact address is at the very domain that is about to expire. When the domain lapses the mailbox stops too, so the escalating warnings arrive nowhere at all.
The other common cause is more mundane. Auto-renew is switched on, everybody relaxes, and three years later the card is reissued and the charge silently fails. The registrar emails about it, to the same address as everything else.
Nobody thinks of a domain registrar when updating payment details, because the charge is annual and small enough to be invisible on a statement.
Noticing that something has arrived is easy. Noticing that something stopped arriving is close to impossible without a system, because there is no moment at which it happens.
The reassuring auto-renew confirmations simply stop appearing, and an absence has no timestamp. This is the same reason broken mail authentication runs for months: silence is not an event.
It is tempting to assume domain lapses happen to businesses that are generally disorganised. It is largely the opposite.
A one-person business usually has the domain on the owner's own account, paid on the owner's own card, with notices arriving at an address they read. Fragile in other ways, but the person and the process are the same entity.
A business with staff turnover and multiple suppliers has more places for the thread to break. Every handover is an opportunity for something that was working to stop being anyone's job, and this particular responsibility was never assigned to anyone in the first place.
Chapter 4
gTLDs, Nominet, DENIC and the rest do not agree on anything here.
Almost everything written about domain expiry describes the generic extension model: auto-renew grace, then redemption, then pending delete. That model is accurate for .com and .net and misleading everywhere else.
The familiar sequence. Grace at ordinary price, redemption at a substantially higher fee, a short queue, then release. Total time from expiry to availability is generally more than two months, and the grace period length is set by your registrar rather than the registry.
A different process entirely. The domain is suspended at expiry and held in a protected state before release, and that protected period is generally longer than the generic redemption window. Fees are usually lower too.
Nominet also records the registrant separately from the registrar, which matters enormously when the account is held by a former supplier. You can see and update ownership through Nominet directly.
The important one to know about, because the assumptions from .com are wrong here in an expensive direction. There is effectively no comfortable grace period. A domain that is not renewed enters a transit state, and if nobody takes it, it is deleted.
Treat the expiry date on a .de as the actual deadline.
Several European registries use a quarantine model instead: .eu, .nl and .be among them. The domain stops resolving at expiry but remains reclaimable for a defined period, often around forty days, usually at modest cost.
Note that the site and mail are down for the whole quarantine regardless of how generous the window is.
Some registries attach conditions to holding a domain at all. .eu requires a connection to the EU or EEA. .com.au ties the licence to a current Australian business registration. .ca has Canadian presence requirements.
These can cost you a domain independently of renewal, when a corporate restructure or a relocation changes your eligibility and nobody connects the two events.
Chapter 5
Grace, redemption, release, and the point where price stops being the issue.
Renewal is the cheapest thing you will ever do about a domain, and every subsequent stage is more expensive than the one before it.
The first three rows are inconvenient. The fourth is a different category, because you are no longer dealing with a registrar operating a published process. You are negotiating with a person who owns something you need, and they know you need it.
Businesses that have traded at the same address for a decade sometimes find there is no route back at any price. Every printed card, every vehicle, every link from a supplier, every email address for every member of staff, all pointing at something you no longer control.
The recovery fee is usually the smallest part. The larger costs are the days offline, the mail that bounced without you knowing, the customers who tried to reach you and concluded you had closed, and the staff time spent working out what happened.
None of those produce a number, which is precisely why this failure is systematically underestimated before it happens and vividly remembered afterwards.
Chapter 6
Drop-catching, and what makes a domain worth catching.
Expired domains are not found by people looking for a good name. They are found by automated services that monitor the release queue and register anything matching their criteria within moments of it becoming available.
This is an established industry with real infrastructure behind it, and it operates at a speed no human can compete with.
An established small business domain scores well on all four, which is exactly the profile these services target.
Usually one of three things. It is parked with advertising, monetising the traffic that still arrives. It is listed for resale at a price reflecting what the new owner thinks you will pay. Or, occasionally, it is used to send mail from your former address, which is the outcome worth being genuinely worried about.
Chapter 7
The three changes that work, and the four that only feel like they do.
Not a personal address, and not an address at the domain in question. A role address at a domain you control separately, forwarding to somebody who reads it. This is the single highest-value change on the list because it fixes the most common failure directly.
Auto-renew is not a safety net if the card behind it expired two years ago. Put a recurring reminder against the card rather than against the domain, because cards are reissued on a cycle nobody tracks.
This is the point of the whole exercise. The registrar's notice is a channel that has already demonstrated it can fail. A date recorded independently of that channel is what makes the failure survivable.
It costs nothing, takes a minute, and closes a separate category of problem. It will not stop a lapse, but you are already logged in.
Chapter 8
Why the renewal date belongs somewhere other than a registrar email.
Everything in this guide comes back to one structural fact: the information that would have prevented the failure existed, and it existed in a channel that failed.
A renewal notice is not a record. It is a message, addressed to a specific person, delivered once, to an inbox that may no longer be read. Records do not have those properties.
Which registrar holds each domain, when it renews, which account it sits on, and which card pays for it. Four facts, written somewhere that outlives the person who wrote them.
That is genuinely enough to prevent almost every lapse described in this guide, and almost nobody has it, because assembling it was never anybody's task.
Check yours
Everything in this guide, checked on your domain in about ten seconds. Free, no account, every finding shown in full.