Your developer vanished and you have no access: getting the site back
- Nine times out of ten the site comes back — the cost is time and patience.
- The domain is the critical piece. Hosting and files can be rebuilt; a domain on someone else’s account cannot.
- Registrars and hosts talk to whoever the paperwork and the payments belong to.
- The cheapest moment to collect your credentials is the first day of the engagement, not the last.
The usual story: the site was built three years ago, it works, nobody touches it. You need to change the phone number in the header — and it turns out the developer stopped replying long ago, the admin email was theirs, and the domain is in their name.
First, work out what is actually lost
| Part | How to check | How critical |
|---|---|---|
| Domain | A whois lookup shows the registrar and the expiry date | The most critical |
| Hosting | Where the domain points, the invoice, the contract | Critical but solvable |
| Site admin | Password reset to your own email address | Often back within the hour |
| Analytics and mail | Google Analytics, Search Console, company email | Annoying, not fatal |
The domain comes first
Run a whois lookup. If the registrant is your company, relax: the registrar will restore access against documents, it is a routine procedure. If it shows the developer’s name, you will have to negotiate.
Check the expiry date separately. The biggest risk here is not a hostile developer but a forgotten renewal. A lost domain means losing every inbound link, every search position and all email on that domain at the same time.
Hosting and files
Identify the host from the domain’s DNS records. If the account belongs to your company, support will restore access against documents. If the account is someone else’s, the host will give you nothing — and they are right not to.
Even then the site can be saved: the public half is available — pages, copy, images, structure. It is not a full copy, there will be no order database, but for a brochure site or a catalogue that is usually enough to rebuild without losing the URLs.
The list to ask for
Send one email with a specific list. Not “please send access”, but:
- Domain: registrar, control panel login, transfer authorisation code.
- Hosting: provider, control panel access, FTP or SSH credentials.
- Site: admin URL and an administrator account.
- Database: a dump and access details, if any exist.
- Services: Google Analytics, Search Console, email marketing.
Keep the tone neutral and keep it in writing — the correspondence matters if you later have to prove ownership. The most common reason for refusal is not malice but an unpaid invoice or a grudge. If negotiation fails, the sequence is a written demand, then the registrar and host with your company documents, then a lawyer. Most cases never reach the third step.
How to avoid it next time
- Register the domain yourself, in the company’s name.
- Open the hosting account yourself and add the contractor as a user.
- Keep your own administrator account in the site’s admin panel.
- Connect analytics from your own Google account.
- Once a quarter, confirm a backup exists and does not live on the same server.
None of this is distrust. It is the same as holding the keys to your own office even though a different company does the cleaning.
We will help you regain control: work out what is lost, what can be recovered, and take the site onto support.