Websites

How to Recover a Website That Has Gone Offline

Website down after an expired domain, a closed hosting account or a missing supplier? A calm, step-by-step guide to finding out what happened and getting it back.

A business website can disappear for surprisingly ordinary reasons: a renewal payment fails, a hosting account is closed, a platform subscription lapses, or the person who built the site is no longer reachable. The good news is that a website is rarely lost completely. The work is to find out exactly what failed and what survives.

1. Work out what has actually failed

A website depends on three separate things. Check each one.

  • The domain. Is the registration still active? Look up the domain’s registration details and expiry date. An expired domain usually goes through grace and redemption periods before it can be registered by someone else, so act quickly.
  • The DNS. Is the domain still pointing to the right place? If DNS records were removed or changed, the site can be intact but unreachable.
  • The hosting or platform. Is the account still open and paid? Has the site been suspended?

The error a visitor sees often hints at which one failed: a “site can’t be reached” message usually points to the domain or DNS, while a platform or hosting error page points to the account.

2. Regain access to the accounts

Find out who holds the registrar, DNS and hosting accounts. If it was a former supplier or employee, gather proof of ownership, such as invoices, business registration documents and email records, and contact the provider. Providers have processes for this, but they take time, so start early.

3. Find out what content survives

In rough order of usefulness:

  1. The original platform or hosting account, if it can be reactivated.
  2. Backups, whether made by the host, a plugin or a past supplier.
  3. Exports made at any point, and the original files: images, documents and text.
  4. Public web archives, such as the Internet Archive’s Wayback Machine, which may hold copies of past versions of public pages. Coverage varies, and images and functionality are often incomplete, but they can recover text and structure.
  5. Search engines’ and social media copies of text and images, as a last resort.

4. Decide: restore or rebuild

If the original site can be reactivated or restored from a backup, that is usually fastest. If not, rebuild using the recovered content, ideally on a platform and hosting where the business controls every account. Keep the same page addresses wherever possible, so search rankings and links from other sites still work.

5. Make sure it cannot happen again

  • Keep the domain, DNS and hosting in accounts owned by the business, with more than one person able to log in.
  • Turn on automatic renewal and keep payment details current.
  • Keep regular backups somewhere separate from the host.
  • Record who your suppliers are and what they look after.

Need help?

Recovering a website is part investigation, part rebuild. If your website has gone offline, see website migration and recovery.

Related projects

Confidential client

Halcyon (pseudonym)

Moving a client's website off SmugMug and its high running costs, and getting the website restored at its own domain.

Read the case study →

Have an operational problem worth solving?

Tell me what is slowing your team down and which systems you use today. You do not need a technical specification: describing the problem is enough to start.

Discuss a project