Who Really Owns Your Website? Domain, Hosting and Code Explained
Many business owners pay for a website and later discover they cannot log in to it, move it or even keep their own web address. Here is what you should own, how to check, and what to ask your developer before you pay.
· 6 min read
Imagine paying for a shop to be built, then finding out the land belongs to the builder, the keys are kept by someone you cannot reach, and the building plans are locked in a drawer. You could trade there, but only for as long as the builder allows it.
That is exactly how many business owners are treated when it comes to their website. They pay, the site goes live, everyone smiles. Then one day they want to change the phone number, move to a better provider or simply fix something, and they discover they cannot. They do not have the login. The address is registered in someone else's name. Nobody can find the files.
This post explains what a website is made of, what you should own, and the questions to ask so you are never locked out of your own business.
A website is three separate things
People say the website as if it were one object. It is actually three, and each can belong to a different person.
The domain is your address on the internet, for example yourbusiness.com. It is registered with a company for a fee that is usually paid once a year. Think of it as your name and your street address. If you lose it, customers can no longer find you, and in the worst case someone else can register it.
The hosting is the computer where your website's files live and from which they are delivered to visitors, around the clock. Think of it as the land and the building. It is also paid for regularly, monthly or yearly.
The code, together with your content, is the website itself: the pages, the design, the text, the images, the database, the admin area. Think of it as the building and everything inside it.
Who owns what, and why it matters
All three should belong to you, the business owner, or at least be fully accessible to you. Here is what goes wrong when they do not.
If the domain is registered in your developer's name, they are the legal owner. If you fall out, if they disappear or if they simply stop renewing it, your address can be lost, and your email addresses ending in that domain stop working with it.
If the hosting account is theirs, you cannot see what you are paying for, you cannot move your website, and you depend on them to keep it paid and updated.
If you do not have the code, a new developer cannot continue the work. You may have to pay to rebuild the website from scratch.
And if you only have a login to a basic page editor, you can change the words but you do not control anything underneath.
How owners get locked out
It is rarely malicious. Most of the time it is convenience. A developer registers the domain in their own account because it is quicker. Hosting is bundled into one monthly bill. Logins are shared over a chat message and never changed. Then the developer changes jobs, changes phone numbers or goes quiet, and the owner is left holding a website that nobody can touch.
Sometimes it is deliberate. A developer who holds the domain or the files has leverage, and may ask for extra money before handing anything over. Neither situation is acceptable for something your business depends on.
What you should receive
When a website is delivered, you should be able to say yes to each of these.
The domain is registered in my name or my business name, with my email address as the contact, and I have the login. I have the hosting account details, or I am clearly told what hosting is used, who pays for it and when it renews. I have the admin login for the website, with a strong password I have changed. I know where the code lives and I have a copy, or the agreement says exactly how I get it. There are regular backups, and I know where they are stored. And there is a written note of how everything fits together.
Questions to ask before you pay
Whose name will the domain be registered in? Who owns the hosting account, and what does it cost every year? Will I receive the full source code, and when? What happens if you are unavailable? How are updates and security fixes handled, and who answers when something breaks? Is the support cost written down?
A good developer answers these without hesitation. If someone becomes vague or annoyed when you ask, treat that as information.
What to do if you are already locked out
Start by finding out who the domain is registered to. A public lookup of the domain's registration will usually show the registrar, and sometimes the contact. Contact the developer calmly and in writing, and ask for the domain transfer details and a copy of the website files and database. Keep every payment receipt and message as proof that you paid for the work.
If the developer cannot be reached, you can still often recover. The hosting company or the domain registrar has procedures for proving ownership. And if the site itself is out of reach, a developer can often rebuild it from the live pages quickly, with the same content and design, so you are not starting from zero.
How I handle it
I treat ownership as part of the delivery, not an extra. For every website I build, I register the domain in the client's name, or hand it over properly, give you the admin logins, explain the hosting and tell you what it costs, and make sure you can reach your files and backups. You should never need my permission to keep your own business online.
If you are not sure who owns your website, or you suspect you are locked out, get in touch and I will look into it for you and tell you honestly where you stand. Use the contact page, or call or WhatsApp me on +231 777 810 466. And if you know a business owner who has never asked these questions, send them this post. It may save them a great deal of trouble.
About the author
Francis Landford
Software Engineer | Creative Problem Solver | Innovative Software Solutions & Modern Applications
More about Francis Landford →