Domain and hosting problems that take a website down

Most website problems are visible while the site is still up: a slow homepage, a form that silently fails, a page that looks wrong on a phone. Domain and hosting problems that take a website down are a different kind of fault. There is no degraded version to notice, just a domain that resolves one day and doesn't the next, or a server that stops answering because an invoice went unpaid. For a local business, that usually means the phone stops ringing and nobody can say why, because there is nothing left on screen to point at.

How a domain actually goes down

A domain name is a subscription, renewed annually or every few years, and it lapses the same way any other subscription does: the card on file expires, the renewal email goes to an inbox nobody checks any more, or the person who registered it on the business's behalf has long since moved on. Most registrars give a grace period after expiry, often a few weeks, before the domain drops and becomes available for anyone to register again. Once that happens the business doesn't just lose the website. If email runs through the same domain, which it often does for a small business, every enquiry, invoice and reply stops arriving too, and nobody finds out until a client rings to ask why they never heard back.

The ownership problem hiding underneath

The more common version of this isn't neglect, it's ownership. A huge number of small business domains were registered years ago by whoever built the original site: a freelancer, a nephew, an agency that has since closed. The domain sits in that person's registrar account, renewed automatically on a card that still works, and the business owner has no login, no visibility and no idea the arrangement is fragile. It works fine for years, right up until the person who registered it loses the card, ignores a renewal notice, or simply stops paying for something they no longer have a reason to maintain. A WHOIS lookup on the domain shows who is actually listed as the registrant, and it is worth running one before you take on any audit or rebuild, because “who owns this domain” is a question most business owners have never had to ask themselves.

Hosting lapses look different but cost the same

Hosting fails for similar reasons: an expired card, an account flagged for non-payment, a free trial that quietly ended. The difference is that a hosting lapse can be partial in a way a domain lapse usually isn't. Sometimes the site goes fully dark. More often the host suspends the account and replaces the site with a generic holding page, which is arguably worse, because the domain still resolves and the business still looks findable, right up until someone actually clicks through and finds a placeholder page with no phone number on it. If you're running an audit and the homepage shows a bare hosting-provider template rather than the business's own site, that's the sign to check, not assume it's a one-off glitch.

What to check before it becomes a crisis

None of this needs specialist tools to check. A WHOIS lookup shows the registrant and the expiry date. Most registrars will also show a public expiry date even with ownership privacy switched on, and a domain expiring within the next few months is worth flagging on its own, separate from anything else in an audit. For hosting, there isn't a clean external check, but a few signs are worth watching for during a normal site review: an SSL certificate approaching its own expiry (a good companion check to run alongside this one, covered in the quiet cost of a website with no SSL certificate), a site that has clearly not been touched or updated in years, or a business owner who, when you ask, genuinely doesn't know who pays for their hosting or domain. Any one of those is worth a direct question before you build anything on top of it.

The fix is boring, which is why it gets skipped

Sorting this out isn't technically difficult. Transfer or register the domain into an account the business itself controls, with its own card and its own login details written down somewhere that survives a change of web designer. Turn on auto-renew, and add a second contact email that isn't tied to one person who might leave. Do the same for hosting: make sure the account is in the business's name, on a payment method someone checks, with a renewal date that isn't a surprise. None of this is exciting work and it rarely gets raised until something has already gone wrong, which is exactly why it's worth raising early, as part of an onboarding conversation rather than an emergency call.

This is one of the findings that doesn't show up neatly in an automated audit, because a domain that is still up today gives no outward sign that it might not be next month. Patchscout's audit still catches the symptoms that tend to travel with it, an SSL certificate on its way out, a site that hasn't been rebuilt in years, so a business with this problem brewing often shows up as worth a second look for other reasons first.

The three free searches at app.patchscout.co.uk/signup are enough to see whether that kind of audit turns up prospects worth asking the ownership question of.