What to Do When Your Web Developer Disappears

When your web developer disappears, recover control in a fixed order. Secure the domain first, then the hosting and DNS, then get a copy of the site's files. The domain comes first because whoever holds its registration decides whether the site stays online. If your accounts are already in your own name, you can usually regain control without the developer. If they registered everything under their name, that is the hard case.

First, work out what you still control

Start by listing what you can actually log into, because that decides how hard the rest will be. A developer going quiet is a problem. A developer going quiet while holding your domain is an emergency.

Run these four checks in an hour or less:

Asset	How to check you hold it	If you do not
Domain	A WHOIS lookup, plus whether you can sign in to the registrar	The domain is the priority; act on it first
Hosting	Whether you can log in to cPanel or the host's dashboard	Contact the host directly with proof you own the account
DNS	Whether the registrar or host panel lets you edit the records	Regaining the domain or host restores this
Website files and CMS	Whether you have an administrator login, not just an editor one	Export what you can; plan for a rebuild if not

For .my domains, MYNIC's WHOIS tool (MYNIC, retrieved August 2026) shows the registration record, though it now hides personal registrant details for privacy. The question underneath the lookup is simpler: whose account holds the domain, and can you sign in?

Secure the domain before anything else

The domain is the first thing to secure, because it is the single point that can take your whole online presence down. Lose access to it and you can lose the website, the business email running on it, and the address customers already know.

If the registrar account is in your name, change the password now and check the renewal date. In our experience, a domain quietly lapsing during a vendor dispute is one of the most common ways a business loses its name. Confirm it is not close to expiry.

If the account is not in your name but you can prove the business is yours, the registrar may still help you recover it. Once you have control, you can move the domain to a registrar account you open yourself.

Get into hosting and back up the site

With the domain secured, get into the hosting next and take a full copy of the site. A working website that exists only on a server you cannot access is one bad day away from being gone.

Log in to the hosting account and download a complete backup: the files and the database. If you cannot log in, contact the hosting company directly. Hosts will often restore access to the account holder after you prove the business is yours, even when a developer set it up.

Keep that backup somewhere you control, off the server. It is your insurance against the site being taken down, and the starting point for moving to a new developer or host.

When the developer holds everything in their own name

The hard case is when the developer registered the domain, hosting, and email under their own name, not yours. To a registrar or host, the name on the account is the owner, so there is often no technical way around it.

In our experience, this is where a police report does not help, because the registrar treats the named account holder as the owner. The route becomes a contract matter: a written request for the transfer, then a lawyer if they refuse, treating it as a dispute over what you paid for.

Sometimes the faster path is to rebuild on accounts you own and walk away from the trapped ones. If the old domain is genuinely lost, a new domain plus a fresh build under your own name can cost less than a long legal fight. The trade-off is losing the address customers knew.

Weigh the recovery against the rebuild honestly.

This is also the point where who owns the code matters, because a rebuild is easier if the design and content are legally yours.

How to make sure this never happens again

Prevention is one clause and one habit, and both cost nothing before a project starts. The clause: every account and registration is created in your business's name, and the provider gets access you can revoke. The habit: take a full handover at sign-off, not a promise to send it later.

A pattern we repeatedly see is that lockouts trace back to the setup day, not the falling-out day. The accounts went under the vendor's name at the start, and nobody noticed until the relationship soured. Settling who controls the site while everyone is still cooperating is the one protection that costs nothing.

Frequently asked questions

Can I get my domain back if my developer will not respond?

Sometimes, and it depends on whose name is on the registration. If the domain is registered to you and the developer only had access, reset the password with the registrar and you are back in control. If it is registered to the developer, you usually cannot force a transfer without their cooperation or a legal process. This is why the registrant name matters more than any password, and why checking it early tells you which situation you are in.

Will my website go offline if my developer disappears?

Not immediately, in most cases. A live site keeps running on its hosting until something changes: the hosting bill goes unpaid, the domain lapses, or an account is closed. The danger is that nobody is watching those renewal dates once the developer is gone. Secure the domain and hosting quickly, move the billing to you, and the site keeps serving visitors while you sort out the rest.

Is a police report useful if a developer holds my accounts?

Usually not, and it surprises people. To a registrar or hosting company, an account registered under the developer's name is treated as theirs, so a police report rarely moves a registrar. Your real leverage is a contract claim over work you paid for. That is why the prevention clause and a written handover matter far more than any report after the fact.

Should I just build a new website instead of recovering the old one?

Sometimes, when recovery would cost more than a fresh start. If the domain is lost and the developer is uncooperative, a new domain and a clean build under your own name can be faster than a drawn-out dispute. The real cost is the old address: customers, links, and search history tied to it. Weigh that loss against the time and legal expense of recovery before you decide.

What is the one thing that prevents all of this?

One line in every agreement does most of the work: all accounts and registrations are created in your name, and the provider receives access you can remove. Add a full handover at project sign-off, and a developer who later disappears takes nothing you cannot reach. Both are free to arrange before work begins. After a relationship sours, the same protections take a lawyer.

Regain control, then never lose it again

Storming Solutions builds and maintains websites for businesses across Kuala Lumpur and the rest of Malaysia, and we take over stranded sites where a previous developer went dark. Every account we set up sits in the client's name from day one, because we would rather earn the next project than trap you into it.

Locked out, or worried you might be? Talk to us about a recovery and access check, or see how we set projects up cleanly on our web development page. We map what you still control, what you do not, and the fastest safe way to get the rest back.