The Host's Casebook / The blogger and the vanishing domain

The blogger and the vanishing domain

CASEBOOK

6 min read · 1,234 words

A note on authenticity. This is a composite story written by the editors, built from situations that come up again and again. It is not the account of a particular named person or business. Real reader stories go through the submission page and are marked as reader-submitted.

A food blogger had run her recipe site for six years. It had a modest but loyal readership, a few hundred posts, and a steady trickle of search traffic that paid for her flour and a little more. Her domain had been set to renew automatically every year, using a card on file at the registrar. She thought of it as a thing that happened by itself, like the electricity.

In the spring her bank replaced her card after a fraud alert. She updated the new details with the places she remembered: her streaming subscriptions, her phone contract, the hosting company. She did not update the registrar, because the registrar was not a place she ever visited. The old card number stayed on file there, and when the renewal date arrived the payment failed without a sound.

The notices she never saw

The registrar did what registrars do. It sent a reminder sixty days before expiry, another thirty days before, and a failed-payment notice on the day itself. All of them went to the contact address on the domain registration. That was an old address, from the week she registered the domain, belonging to an email account she had opened for the purpose and then stopped reading. It was not tied to her hosting login and she had no reason to open it.

Meanwhile the site carried on working. This is the part that fools people. When a domain expires, the registry does not delete it that minute, and for a time the site can appear untouched. Then comes a change: the registrar's own default page may replace the site, or the nameservers may be pointed to a parking server, or in some cases the site keeps loading for a few days while the domain sits in a grace period.

Her first sign was a reader message saying the blog was showing adverts for a payday loan company. That was the parking page.

What happens to a domain nobody renews

The lifecycle varies between top-level domains and registrars, so treat these as typical rather than fixed. The shape is the same almost everywhere.

Activepaid upGrace perioddays to weeksnormal feeRedemptionabout 30 dayshigh restore feePendingdeletefew daysReleasedanyoneTypical for many generic domains; country domains differ. Check your own registry's rules.
The period in which an owner can pay is short, and the price rises at each step.

In the grace period, the owner can usually renew at the ordinary price, sometimes with a small late fee. After that, many registries move the domain into a redemption period, where it can still be recovered, but only through the registrar and with a much larger fee, which the registrar passes on. Next comes a short pending-delete stage in which nothing at all can be done. Then the name is released, and anyone can register it.

Why the contact address mattered most

Every registration carries contact details, and the registrar's notices go to the registrant email. Since the rules on contact verification tightened some years ago, registrars also send a verification message whenever the registrant address is first set or changed, and may suspend a domain that stays unverified. She had once clicked such a link, years ago, and then forgotten the address existed.

The lesson is mechanical rather than moral. Hosting company mail, registrar mail, payment mail and security alerts all go to different addresses in most people's lives, and each address has its own reason to be forgotten. A registrar address that depends on a free mailbox you rarely open is a single point of failure for the whole site. The fix takes five minutes: change the registrant email to one you read, wait for the verification message, click it, and send yourself a test notice if the registrar offers one.

The race she lost

A released name does not sit waiting. A whole industry watches the deletion lists and registers any domain with a track record: age, inbound links, search traffic. Software places orders in the first moments after release, sometimes through several competing registrars at once. A domain with six years of food-related content is exactly what these services look for.

By the time she realised what had happened, her domain had passed through its stages without her seeing a single message, and it had been registered by an automated service within hours of release. She could see the new owner's page when she typed her old address. It carried adverts, and below them a line saying the name was for sale.

If you see your domain in the hands of a stranger, do not panic-pay the first price on the page. Look at the registration record, check who the registrar is, and think before you reply to anyone. Sellers of recovered names know exactly how much the name matters to its old owner.

Buying it back

She did buy it back, through the broker that the owner named, and the price was several hundred times the registration fee she had paid each year. The negotiation took two weeks. In that time her posts were gone from the web. Her search traffic fell to nothing, and when the name came back and the site was rebuilt from backup, rankings recovered over weeks, not days.

Stage at which she actsTypical costEffect on the site
Before expiryNormal renewal feeNone
Grace periodRenewal, possibly a small late feePossible brief parking page
RedemptionRenewal plus a restoration feeSite offline, easy to recover
After releaseWhatever the new owner asksSite offline, may never return

The figures in her case were illustrative of the pattern, not a quote: restore fees at the redemption stage are usually a modest multiple of renewal, while a market price after capture has no ceiling at all.

Rebuilding after the recovery

Getting the name back was only part of the job. DNS had to be put back as it was, and that meant finding the records. She had a hosting control panel with the zone, but the nameservers at the registrar had been reset during the lapse, so she had to point them at her host again. The email on that domain, which she used for her recipe newsletter replies, had been silent throughout. Messages sent to her during that fortnight had bounced, with senders getting an error.

Nameserversreset at hostDNS recordsA, MX, TXTCertificatereissue, HTTPSEmailtest both waysSearchre-verify
Recovering the name is the first step of five.

She walked through them in order, tested the site with curl -I, sent test emails in both directions, and re-verified the site in the search tool. Rankings crept back over about two months.

The new routine

She changed four things, none of which cost any money.

Domains can also be locked, which blocks unauthorised transfers. That does nothing for a lapse, but it is a useful companion setting.

What stayed with them

A domain is a rented name, and the rent is collected by a system that only knows your card and your inbox. Keep both current, and put the renewal date where a human will see it.

PreviousThe shop that moved on a Friday afternoonNextThe portfolio with a certificate warning

More from The Host's Casebook

Composite case

The developer and the leaked key

A freelance developer committed a configuration file to a public code repository. It contained the database...

Composite case

The band that lost its mailing list

A local band collected email addresses at gigs with a paper sheet and typed them into a plugin on their...

Composite case

The agency and the staging site that got indexed

A small web agency built a client's new site on a staging subdomain. When the client approved it, the agency...