Paying for a website does not automatically make it yours. Ownership is three separate things — the domain name, the code, and the hosting account — and each one belongs to whoever's name is on that account, not to whoever paid the invoice.
That gap is the single most expensive thing Indian small businesses get wrong about their own websites, and it is almost always discovered at the worst possible moment: during a disagreement, or when the person who built the site stops answering the phone.
The three things, and why they separate
Most owners think of "my website" as one object. It is not. It is three, and they can each sit with a different person.
The domain name is your address — yourbusiness.in. It is rented from a
registrar, usually yearly. The person whose name and email are on that
registration controls it. They can move it, let it lapse, or point it somewhere
else, and no invoice overrides that.
The code is the site itself: the pages, the templates, the database. If you have the files, you can move to another developer in an afternoon. If you do not, a "rebuild" means starting from zero even though you already paid for it once.
The hosting is the machine the code runs on. It is a separate account from the domain, usually billed separately, and it is the one people most often forget exists until it expires.
You can own all three, some of them, or — more often than anyone expects — none of them, while genuinely believing the website is yours because you paid for it.
Why this goes wrong without anyone being dishonest
It is worth saying plainly: most of the time nobody set out to trap you.
A small developer building sites for local businesses registers domains through their own account because it is faster than walking a client through a registrar signup, and because the client asked them to "handle everything". Hosting goes on the developer's reseller plan because one plan covering twenty clients is cheaper than twenty plans. The code lives on their laptop because there was never a reason for it to live anywhere else.
None of that is malicious. All of it means that on the day you want to leave, or the day that developer moves on to a salaried job, you have nothing.
The problem is not bad intent. It is that the convenient setup and the safe setup are different setups, and nobody is choosing between them out loud.
How to check what you own today, in about ten minutes
You do not need your developer's cooperation for the first two of these.
Check the domain. Search your domain on a WHOIS service such as
who.is, or on registry.in if it is a .in domain. Look at the registrant
name and email. If privacy protection is on you may see the registrar's details
instead of a person's — in that case the real test is the next one.
Ask for the registrar login. One message: "Please send me the login for the account where our domain is registered." A straight setup produces it the same day, because it was always yours. Watch what happens if the answer is a reason rather than a password.
Ask where the code is. The answer you want is a repository — GitHub, GitLab, Bitbucket — with your account added to it. "It's on my system" is an answer, and it tells you the code exists in exactly one place in the world.
Check who the hosting renewal emails go to. If renewal notices have never reached your inbox, the account is not in your name.
What to ask for in writing, before the advance
The right time to settle this is before any money moves, when it is an ordinary line in a quote rather than a confrontation. Four points, in plain language:
- The domain is registered in my name and my business email, and I have the registrar login from day one.
- The hosting account is in my name, billed to me or billed through you but transferable, and I have the password.
- I receive the complete source code and a copy of the database at handover, in a repository or an archive, with no part withheld.
- The work is mine outright — no licence, no per-year fee to keep using what I paid to have built.
An email thread saying this is enough. It does not need a lawyer, and asking for it is not an insult — a developer who works this way already will agree in one line, because it costs them nothing. The reaction to the question tells you more than the answer does.
The one place it is reasonable for someone else to hold something
There is an honest exception, and pretending otherwise would be unfair to good developers.
If a developer has built something genuinely reusable — a booking component, a billing module, an internal framework they use across many clients — they may licence that to you rather than hand over ownership of it. That is normal, and it is often why your site cost less than it otherwise would.
What matters is that it is named, and that it is not the whole site. "We licence our appointment-booking module, everything else is yours" is a fair arrangement. "The code stays with us" is not an arrangement, it is a dependency.
Ask which parts are licensed, and what happens to those parts if you leave. If the honest answer is that the site cannot run without something you do not own, you want to know that on day one rather than in year three.
If you have already paid and own nothing
This is the common case, and it is recoverable more often than people assume.
Start with the domain, and start calmly. It is the piece that matters most and the piece hardest to rebuild. Ask for it to be transferred to a registrar account in your name. Most of the time this simply happens; there was no plan, just a default nobody revisited.
Ask for the code as an export, not as a favour. Many hosting panels let anyone with access download the files and database directly.
If the relationship has already broken down, weigh the cost of the fight against the cost of rebuilding. A five-page brochure site is often cheaper to rebuild than to argue over. A site with years of blog posts, rankings and customer data usually is not — and that is precisely when it is worth being patient and polite to get the transfer done.
What you should not do is nothing. A domain in someone else's account is fine right up until the year it quietly does not get renewed.
When you should not hire anybody at all
If you do not have a domain yet and you are not sure the business needs a website this year, the useful first step is not hiring a developer. It is buying the domain yourself, in your own name, for a few hundred rupees a year.
It takes fifteen minutes on any registrar. It means that whenever you do build something, the most important piece is already yours and cannot be lost in a disagreement. And if you never build the site, you are out the price of a year's renewal instead of the price of a project.
We would rather tell you that than sell you a website you are not ready for. If and when you are ready, our own terms are the four points above — the domain in your name, the hosting in your name, the code in your repository from day one — and you can read what a build actually costs in what a website really costs in India and how to judge whoever you hire in seven questions to ask a web developer.
This is general guidance on how domain, hosting and code ownership normally work, not legal advice on any contract you have signed. For a dispute over an existing agreement, speak to a lawyer with the paperwork in front of them.