Your web designer stopped responding. Here's how to get your website back.

It usually starts small. You email about a phone number that needs changing and don't hear back for a week. Then two. Then the emails stop being answered at all, and you realise you don't actually know where your website lives, who's paying for it, or how to get into it.

This happens constantly and it is almost never dramatic. People change jobs, get sick, burn out, take a full-time role, or just quietly stop doing freelance work. The site keeps running because hosting is on autopay somewhere. Nothing breaks until something needs to change — or until a card expires.

Here's how to work out where you stand and get control back. Do it in this order, because the order matters.

Before anything else: find out when the domain expires

Everything else can wait a week. This can't.

Go to lookup.icann.org and look up your domain. Note the expiry date and the registrar. If the expiry is close and you can't get into the account, that is now the most urgent problem you have — when a domain lapses, the website goes dark and so does every email address on it.

Step 1 — Work out what you're missing

There are five separate things, and people who've never been through this tend to assume they're one thing. They're not, and they can each be in a different place.

• The domain — the name itself, at a registrar
• The hosting — the server the site actually runs on
• The DNS — the settings that point the domain at the host and route your email
• The website files — the actual code, images, and content
• The email — often a completely separate service from all of the above

Write down which of these you currently have a login for. That list is your real starting position.

Step 2 — Find out where things are, without needing anyone's help

You can learn most of this from public records and your own bank statements.

Where the domain is

The ICANN lookup above tells you the registrar and the name servers. The name servers are the clue to who's hosting you — if they say something like ns1.bluehost.com, your host is Bluehost.

Where the hosting is

If the name servers didn't make it obvious, look at your card statements and bank records for recurring charges. Hosting is usually $5–$40 a month or a lump sum once a year. Search two or three years back — annual charges are easy to miss.

If the charges are on your card, you're in better shape than you think. Call the company and explain you're the account holder and need to recover access. They'll have an identity verification process.

If the charges aren't on your card, your designer is paying for it, which means you're on their account, and that's the situation you need to resolve.

Where the email is

Check the MX records for your domain using any free DNS lookup tool. They'll say google.com (Google Workspace), outlook.com (Microsoft 365), or your host. That tells you who to contact about email — and email is usually the thing people care most about recovering.

Step 3 — Make one clear, easy-to-answer request

If you can still reach the person, don't send a long email about how disappointed you are. Send a short one that's easy to say yes to. People who've gone quiet are often embarrassed, and embarrassment makes people avoid, not respond.

Give them a way out that doesn't require an apology. You want the credentials, not an admission.

If there's no response at all

Send one more, plainly, with a date on it: "If I don't hear back by the 15th I'll go directly to the registrar and the host to recover the accounts. I'd rather do it with you." Then do exactly that. Registrars and hosts both have account recovery processes for business owners in this position — you'll typically need incorporation documents, a matching ID, and proof you've been paying.

Step 4 — Get a copy of the site while you still can

Even if you're locked out of everything, the public version of your website is, by definition, public. Any competent developer can pull down a copy of a static site in an hour. It won't include a database if you have one, and it won't include the original editable files, but it preserves your content, your text, and your images — which is usually what actually took the time.

Do this early. It costs almost nothing and it means the worst case stops being "we lost everything."

Step 5 — Decide whether to recover or rebuild

Once you know where things stand, there's an honest calculation to make.

Recovering makes sense when the site is reasonably current, you've got or can get the logins, and the only real problem is that nobody is maintaining it.

Rebuilding often makes more sense than people expect. If the site is five or more years old, isn't right on phones, and is built on something you can't edit, you may spend more in access fights and patchwork than a fresh build would cost. And you'd still have the old site.

The exception is your domain and your email. Never rebuild around those — recover them. A new domain means every card, sign, truck, invoice and inbound link points somewhere dead.

Step 6 — Set it up so this can't happen again

Whoever builds your next site, insist on this before any work starts:

• The domain is registered in your account, under your business, with your billing card
• Hosting is in your account, on your card
• Your developer gets access to those accounts — not ownership of them
• You hold a copy of the website files and know how to get another
• The logins live somewhere the business keeps records, not in one person's head

None of this makes a developer's job harder. Any developer who resists it is telling you something useful.