When an agency disappears, recover the domain and control accounts before rebuilding the website. The domain, DNS, hosting, source code, and content may belong to different providers. Losing one does not automatically mean all five are gone.
Stabilize before changing anything
Save evidence while the current state is still visible:
- invoices, contracts, renewal notices, and payment receipts;
- emails that show who ordered the domain or hosting;
- the exact failing URLs and screenshots with timestamps;
- current DNS records and nameservers;
- public pages, downloadable files, and search-result snippets;
- analytics, Search Console, or ad-account access that still works.
Do not send passwords, identification documents, or payment-card details to an unverified contact. Use the provider’s official recovery channel.
Identify the dependency that actually failed
| Symptom | Likely system to check first | What it does not prove |
|---|---|---|
| Domain does not resolve | Registrar status and authoritative DNS | The hosting files were deleted |
| Domain resolves to an error | DNS target and hosting deployment | The domain registration was lost |
| Website works but email fails | MX and email-provider records | The web host is responsible |
| Old page works but changes are impossible | Repository, CMS, or deployment account | A rebuild is required |
Start with the ICANN Lookup. It can identify the registrar and nameservers for many domains. Public lookup information may be privacy-redacted, so ownership recovery still requires the registrar’s documented process and evidence.
Recover in this order
- Registrar account: establish who the registered holder is and request account recovery or an internal account move.
- DNS: export the current zone before changing nameservers. Preserve mail, verification, and service records.
- Hosting: ask the identified provider to preserve the account and explain its authorized recovery procedure.
- Source and content: locate repositories, CMS exports, object storage, databases, local archives, and recent public copies.
- Measurement and business services: recover Analytics, Search Console, email sending, forms, payments, and advertising accounts independently.
ICANN explains that registrants should work through their registrar for registration management. A transfer between registrars is different from recovering access inside the current registrar, so do not start a transfer until control and lock status are clear.
Decide whether a rebuild is necessary
Rebuild only after inventorying what survives. A static site may be recoverable from a repository and asset folder. A CMS may need both files and a database. A hosted builder may allow export only through the existing account.
Use this decision rule:
- control recovered and build reproducible → restore the current site;
- content recovered but runtime unavailable → migrate into a supported platform;
- only public pages remain → preserve factual content, then rebuild deliberately;
- domain holder dispute unresolved → avoid launching a replacement on a confusing look-alike domain without legal and brand review.
Prevent the same lockout
Put the domain, DNS, repository, analytics, and billing under organization-owned accounts. Grant agencies named roles, require multiple client administrators, record renewals, and test a clean deployment and restore. The durable outcome is not a new homepage. It is a website the organization can operate after any individual vendor leaves.
Need a clearer first step for your website?
Start with the situation and outcome. We will help define the scope and next step.