What to Do When Your Domain Expires or Gets Suspended

If your domain expired or was suspended, the first thing to establish is which phase you are actually in, because that determines whether you can fix it in minutes or whether you are now paying a registry to release it. The registrar's control panel usually shows one of a small set of states, and the state name maps to a stage in the shared lifecycle that every registry runs.

The lifecycle is roughly: active, expired (registrar grace period), redemption, pending delete, then released. The registrar grace period is the one you want. Renewal there is a normal renewal. Once the domain moves into redemption, the registry has taken it back from the registrar and you are asking for a restore, which is a different and slower operation. Pending delete is the last stage before the name returns to the pool, and there is no mechanism to pull it back from there.

How to tell whether the domain expired or was suspended

These are two different failures and they need different responses. An expiry is a billing and lifecycle problem. A suspension is usually a policy problem: unpaid invoice at the registrar, an abuse complaint, a whois accuracy hold, or a failure to respond to a verification email. A suspended domain still resolves at the DNS level in many cases, but the registry has set a client hold, which means the delegation is removed and resolvers stop answering for it.

Query the registry directly rather than trusting a browser. RDAP is the modern replacement for whois and returns structured JSON, which is easier to read and easier to script against.

curl -s https://rdap.example-registry.org/domain/example.com | \
  jq '{status: .status, events: .events}'
{
  "status": ["client hold"],
  "events": [
    { "eventAction": "registration", "eventDate": "..." },
    { "eventAction": "expiration",   "eventDate": "..." }
  ]
}

The status array is the part that matters. clientHold or client hold means the registrar has told the registry to stop publishing the delegation. serverHold means the registry itself has done so, which usually follows an abuse or legal action and is not something your registrar can lift on your behalf. redemptionPeriod means you are past grace. pendingDelete means the countdown to release has started.

For older tooling, the equivalent query is whois example.com, and the status lines appear near the top. The output format varies wildly between registries, so prefer RDAP where it is available.

What actually happens during grace, redemption and pending delete

During the registrar grace period, typically a few weeks but set by each registrar and by the registry's own policy, the domain stops resolving but is still yours. The nameservers are still recorded. If you renew, delegation comes back and you may not have to touch DNS at all. This is the cheap and boring outcome, and it is the one you want.

Redemption is the expensive and slow one. The registry has removed the domain from the registrar's account and parked it. To restore it, the registrar has to submit a restore request to the registry, and the registry charges the registrar a restore fee. Your registrar passes that on, usually with a markup, and the process can take days rather than minutes. The nameservers may or may not survive the round trip, so plan to re-enter them.

Pending delete is a fixed window, typically five days, during which nothing can be done. The domain is queued for release. When the window closes, it drops to the open market and anyone can register it. If the name has any commercial value, expect drop-catchers to be waiting, and expect them to be faster than you.

Confirming where you are before you pay anything

Do not pay a restore fee until you have confirmed the status is actually redemptionPeriod. Registrars sometimes surface a generic "expired" label in their UI while the registry record still shows the grace period, and paying the larger fee in that situation is a waste. Check RDAP first, then contact support with the status in hand.

Getting the site back with minimal downtime

If the domain was suspended rather than expired, renewal will not help. You need the hold lifted. That means resolving whatever triggered it: paying an outstanding balance, replying to the verification email the registrar sent, or responding to the abuse report. The registrar's support queue is the only path, and the registry will not act on your request directly because you are not their customer.

While the domain is unreachable, DNS queries for it fail. Depending on the negative TTL that resolvers cached, recovery is not instant even after delegation is restored. You can shorten this the next time by keeping your SOA minimum and negative caching values low, but you cannot retroactively shorten what is already cached.

If you need the site reachable during the outage, point the application at a fallback hostname you control. Users who still have the old domain cached will fail, but anyone arriving via the fallback will reach you. A simple server block makes this explicit:

server {
    listen 443 ssl;
    server_name fallback.example.net;
    location / {
        proxy_pass http://127.0.0.1:8080;
        proxy_set_header Host $host;
    }
}

Keep the backend identical so you are only changing the name users type, not the application. Once the domain is restored, add the original name back to server_name and let the fallback stay as a safety net.

Protecting mail and other records

Mail is the part people forget. If the domain lapses, MX records stop resolving and inbound mail bounces. Anything sent during the outage is usually lost, not queued, because the sending server cannot find an MX. Once the domain is back, verify that MX, SPF, DKIM and DMARC records are intact, then send a test message from an external account. If you use a third-party mail provider, check that their verification of domain ownership has not lapsed as well, since some providers re-check periodically and will stop relaying if the check fails.

What to do next

Check the RDAP status for every domain you are responsible for today, and put the expiry dates in a calendar that someone other than you will see. Turn on auto-renew where the registrar supports it, but do not treat that as sufficient, because a failed card or an expired payment method will silently break it. Keep registrar and registry contact addresses on a mailbox that is not hosted on the domain in question, so that a lapse does not also cut off the notifications telling you about the lapse. If the domain is already in redemption, contact your registrar's support directly, quote the registry status, and ask them to confirm the restore fee and timeline in writing before you authorise it.