A domain registration has an end date. If nobody renews it, the domain does not disappear on that day, and it does not stay working either. It moves through a series of stages. At the start the website may already be gone. At the end the name can be registered by someone else.
This guide describes those stages for generic top-level domains such as .com, .net, and .org, which follow ICANN policy. Country-code domains set their own rules, and registrars add their own on top. Treat the lengths below as a typical pattern and check your registrar's terms for the real numbers.
The stages
| Stage | What happens | Visitors see | Can you renew? |
|---|---|---|---|
| Before expiry | Registrars send reminders | A working site | Yes, at the normal price |
| Just after expiry | Often a short hold. Some registrars show a parking page | A parking page, or nothing | Usually yes |
| DNS switched off | The domain stops resolving | "Server not found" | Yes, until the redemption stage |
| Redemption period | Held for restoration, about 30 days | "Server not found" | Only by restoring it, which may cost more |
| Pending delete | Last days before release. ICANN gives five calendar days | "Server not found" | No |
| Released | The name returns to the pool | Possibly someone else's site | No. Anyone can register it |
Before expiry
ICANN's policy for generic domains asks registrars to send at least two reminders before the end date, about a month and about a week ahead. The policy also asks for one more notice if the domain has not been renewed or deleted five days after expiry. These are emails. They work only if the contact address is read by someone.
After expiry, before DNS stops
What your registrar does in the first days differs. Some leave everything working for a while. Some switch the site to a page of their own. ICANN's policy says the registrar must allow renewal from the moment of expiry until the end of the period when DNS is switched off.
DNS switched off
The policy requires DNS to be switched off at some point after expiry, so that the domain stops pointing at the old website. From this point the website stops answering. Every service that depends on the name stops too: email, API endpoints, payment callbacks, and links in old messages.
Redemption period
During the Redemption Grace Period, ICANN's policy says the domain is not in DNS, a transfer is locked, and its state is visible in lookups. It lasts 30 days. The original owner can restore the domain through the registrar. Registrars commonly charge a restoration fee on top of the renewal, so ask before you start.
Pending delete
After redemption, the domain is queued for deletion. On its page of status codes, ICANN says a domain is removed from the registry about five calendar days after the redemption period ends. At this stage it can no longer be restored.
Released
Once the registry deletes the name, it can be registered by anyone. A name that people recognise, or that other sites link to, can be taken quickly by someone who watches for dropped domains. If you lose a domain this way, you can no longer get it back by paying. You can only try to buy it from its new owner.
Status codes you may meet
A lookup of a domain may show status values that match these stages. ICANN's page of EPP status codes describes them:
autoRenewPeriod: a short period after an automatic renewal.redemptionPeriod: the redemption stage.pendingDelete: the final days before release.clientHold: the registrar has stopped the domain from working in DNS. Reasons include a dispute, non-payment, or the lead-up to deletion.serverHold: the same, set by the registry.
A clientHold or serverHold on a domain you rely on is a reason to contact your registrar the same day.
What breaks first
A website is the visible part. The quieter casualties are often worse.
- Email. Messages sent to your domain bounce or are lost.
- Certificate renewal. Automatic renewal that proves control of the domain can fail.
- Login and payment callbacks. Services that call your domain get no answer.
- Search and links. Search engines and other sites see a dead address.
If it has already happened
- Open the registrar account and read the domain's status. It will show how far along the stages it is.
- Renew right away if the status allows it. Pay by a method that is certain to work.
- If it is in redemption, ask the registrar how to restore it and what it costs.
- Do not transfer it to another registrar while it is expired or in redemption. A transfer is locked in that stage.
- After recovery, check the zone. Records and name servers usually return, but confirm each one. See How to Troubleshoot DNS Resolution Errors.
- Check the certificate and the email after DNS is back.
- Fix the cause. Update the payment method, the contact address, and the automatic renewal setting.
How to avoid it
The prevention steps are in How to Check When a Domain Expires. In short: automatic renewal on, a valid payment method, a contact mailbox that someone reads, and a warning that does not depend on the registrar's emails.
How UptimeWire fits
UptimeWire checks the registration date of the domain behind each website once a day and warns you by email and Telegram before it expires, within the period you chose for that website. It sends one warning. It does not repeat it daily.
If the domain does expire and the name stops resolving, the ordinary website check starts to fail with a message that the domain name could not be resolved, and after three failed checks in a row an incident opens. That alert comes after the site is already down. The domain warning exists so that you never get that far.
If the registry does not publish an expiration date, the check shows unknown and sends no warning. UptimeWire does not renew or restore domains.