Your web developer disappeared: what to recover first
Short answer: protect the domain and business email first, then preserve the live website and collect hosting, CMS, analytics and search access. Work through the registered providers and documented recovery routes. Do not send passwords over ordinary email or WhatsApp, and do not assume that public website files are a complete source-code or database backup.
First hour: preserve evidence and avoid making the outage worse
- Save the contract, scope, invoices, payment records, messages and every account email you can find.
- Record the domain, registrar, expiry information, nameservers, hosting invoices and business-email provider.
- If the site is live, take screenshots and an authorised backup before updating software, DNS or passwords.
- Use a business-controlled email address for recovery. Enable two-factor authentication where the provider supports it.
- Send one written handover request naming the exact accounts, files and deadline. Keep the response or non-response.
Recovery order and what counts as success
| Priority | Recover | Minimum evidence | Safe next step |
|---|---|---|---|
| 1 | Domain and DNS | Registrar account under the business, renewal control and current registrant/contact data | Secure the account, review expiry and export DNS records |
| 2 | Business email | Administrator access, user list, billing and recovery contacts | Protect administrator accounts and confirm mail delivery before DNS changes |
| 3 | Hosting and data | Hosting login plus a restorable files-and-database backup | Copy first; test on staging before changing the live service |
| 4 | CMS and integrations | Named administrator accounts, licences, payment/form destinations and API ownership | Remove obsolete access only after a replacement administrator works |
| 5 | Analytics and search | Business owner/admin access to the actual properties | Verify ownership and audit users, tokens and linked products |
Recover the domain through the registrar
Use an ICANN lookup or the relevant registry lookup to identify the registrar and registration dates; privacy services may hide personal contact data. Then use that registrar’s account-recovery process. Supply only the evidence it requests, such as business identity, invoices, payment references and earlier account emails.
Expiry and restoration rules vary by top-level domain and registrar. For many generic domains, ICANN documents renewal notices and a redemption process, but you should not assume every extension follows the same timetable or fee. Contact the registrar promptly and follow its written instructions. See ICANN’s domain renewal and expiration FAQ.
Preserve hosting, files, database and email separately
A website normally needs both files and a database; an ecommerce or membership site may also depend on media storage, scheduled jobs, transactional email, DNS, third-party apps and payment webhooks. A browser copy or web archive can help reconstruct visible content, but it is not proof that you recovered the original theme, application code, orders, users or settings.
Identify providers from invoices, bank statements, DNS records and account emails. Ask each provider what its authorised recovery route requires. A provider may be unable to give a third party access even when that person paid the developer, so describe the facts and let the provider apply its own account and legal process.
Regain measurement accounts without pretending old data can be recreated
For Google Search Console, the business can establish a new verified owner when it controls an accepted verification method, then review users and unused ownership tokens. Google Analytics access depends on an existing administrator adding the business; a new property cannot recreate historical data from an inaccessible property. Google documents the roles in its Search Console ownership guide and Analytics access guide.
When the dispute may need outside help
Preserve evidence and ask for a specific remedy in writing. Eligible consumer grievances can be raised through India’s official National Consumer Helpline. Whether a matter is a consumer dispute, business-to-business claim, contractual breach or possible fraud depends on the facts. Do not rely on a generic article to decide between a complaint, notice or legal proceeding; ask a qualified Indian lawyer about the evidence, limitation periods, jurisdiction and appropriate route.
Recover, migrate or rebuild?
- Recover and keep: the current site is supported, access is complete, a restore test works and it still meets the business need.
- Recover and migrate: the site is usable but the hosting, account ownership or support arrangement is unsafe.
- Rebuild: the database or source is incomplete, the platform cannot be maintained, critical licences cannot be transferred, or the site no longer meets the requirement.
Do not point the domain at a replacement until email records, redirects, important URLs, forms and rollback have been planned. If the original site still serves customers, preserve it until the replacement has passed staging checks.
Prevent the same dependency next time
- Keep the domain, DNS, hosting, email, analytics, search and payment accounts under business-controlled identities.
- Give suppliers named user access instead of sharing the owner password.
- List deliverables, licences, recurring charges, source files, data exports and handover steps in the signed scope.
- Keep independent backups and perform a restore test; a green “backup completed” message is not a recovery test.
- Review account owners and recovery contacts whenever staff or suppliers change.
Website recovery questions
Can I recover a domain registered through the developer?
Possibly, but account ownership and domain policy matter. Identify the registrar, preserve proof of the agreement and payments, and use the registrar’s authorised recovery or dispute process. Do not assume public WHOIS data proves ownership.
Can a public copy of the live website replace a backup?
No. It may preserve visible pages and assets, but it usually does not contain the database, private media, orders, users, application logic, server configuration or editable source. Treat it as reconstruction material.
Should I change DNS immediately?
Only after recording current DNS and understanding website and email dependencies. A rushed nameserver change can take the site or business email offline. Prepare the destination and rollback first.
Can a new Analytics property recover old reports?
No. A new property starts collecting after it is implemented. Try the existing property’s documented access route and preserve any exports you already have.
When should I get legal advice?
Get qualified advice when ownership is disputed, important money or data is involved, there may be fraud or misuse, a deadline may expire, or a provider requires a formal legal process. The correct route depends on the facts.
Who owns your website? · Website redesign · Ask about a recovery assessment