Getting Access to Your Own Site When the Developer Won't Reply

If your web developer has gone quiet and you cannot access your own site, you are not necessarily stuck. Ownership of the domain and hosting account usually matters more than who originally set them up, so your route back often runs through the registrar and hosting company directly, not through the developer. The first job is to work out who actually holds each account. Then you go to those companies, not the silent developer. Here is the practical path.

First, map what you have and what you are missing

You cannot recover access without knowing what is missing. List the four pieces and mark which you can reach:

1. The domain. Look it up in ICANN's lookup tool to see the registrar. Do you have a login there?
2. The hosting. Which company hosts the site, and do you have an account with them?
3. The website files and content. Do you have any backup or copy?
4. The CMS admin. Can you log in to the site itself?

Whatever you can already reach, secure it now by changing the password. Whatever you cannot, that is your recovery list. Who owns your website covers this mapping in more detail.

Try the direct, reasonable route first

Before treating this as a fight, make one clear, documented request. Email the developer, politely and in writing, asking for the logins to the domain, hosting, and site, and a backup of the files. Give a reasonable deadline. Keep the email, because it matters later if this escalates.

Sometimes silence is just a busy or disorganised freelancer, not a hostage situation, and a clear written request gets a response where casual messages did not.

Going around a developer who will not cooperate

If there is no reply, you go to the companies that actually run the infrastructure.

• The registrar. If the domain is registered to you or your business, even if the developer set it up, the registrar has a process for recovering access to an account, usually involving proving your identity or ownership. Contact their support and explain the situation.
• The host. Same idea. If the hosting was bought in your name or paid for on your card, the host can often help you recover the account. If the developer bought it on their own account, this is harder, and you may need to move the site.
• Rebuild the access, not the site. If you have a backup or can export your content, you can move to hosting and a domain you control, even if you cannot prise the originals loose. Sometimes recreating clean access is faster than winning an argument.

What helps most is proof that the business, and ideally the domain and payments, are yours. Card statements, company records, and the domain registration details all help.

When to get help

If the domain itself is registered to the developer and they will not budge, or the site is complex and you have no backup, this can get genuinely stuck. That is the point to bring in someone who has untangled these before, or in a serious case, to take legal advice. It is often cheaper to rebuild access than to fight, and a professional can tell you which applies.

Stop it happening again

Once you are back in control, prevent a repeat. Put every account, domain, hosting, CMS, in your own name, and keep the logins yourself even if a developer manages the site day to day. When you next hire someone, agree ownership up front, in writing, so the domain, hosting, and accounts are yours from day one.

What to do next

Map what you can and cannot access today, and secure what you can reach right now. Send one clear written request to the developer. If it goes unanswered, go straight to the registrar and host about recovering the accounts. And if you are inheriting the site to move it elsewhere, taking over a website from another developer covers the clean handover.