Domain expired and the website is down: what do you do first?

Short answer: Log in to the registrar account that holds the domain and renew it right now. If it is still inside the grace period, the renewal usually brings the site back within minutes to a few hours, once DNS caches catch up. If the registrar says it has moved into redemption, you can often still get it back, but it tends to cost more and take longer. Tell the client before they find out themselves.

What actually happens when a domain expires?

Expiry is not one event. It is a sequence, and the exact lengths depend on the registrar and the extension (.com, .net, a country code). The pattern below is common for generic domains like .com, but it is a rule of thumb, not a guarantee. Your registrar's own policy page has the real numbers.

Registrars send notices to the email on the registrant record, which is often a former employee or the previous agency. That is why the warnings so often go unseen.

How do you confirm it is the domain and not the hosting?

Do this before you change anything on the server. Run these from a terminal:

whois clientdomain.com
dig clientdomain.com +short
dig clientdomain.com NS +short

In the WHOIS output, look at the Registry Expiry Date field and the status lines. A status of clientHold, redemptionPeriod or pendingDelete points at the domain itself. If dig returns nothing for the A record and the nameservers, the domain is not resolving at all, and nothing you do in WordPress or on the host will help. If the dates are fine and dig returns an IP, look at hosting, a firewall or an expired SSL certificate instead.

Here is a reproducible example you can run right now against a public domain. It asks the .com registry's RDAP service (the machine-readable successor to WHOIS, defined in RFC 9083) for the expiry event and status:

curl -s https://rdap.verisign.com/com/v1/domain/example.com | jq '.status, (.events[] | select(.eventAction=="expiration"))'

The output is a list of status strings, then an object shaped like {"eventAction": "expiration", "eventDate": "YYYY-MM-DDTHH:MM:SSZ"}. The date and statuses change over time, so run it yourself rather than trusting a copy here. For a lapsed domain, expect a status such as redemption period or pending delete instead of the usual prohibited-transfer statuses. This example uses a reserved public domain, not a quietwatch customer. We do not name client sites in articles.

What are the exact fix steps?

1. Find the registrar account. If you do not know where the domain lives, WHOIS names the registrar. If the client registered it themselves, ask them to reset the password or add you as a delegate.
2. Renew for more than one year. Two to five years removes the next scare. Turn on auto-renew and add a payment method that is not about to expire.
3. If the registrar shows it as redemption, pay the restore fee. Do not wait for the price to drop. It will not, and the pending delete window is short.
4. Check the nameservers. Some registrars reset them to parking servers during expiry. Set them back to the host or to Cloudflare.
5. Check the records at the DNS host. They usually survive, but confirm A, CNAME, MX and TXT (SPF, DKIM) are all present. Cloudflare's setup documentation describes a zone as active only once the domain's nameservers point to Cloudflare, so check the zone status in your dashboard.
6. Wait for propagation, then test the site, the www version, and send a test email both ways.
7. Update the registrant email to a shared address the agency controls, so the next warning does not vanish.

Will an expired domain hurt Google rankings?

A short outage usually does not, but we cannot promise it. Google Search Central has a page on HTTP status codes and network and DNS errors. As we read it, DNS and network failures are treated as crawl problems: Googlebot retries, may slow its crawling, and URLs that keep failing can eventually drop out of the index. The page does not give a fixed number of days, so treat any deadline you read elsewhere as a guess. The practical point is that risk grows with the length of the outage. Hours are rarely a problem. Weeks of DNS failure can lead to pages falling out of the index, and recovery after that takes time.

After the site is back, open the Crawl Stats report in Search Console and look for DNS errors and server connectivity failures in the days around the expiry. Then request indexing for the home page and key pages. If the domain was lost and re-registered by someone else, that is a different and much harder problem, because the history and links no longer belong to your client.

What do you tell the client?

Keep it short and factual:

• What happened: the domain registration lapsed on a specific date, so the site and email stopped resolving.
• What is fixed: renewed today for a set number of years, auto-renew is on, DNS is restored.
• What it cost: the renewal, plus any restore fee, with the amounts.
• What you are watching: Search Console crawl errors and email delivery for the next week.
• What changes: reminders now go to a shared address, and expiry dates are tracked.

Do not blame the client's old email or the previous agency in writing. Fix the process and say so.

How do you stop it happening again?

Write every client domain's expiry date down in one place, and check it on a schedule instead of trusting registrar emails. For a quick one-off look at a domain or its certificate, use the domain and SSL expiry checker. SSL certificates expire separately from domains, so a domain renewal does not renew a certificate. Both need a date on your calendar.

How does quietwatch catch this every day?

quietwatch checks domain and certificate expiry on every client site once a day and warns you well before the date, along with what quietwatch checks every day for noindex, robots.txt and sitemap problems. The free tool above is the place to start if you want to see where your client domains stand today.

Sources

• Google Search Central: HTTP status codes, and network and DNS errors (crawl behavior during DNS and network failures)
• Cloudflare docs: Full DNS setup and nameserver activation (zone activation and nameservers)
• RFC 9083: JSON Responses for the Registration Data Access Protocol (RDAP) (the status and expiration event fields in the example)

All posts · The fourteen checks