Domain expired and website is down

How an expiry takes the site down

When a domain expires, the registry stops publishing its record set. The entire domain stops answering: no web, no email, no other subdomain, while the site's hosting stays on. The timing varies by registry, but the universal order is:

1. Grace period (often 0 to 30 days, varies). The domain is already expired, the nameservers stop answering for it, and the whole site may work intermittently or stop entirely.
2. Redemption / action. The registrant can still restore, but usually at a restoration fee.
3. Release. The domain becomes available to register again by anyone.

The "domain expired" error message a visitor sees is not a website error at all, it is an ERR_NAME_NOT_RESOLVED at DNS, because the name no longer answers. The host and the files are untouched; the name is gone.

Confirm it is the domain

Before renewing, verify the symptom is the domain:

1. nslookup example.com returns NXDOMAIN or an error, while the hosting IP still answers a ping.
2. The site works if you point Hosts or hosts at the known IP, e.g. add 203.0.113.10 example.com to the hosts file and visit. If the site loads that way, the code is healthy and the domain is not.
3. Check the WHOIS: the expiry date appears and the status shows REDEMPTIONPERIOD or PENDINGDELETE, from any WHOIS tool.

The test with the hosts file also tells you the exact state: if the site loads on the IP but the world cannot find the name, the fix is 100% the domain.

Renew and restore

1. Log in to the registrar and open the domain's row. Look for "Renew" even if the period says expired.
2. If the registrar shows RESTORE or REACTIVATION, that is the redemption fee on top of the renewal; the flow is just paying both.
3. Renew for at least one additional year, and remove any reason to use the expiry period.
4. If you find the domain is in REDEMPTION and the registrar asks for the auth code, do not skip the nameserver transfer unless the intended new provider can handle the domain.

When the DNS is off after renewal

After renewal, the site may take up to a few hours to come back everywhere. The registry republishes the record set, but the TTL (time to live) of the old outage was long, so old resolvers keep failing while the new records spread.

• Confirm the records match the article dns-propagation-and-resolution: the A or CNAME that points to the host is present.
• Check the nameservers: if the domain was on registrar's own nameservers before expiry and gets moved, the site can work in some regions.
• Wait, do not re-register. Registering the same name again, for example with a spare domain, does not give you the old site, and automated drop-catchers can take the name instead of you.

The reverse scam

Between expiry and renewal, the domain may be parked or held by the registrar itself. If the renewal does not produce the site, the registrar's own page or a "domain auction" could be showing, and the correct action is a ticket, not a second registration.

Prevention

• Set auto-renew with a payment card that cannot fail and one backup method (the registrar's lock, auto payment).
• Lock the domain and keep the registrant email current so you always receive renewal notices.
• Record the expiry date in two calendars, one for the owners, and confirm it annually, so a renewal that cannot fail is simply a habit no one has to remember.
• If the domain supports the business for years, treat renewal as a fixed annual commitment rather than a discretionary spend.
• Monitor the WHOIS expiry monthly as part of the site health checklist.

When the domain went via a reseller or hosting panel

Domains bought inside a hosting plan sometimes expire inside that panel without a separate invoice. Once renewed in the panel, the site may still be down because the nameserver settings that point to the host were not restored: verify that the A and CNAME records and the TXT for email exist again.