The freelancer who built your website disappeared. Here's how to take back control.
It happens quietly: the freelancer who built your site stops answering emails. Maybe they changed careers, maybe the agency folded. Nothing breaks at first — the site hums along — until you need to change something, renew something, or fix something, and discover that every login belongs to a person who no longer exists online.
The way out is to stop thinking of it as "the website" and start thinking of it as four separate assets, because they're often held in four different places — and they have very different recovery paths and priorities.
First, map the four layers
Run a registration-data lookup (lookup.icann.org) to see the registrar and the domain's status, and check the nameserver records to see who runs DNS. The hosting provider is often identifiable from where the site's address points. Stedra's free scan reads all three from public records in one pass.
- The domain — held at a registrar. Whoever controls this controls everything downstream, including your email.
- DNS — the nameservers that point your domain at your website and mail. Sometimes at the registrar, often at a separate provider (e.g. Cloudflare).
- Hosting — the server or platform where the site's files and database actually live.
- The CMS — the WordPress/Shopify/webflow admin login for editing content.
Recover in this order
- 1Domain first — alwaysIf the domain is in the freelancer's registrar account, follow our domain-transfer guide. Everything else on this list can be rebuilt; a lost domain often can't.
- 2Then DNSOnce you control the domain, you can repoint the nameservers to a DNS account you own — even if you never recover the old DNS login. Export or reconstruct the zone records first so mail doesn't break.
- 3Then hostingIf you have invoices or receipts, contact the host's support with proof of payment and business ownership — most will work with you. If the hosting was on the freelancer's own reseller account, plan to migrate: take a full copy of the site (files + database) any way you can, and stand it up with a host you control.
- 4Then the CMSWith hosting access you can reset any CMS admin password from the server side. No hosting access? A fresh hosting account plus your site copy gets you a working admin again.
If they're reachable but slow
Most vanished developers aren't malicious — they're overloaded or have moved on. Make cooperating trivially easy: send one email listing exactly the four handovers you need (domain transfer or registrant confirmation, DNS export, hosting access or a full site copy, CMS admin), offer to pay an hour of their time to do it, and give a deadline. That single email resolves more of these cases than any escalation does.
Make sure this never happens again
- Every layer — registrar, DNS, hosting, CMS — lives in an account the company owns; contractors get delegated or collaborator access.
- Billing for each is on a company card, so nothing silently lapses with a stranger's wallet.
- Keep an off-site backup of the site on a schedule you control.
- Write all four logins into your asset register, with a second person who can reach each.
The free scan maps your domain, email, cloud, social and tools from public records — and shows what you'd lose access to tomorrow. No login, nothing to install.
Check my business