In short: if your developer disappeared, first secure your domain, then your hosting, then your code and admin accounts, in that order. Most businesses can regain control in 1–5 days, even with no reply from the developer, as long as the domain and hosting were paid for in the business's name or by the business's card.
It happens more often than people think: a freelancer takes a full-time job, an agency closes, or a developer simply stops answering. Meanwhile the site needs a change, a renewal is coming up, or something has broken. This guide walks you through getting control back without breaking anything.
What to do first if your developer disappeared
Before you change anything, write down what you know. Spend 30 minutes making a list of:
- Your domain name and where you think it is registered (GoDaddy, Namecheap, Cloudflare, a local registrar)
- Who sends you the hosting invoice, if anyone
- Any logins the developer ever shared with you
- Email addresses used to set things up (yours, a staff member's, or the developer's)
- Third-party services: payment gateway, email, Google Analytics, Search Console, booking tools
Then send the developer one polite, written message asking for access and giving a deadline, for example 7 days. Keep it friendly. Many "disappeared" developers are simply busy, and a clear request gets a reply.
Step 1: Secure your domain name
The domain is the most important thing you own online. Whoever controls it controls your website and often your email.
- Look up your domain on ICANN Lookup to see which registrar holds it and when it expires.
- Contact that registrar's support. If the account is in your name, or you can prove the business paid for it, they can usually move it to an account you control.
- If it expires within 60 days, renew it as soon as you have access. An expired domain can be bought by someone else.
Transfers between registrars follow the ICANN Transfer Policy, which protects the registered owner (the "registrant"). This is why it matters whose name is on the domain record.
Step 2: Get access to your hosting
Find out where the site actually runs. A good developer can tell from the domain's DNS records in a few minutes. Then:
- If you pay the host directly: reset the password using your email, and you are in.
- If the developer pays and re-bills you: contact the host with proof of payment and ask them to move the account, or have a new developer copy the site to new hosting.
- If nobody knows: a developer can still copy the public website, but a full copy of the database and files needs server access. Do this before the hosting bill goes unpaid.
Step 3: Recover the code and admin accounts
For WordPress, Shopify, Wix and similar platforms, you need an administrator login. If you only have an editor login, the hosting account lets a developer create a new admin safely.
For custom-built sites and apps, ask for:
- Access to the code repository (GitHub, GitLab or Bitbucket), with you as the owner
- The database and any environment settings (API keys, email settings) stored on the server
- App store accounts (Apple, Google Play), which should always be in your business's name
Step 4: Lock everything down
Once you have access, assume the old developer could still log in, even if they never would:
- Change every password and turn on two-factor login
- Remove old user accounts from the website, hosting, DNS and repository
- Replace API keys for payments, email and maps
- Take a full backup and store it somewhere the old developer cannot reach
- Check Google Search Console for security warnings
How long does it take to take over a website?
| Situation | Typical time |
|---|---|
| You have the hosting and domain logins | 1 day |
| Domain and hosting in your name, but no logins | 2–5 days via support |
| Domain or hosting in the developer's name | 1–4 weeks, depending on the registrar and proof of payment |
| Custom app with no code access | From 1 week to a partial rebuild |
What should a proper website handover include?
Whether you are leaving a developer or a new one is taking over, ask for this handover pack:
- A list of every account, who owns it and when it renews
- Admin logins for the website, hosting, DNS and repository, all in the business's name
- A recent full backup (files and database)
- Notes on anything custom: plugins, integrations, scheduled jobs
- Known problems and anything that was half-finished
How to stop it happening again
- Register the domain and hosting in your business's name, paid with the business's card
- Have the code in a repository you own, with the developer invited as a member
- Keep a shared document of every login, stored in a password manager
- Choose a team rather than one person, so holidays and job changes do not stop your website
Need someone to take over?
Rachyet takes over websites and apps from developers who have moved on: we recover access, take a full backup, fix what is urgent and then look after the site with a fixed monthly maintenance plan. If the site has been neglected for a while, our website security check is a good first step. Tell us what you have access to and we will reply with a plan within one business day.