Who Owns Your Website? The Four Things to Check

Your website is really four separate things you can own or not own: the domain name, the hosting account, the code and design, and the content. Most owners assume they hold all four, and discover at the worst possible moment that a developer or agency quietly holds one or two.

Ownership is not one yes-or-no question, and that is the trap. Below is what each of the four means, how to check who actually holds it today, and what to do if the answer is not you.

What are the four things you can own?

Think of a website as a house. Four different papers decide whether it is yours.

The domain is your address, your business name dot com. Whoever holds the account where it is registered controls it, and it renews every year. The hosting is the land the house sits on, the server where your files live. It is a separate account, often with a separate company. The code and design are the house itself, the theme and build that make your site look and work the way it does. The content is everything inside, your text, images, logos, and the pages you have added over time.

These can sit in four different places under four different names. You can own your content while someone else holds your domain. You can own your domain while your site runs on an agency’s hosting you cannot access. Knowing which is which is the whole game.

How do you check who owns each, in ten minutes?

You can verify all four this afternoon without asking anyone, which is the point. If you have to ask your developer who owns your domain, that itself is a warning.

• Domain: can you log in to the account where the domain was registered, on your own, with your own details on file as the registrant? If you have never seen that login, you do not currently control your domain.
• Hosting: do you have a hosting account in your name that you can log in to, see your files, and take a backup from? Or does your site simply exist somewhere your developer manages?
• Code: do you have a copy of your site’s files and database saved somewhere of your own? If the only copy lives on someone else’s server, you are one disappearance away from having nothing.
• Content: do you have the original logos, images, and text saved outside the website? These are usually yours by right, but “by right” does not help if you cannot lay hands on them.

Four logins and one backup. If you can produce all of them, you own your site. If you cannot, you have found the gap before it found you.

What does “the agency owns the site” really mean?

It usually means one of two things, and they are very different. The honest version is that the agency built the site and hosts it for you, but you can take the domain, the files, and the content whenever you ask. The site is theirs to maintain and yours to leave with.

The other version is a cage. The domain is registered under the agency’s account, the site lives on hosting only they control, and the build is locked so that leaving means starting over. Some make this explicit in a contract; more often it is just how things ended up, and nobody spelled it out. Either way, the test is the same: can you walk away with your domain, a copy of your site, and your content? If the answer is no, you are renting something you thought you owned, and the monthly fee is really a ransom you have not noticed yet.

How do you get ownership back?

Start calmly and in order, because panic makes people sign things. First, secure the domain, since it is the piece that is hardest to replace and easiest to hold hostage. Ask, in writing, to be made the registrant and given access, or to have it transferred to a registrar account in your name. Second, get a full copy of the site, the files and the database, saved somewhere you control. Third, get the original content and brand assets.

Most of the time a plain, professional request does the job, because most developers are not villains, just disorganised. When someone genuinely refuses, you usually still have routes: a domain can often be recovered through the registrar with proof the business is yours, and a site can be rebuilt from its live pages if the worst happens. It is slower and it costs, which is exactly why checking early, before there is a dispute, is worth ten minutes today.

How should a developer hand over ownership?

A good handover leaves you holding all four papers without having to ask. On every build I do, the domain stays in your name, the hosting is an account that is yours, you get a copy of the site and the logins written down in one place, and the content is yours to take. You should be able to fire me and lose nothing but me. That is the standard to hold any developer to, and it costs them nothing to meet except the habit of doing it.

This is the other half of the cost conversation, because a cheap build that traps you is not cheap. I wrote about that side in what a custom WordPress website costs, and how I structure real projects is on my work page. If you want a site built to hand you every key from day one, that is what custom WordPress development is for.

If you want a site you actually own rather than rent, send me a message on WhatsApp and tell me what your business does. I will tell you honestly what a clean, fully-owned build looks like for you. Message me on WhatsApp.

Quick answers

Can my developer hold my domain hostage?

They can if the domain is registered under their account instead of yours, which happens more than it should. This is why the domain is the first thing to secure. If it is registered in your name with your details as the registrant, no developer can hold it, and you can point it anywhere you like.

What files should I have copies of?

A full backup of your site’s files and its database, saved somewhere of your own such as your computer or your own cloud storage, plus your original logos, images, and any written content. With those, your site can be moved or rebuilt by anyone. Without them, you depend entirely on whoever holds the only copy.

Is my content mine?

The words, images, and logos you created or paid for are almost always yours, even when someone else built the site. The catch is access, not ownership: content you cannot reach or download is yours in principle and useless in practice. Keep your own copies so the question never arises.