Your developer vanished.
They still hold the keys. Here is how to get them back.
A freelancer or small agency built the site and kept every login in their own name. Now the business cannot change a price, fix a bug, or prove it owns the domain.
Why this keeps happening
A lot of small-business sites get built by one freelancer or a two-person shop. In the rush to launch, nobody asks the question that matters later. Whose name is the domain under. Who holds the hosting login. What happens if this person is unreachable next year. It works fine for months, sometimes years. Then it suddenly does not. This is not a sign the business did anything careless. Almost nobody asks this question until the day they need the answer.
Figuring out what is actually missing
Before anything else, separate three things that often get lumped together as “access.” The domain: who owns the registration. The hosting and server: where the site actually runs. The application itself: the code, the database, the admin login. Losing all three at once is rare. Usually one or two are recoverable through the platform’s own process, even without the previous developer’s help. Knowing which is which changes the whole plan.
What actually gets access back
Domain registrars, hosting providers and most site platforms have a recovery process built for exactly this. It works for a business that can prove it is the real owner, separate from whoever originally registered it. It usually needs registration documents, billing history, or a paper trail showing who paid for the service. It is slower than a shared password would be. It does not need the previous developer to respond, cooperate, or still be reachable.
When the code itself is the real gap
If the actual application code is missing, with no backup, that is a harder problem than a locked login. Depending on the platform, this can mean rebuilding from what is publicly visible on the live site. That is slower and more expensive than picking up existing code, but it is not usually a dead end. We say plainly, before any work starts, how much of a rebuild a situation actually needs, instead of promising a quick fix that is not realistic.
Making sure this cannot happen again
Once access is back, the real fix is structural. The domain registered to the business, not a person. At least one more team member with admin access to hosting and the site. A copy of the code and database living somewhere the business controls. None of that is expensive to set up. It is just the step that gets skipped when one person builds a site in a hurry. Everyone trusts them, right up until they are not reachable anymore.
What to do in the next hour
- 01
Check who the domain is registered to using a WHOIS lookup, and whether that email is one you control.
- 02
Look for any invoice, contract or email where the developer confirmed what belongs to the business.
- 03
List every system this one person might control: hosting, DNS, email, the admin panel, payment keys.
- 04
Do not threaten legal action over chat yet. It rarely speeds up a reply and can end the conversation.
When to call us
Call us if the site is how customers find or buy from the business. Also call if the domain itself is at risk, or you need someone to take over and keep it running. Get a free plan →
FAQ
Legally, who owns the code and the site if the contract was never clear?
It depends what was agreed, written or not, and the laws that apply. In most freelance work, the client owns what they paid for, even without a perfect contract. Proving that is easier with an invoice or email trail. We are not lawyers, and for a real dispute we say so and point you to one.
Can you get our access back without the old developer's cooperation?
Often yes, through each platform's own recovery process. Domain registrars, hosting providers and site platforms have recovery paths that work from proof you are the business behind the account. It depends how the accounts were originally set up.
What if we never get the original code back?
We tell you honestly how bad that is for your specific site. A WordPress or Shopify site is usually rebuildable without too much pain. A fully custom app with no code or backup is a harder rebuild, and we say so before you spend money assuming otherwise.
Will the code be ours once this is sorted out?
Yes, on payment, as set out in whatever agreement we make. You get read access from day one, so you are never in this position with us.