Your Web Developer Disappeared: How to Get Your Website Back (India, 2026)

Your developer has stopped replying. Calls go unanswered, WhatsApp shows one tick, and you have just realised you cannot log in to your own website. Maybe the site is still up. Maybe it went down last week and you have no idea why.

The short answer: how much you can recover depends almost entirely on whose name things are registered in, not on who paid. The domain is the one asset with a deadline, so that is where to start. Hosting is usually recoverable. Content you supplied is yours. Copy and code the developer wrote may legally still be theirs, which is uncomfortable but rarely decides the outcome in practice. Work through the three steps below in order.

First, find out what the public record tells you

Before you chase anyone, run your domain through lookup.icann.org. One caution that most guides skip: the registrant name and email are almost always hidden. Privacy redaction is now the default for both .in and .com, so do not expect the lookup to name your developer. We ran it on our own domain and the registrant field came back empty.

What it does reliably tell you is more useful than it sounds:

To work out whether the domain is in your name when the record is redacted, try these instead: go to the registrar named in the lookup and run a password reset against your own email address; search your inbox and card or UPI statements for a renewal receipt from that registrar; or check who the renewal reminders have been going to. If the reset email arrives and the receipts are in your name, the domain is yours and this is an access problem, not an ownership problem. That distinction decides everything that follows.

Step 1: deal with the domain first

The domain is the only piece with a clock on it. Hosting can be replaced, code can be rewritten, content can be retyped. Note that expiry is not instant death: there is normally a grace period and then roughly thirty days of redemption during which you can still restore the name, though redemption fees run into thousands of rupees rather than the few hundred a renewal costs. After that it goes back on sale to anyone.

If the domain is yours and you can get in: log in, enable auto-renew, and pay for several years at once. Five minutes, and the worst outcome is gone.

If the developer holds it and will cooperate: this is easy and cheap. Ask them to unlock the domain and send you the authorisation code, usually called the EPP or auth code. With that code you can pull the domain into your own registrar account yourself. Ask for the transfer before asking for a registrant name change, because changing the registrant typically triggers a 60-day lock during which no transfer is possible.

If they refuse, or you cannot reach them at all: here is the part other guides get wrong. Your registrar will not settle this for you. Registrars explicitly decline to adjudicate ownership disputes between a registrant and a third party, and they will not move a domain because you send them a GST certificate. They act on a court order, an arbitral award, or a decision from a dispute panel, and nothing less.

The realistic routes, cheapest first:

1. Pay the renewal yourself if the registrar will accept it. Many will take payment from anyone. This does not give you ownership, but it stops the clock while you sort the rest out.
2. A lawyer's legal notice. Often enough on its own. A freelancer who has been ignoring emails responds differently to a notice on letterhead, and it costs a fraction of the alternatives.
3. Arbitration. For a .in domain that is INDRP, run by NIXI; for .com it is UDRP. Both require you to show rights in the name, typically a trademark or an established business name. Budget properly: INDRP filing alone is ₹35,400 before any legal fees.
4. Civil court. Slowest and dearest. Realistic only where the domain carries serious value.

Keep your GST registration, incorporation papers and payment records. They are not something a registrar will act on, but they are exactly the evidence these proceedings run on.

Step 2: get into your own hosting, then lock it down

Hosting is usually the easier half. Where the account was opened in your business name or your email, a password reset gets you in. Where the developer opened it under their own account, contact the host's support with proof of identity and evidence you have been paying.

One case that trips people up: if your site sits in a developer's reseller account, the upstream host has no record of you at all and cannot help. Signs of this are a control panel branded with the developer's name, no matching account when you try a password reset at the host, and hosting invoices issued by the developer rather than by the hosting company. In that situation the site has to be migrated out rather than recovered, which makes your backup the whole ballgame.

The moment you have access, do these in order:

1. Take a full backup, files and database, and download it to your own computer. Before you change anything, cancel anything, or tell anyone you are in.
2. Change the hosting and CMS passwords.
3. Turn on two-factor authentication.
4. Remove or demote every user account that is not yours, and check for unfamiliar admin users, FTP accounts and SSH keys.

That last step is housekeeping, not paranoia. A developer who left on bad terms is rare; a forgotten account that nobody closed is extremely common.

Step 3: work out what is actually recoverable

This is where the cost gets decided. Four scenarios, roughly in order of luck:

• You have hosting access and the site runs on WordPress or similar. Everything is recoverable. The files and database in your backup are the whole site.
• You have hosting access but the site is custom-built. The running code is recoverable, though without the original project files it may be harder to change. Usually still cheaper to keep than replace.
• No hosting access, but the site is still online. Content, images and structure can all be captured from the live pages. You are rebuilding the container, not the contents.
• The site is already offline. Check the Wayback Machine for your domain before assuming anything is lost. Text and images often survive there.

The honest question is not "can this be saved" but "is saving it cheaper than replacing it". For a small business site the answer is often no, because a five-year-old abandoned site usually needs the work anyway. If you do rebuild, keep the old URLs where you can, so the rankings you already have survive the move.

Who owns the content and the code

This is the part where confident advice on the internet is usually wrong, so here it is properly.

Under section 17 of the Copyright Act, 1957, the first owner of copyright is the author, the person who created the work, not the person who paid for it. There are exceptions, and they are a closed list.

Two things follow. First, an invoice is not an assignment: transferring copyright in India needs a written document signed by the person giving it up. Second, and more usefully, this is precisely why the handover you ask for on the next project should be a written IP assignment covering copy, design and code — not just a zip file of the site.

In practice this rarely decides anything. Almost nobody litigates copyright over a small business website, and the real outcome is settled by who holds the logins. But it is worth knowing where you actually stand before you assert ownership in an argument.

What it costs to fix in India

Our published rates, and the two dispute figures for context. Other agencies will differ; the shape of the decision does not.

Something worth knowing while you work out which row you are in: this is far more common than it looks. When we audited 333 solar installers on Tamil Nadu's government vendor lists, 21% of the companies that owned a domain had let it go dead or lapse into a parking page. That is not 21% who never bothered with a website. It is 21% who paid for one, and then something quietly stopped being renewed.

That last row is the strongest argument in this entire article for registering your own domain. The difference between the two domain rows is about twenty-five times, and the only thing separating them is whose name went on the registration.

What to send a web developer who is not responding

One message, short, no accusations, and a clear deadline. Long emails about how disappointed you are do not get replies; a specific request with a date sometimes does.

Hi [name] — I need to get the website admin sorted out regardless of whether we keep working together. Could you send me the hosting login and the site files by [date, about a week out]? For the domain, the simplest thing is if you unlock it and send me the authorisation code so I can move it to my own account. Let me know either way.

Two things make this work. It gives them an easy exit rather than demanding an explanation, and it names a date, which turns an open-ended obligation into a task. Ask for the auth code rather than a registrant change, because a registrant change starts a 60-day transfer lock. Keep a copy of what you send: if this ends in arbitration, a written request with no reply is useful evidence.

Why web developers disappear, and how long to wait

In our experience the freelancer who vanishes has usually not run off with your money. They have taken on more work than they can deliver, fallen behind, started avoiding the clients they owe work to, and eventually stopped opening the messages. Others change careers, take a full-time job, or have something go wrong in their lives. That is worth remembering when you write to them, because a polite request gets logins far more often than a legal threat does.

On timing, separate two questions. Securing the domain is not something to wait on at all. Check the expiry date today, whatever else is happening. The waiting question applies only to whether you keep working with this developer, and there my advice is two weeks. Send one written message with a deadline, and if it passes with no reply, move on. You can always stop if they resurface. You cannot get back a domain that expired while you were being patient.

How to make sure it never happens again

Almost every case of this is preventable with four decisions on the next project:

1. Register the domain yourself. Your own account, your own email, your own card. Give your developer access if they need it. This one decision is worth more than the other three combined.
2. Hold the hosting account. Same principle. You are the owner; they are a user you can add and remove.
3. Get a written IP assignment at launch. Not just the files: a signed document assigning copyright in the copy, the design and the code. If a developer will not put that in writing, treat it as information about the rest of the engagement.
4. Make sure a backup lands somewhere you control. Monthly is plenty for most small business sites. A backup that only exists on the developer's machine is not a backup.

These four cost nothing and take about an hour. They are the difference between a developer leaving being an administrative annoyance and being an emergency.

Where to get help

If you are working through this and want a second opinion on what is recoverable, our free website audit will tell you what state the live site is actually in, and our website maintenance service covers sites built by another agency. For the ongoing costs, our guide to website AMC packages in India breaks down what maintenance should include.