BigFreeHost All articles
Opinion

Your Website Dies the Day Your Password Does

BigFreeHost
Your Website Dies the Day Your Password Does

Photo: Shixart1985, CC BY 2.0, via Wikimedia Commons

Here's a sequence of events that plays out more often than anyone in this industry likes to admit.

A small-business owner in Ohio — let's call her Dana, runs a two-person flower shop — has a stroke in February. She survives, but she's out of commission for four months. Her site sits on a free hosting plan attached to an email address she set up in 2019. Auto-renew on the domain hits a debit card that got replaced after a fraud alert. The card declines. The registrar sends three notices to an inbox nobody can open. Sixty days later the domain is in redemption. Ninety days after that, it's on the open market.

The flower shop is still there. The website is gone. And the Google Business Profile that used to point at it now points at a parked page selling somebody else's ads.

Nobody did anything wrong here, exactly. That's the part that should bother you.

Your site is not one thing. It's three.

Most people running a site on a free or near-free plan think of it as a single asset. It's really three separate pieces of property, each held by a different company, each with its own recovery process:

That third one is the quiet killer. If your domain email is your recovery address for the registrar, the host, your payment processor, and your analytics account, then the inbox is the master key to the whole estate. Lose the inbox and you don't just lose email. You lose the ability to prove you're you.

Why your next of kin can't simply call and ask

Hosts and registrars are bound by privacy rules and their own fraud departments. A spouse calling to ask for access to a deceased partner's account gets routed into the same process as a stranger calling to ask for access to your account — because from the outside, they look identical.

Some registrars do publish a deceased-registrant procedure. It usually means a death certificate, a notarized statement, sometimes a court order. It works, but it takes weeks to months, and it typically covers the domain only. Not the site. Not the inbox. Not the customer orders sitting in a database nobody can log into.

Transferring an account is vastly easier than recovering one. But transferring requires a login — which is the thing you didn't leave behind.

The one-page document that solves most of this

Call it a website will. It doesn't need a lawyer, a notary, or a subscription. It needs to be somewhere a trusted person can find it within a day, not a year.

What goes on it:

  1. Every account, by service name and the email address used to log in. Registrar, host, DNS provider, email provider, CDN, payment processor, analytics, SSL issuer, the page builder if it's separate.
  2. Where the two-factor backup codes live. Not the codes themselves on the same page — a pointer to where they are.
  3. Which payment card renews what, and when. A declined card is the single most common cause of a quiet site death.
  4. Where the backups are, and the one-paragraph instruction for restoring one.
  5. Who is authorized to act, and where the durable power of attorney and the will are stored.
  6. One conditional instruction. Something like: If I'm unreachable for 30 days, log in, keep the domain renewed, don't touch the content, and contact my attorney.

That last item is the whole point. It converts a mystery into a checklist.

Storing it without paying for anything

A few free or cheap options that actually work:

Pick two. Two is enough. One is not.

The customer-data wrinkle nobody mentions

If you take orders, run a newsletter, or store contact details, your hosting account also holds personal information about other people. Every US state now has a data breach notification law, and a handful — California most prominently — give consumers the right to demand deletion. An abandoned database on a suspended host isn't neutral. It's a liability with no owner.

So your one-pager should also say who is allowed to export the customer list, who is allowed to delete the account, and what happens to pending orders. That's not morbid. That's just bookkeeping.

Forty minutes, once

Set a timer. Sit down with your laptop. Write down every service that touches your site. Write down the login email for each. Write down the renewal date and the card. Print it. Put it somewhere that isn't your laptop.

Then tell one person where it is.

Nobody is going to thank you for this. There's no launch-day thrill in a document about account recovery. But the difference between a business that survives its founder's bad week and one that doesn't is usually not talent, capital, or hustle. It's whether somebody else knew the password.

All Articles

Related Articles

AI Website Builders Are Handing Out Free Sites — and Quietly Keeping the Receipts

AI Website Builders Are Handing Out Free Sites — and Quietly Keeping the Receipts

We Actually Read the Fine Print: What 12 Free Hosts Say They Can Do With Your Website

We Actually Read the Fine Print: What 12 Free Hosts Say They Can Do With Your Website

What 'Data Center Redundancy' Actually Means at a Budget Host (Spoiler: Probably Not What You Think)

What 'Data Center Redundancy' Actually Means at a Budget Host (Spoiler: Probably Not What You Think)