The Domain That Lapsed

Picture a solo founder with a small SaaS product. The registrar's renewal reminder went to spam in April. The card on file expired in May. In June, the domain lapses.

With it goes everything attached to it: the landing page, the API the app calls, the status page, and the email. The registrar's increasingly urgent "final notice" messages now have nowhere to land, because they are addressed to a mailbox on the domain that just expired. The founder finds out from a message from a user: "hey, did you shut down?"

The product is not down in any normal sense. No restart, rollback or deploy will bring it back. The name it lives at has stopped pointing at it, and getting the name back follows the registry's timetable, not yours.

What breaks, and in what order

When a domain expires, the registrar usually changes its DNS straight away. Most often the name starts pointing at a parking page or a renewal notice. Sometimes it stops resolving at all. Either way:

• The website shows the registrar's page instead of yours, often with ads on it.
• The API stops answering. Clients see DNS failures or the registrar's HTML where they expected JSON.
• Email stops arriving. The mail records have gone, so messages to your domain bounce, and that includes password resets, invoices and the registrar's own notices.
• Everything that checks the domain starts failing. Single sign-on callbacks, webhooks sent to you and verification records all stop working.

DNS caching smooths the first few hours, because some resolvers keep serving the old records until they expire. That just makes it worse. Some people see the site and some don't, and the first reports sound like a random fault rather than an expired domain.

The recovery timeline

For most generic domains like .com, an expired name goes through stages before anyone else can register it. The exact lengths depend on the registry and the registrar, so treat these as typical rather than guaranteed:

Country-code domains, such as .de, .uk and .io, follow their own registries' rules, and some of those are much shorter or much stricter. Check your registrar's policy for each extension you own before you need it, not after.

Drop-catching is a real risk

A domain with traffic, backlinks and an existing email history is worth something to people who are not you. Drop-catching services watch for names entering pending delete and register them the moment they are released. Once someone else owns the name, getting it back means negotiating with them, or a dispute process that takes weeks and is not guaranteed to succeed.

Even short of that, the parking page that replaces your site can carry ads and links you did not choose. Search engines may notice the change, and recovering rankings after a lapse takes time.

If it has already happened

1. Log in to the registrar and renew right away. During the grace period this is usually a normal renewal. Check that payment actually went through.
2. If it is in redemption, pay for the restore. It is expensive, and it is still much cheaper than losing the name.
3. Check the DNS records once it is back. Most registrars restore them, but confirm that the web, API and mail records are correct before you announce anything.
4. Expect a lag. Resolvers that cached the parking-page answer keep serving it until its TTL runs out. How DNS works explains why.
5. Move the registrar contact off the domain so this can't lock itself in again.

Making sure it never gets that far

The reasons a domain lapses are mostly boring: a contact address nobody reads, an expired card, a reminder filed as promotions. Why registrar renewal emails end up in spam goes through them one by one. Fixing them helps, but the reliable fix is a warning that does not depend on the registrar's email at all.

Barkme reads the registration expiry date for every verified domain from the registry over RDAP once a day. It warns at 30, 14, 7 and 1 days before the domain lapses, sending each warning once, to the email, Slack, Telegram or webhook channels you chose. Because the warnings come from outside your domain, they still arrive when your own mail does not. When you renew, the next check picks up the new date and the countdown starts again.

If the name stops resolving, the uptime monitors on that domain fail and open an incident within minutes. A parking page that answers 200 is different. It looks up to any check that reads status codes, which is exactly why the expiry warnings need to arrive weeks earlier.

Domain monitoring and SSL alerts covers what Barkme checks and what each plan includes. The free domain health check shows when any domain's registration expires. The faster version of this story is the SSL certificate nobody renewed.