Who owns your website?

You own your website when three things are in your name: the domain, the hosting, and the code and content. If you can log into all three yourself, the site is yours. If your web designer holds any of them, you do not fully own it yet, and you can check each one in a few minutes.

Insights · Published 10 Sep 2026

Insights

Owning your website means you control three things in your own name: the domain, your web address; the hosting, where the site lives; and the code and content, the files and everything on them. Hold all three and the site is yours to edit, move, or hand to someone else at any time. Hold none, and you are renting access to something registered in another person's name.

What does it actually mean to own your website?

  • The domain. Your web address, registered at a company called a registrar. You own it when the registrar account is in your name and you can log into it.
  • The hosting. The space where your site's files live and are served to visitors. You own it when the hosting account is in your name and billed to you.
  • The code and content. The files that make up the site, and the words and images on it. You own them when you can take a copy elsewhere without asking anyone.

Most people are sold a finished website and never told which of these three they actually hold. A site can look entirely yours on screen and still sit inside accounts you cannot open. The rest of this page is how to check, one piece at a time.

Do I own my domain name?

Your domain is your address on the web, and it is registered at a company called a registrar. To see which one, run your domain through ICANN Lookup at lookup.icann.org, the free tool ICANN operates for exactly this. It shows the registrar of record, the registration and expiry dates, and the nameservers, pulled in real time.

One catch: since the GDPR privacy rules took effect in 2018, registrars redact the personal contact details of individual owners, so you often will not see your own name in the result even on a domain you own. Business registrants are frequently still shown, but individuals usually are not. That means the lookup is not the real test of ownership. The real test is simpler: can you log into the registrar account yourself, and is it in your name or your email? If only your web designer can open it, the domain is registered, but not to you.

Do I own a domain bought through a website builder?

If you bought your domain through a website builder rather than a standalone registrar, the question is the same. A domain registered through a builder is still yours as long as the account is in your name and you are free to unlock it and transfer it away. The thing to check is not who you bought it from, but whether you could move it to another provider tomorrow without anyone's permission. If you cannot, you do not have full control of it yet.

Who hosts my website, and how do I find out?

Your host is wherever the site's files live and are served from. If you have forgotten who that is, there are three reliable ways to find out, in order of certainty.

  • Follow the invoice. Whoever charges you for hosting each month or year is your host, and that account should be in your name. This is the most reliable check, because hosting is a paid service and the bill always leads somewhere.
  • Check the nameservers. The same ICANN Lookup result lists your domain's nameservers, which point to whoever runs your DNS. That is often the same company as your host, and the name inside the nameserver is a strong clue.
  • Look for your login. If you can log into a hosting account and see your site's files or control panel, you have found your host. If you cannot, and you are not paying anyone, your site is very likely hosted inside someone else's account.

It is the same test as the domain: the question is not only where the site is hosted, but whether the hosting account is yours, in your name, on your card.

Do I own the code and content?

This is the piece people forget, because the site already looks like theirs on screen. The code is the set of files that make the site work. The content is the words, images and pages you put into it. You own them when you can get a complete copy and take it to another web person without asking for permission.

Check it with one question: could you hand your entire site to a different developer tomorrow? That means a copy of the files, or the ability to export your content, and an admin login that belongs to you. If the only working copy lives on your designer's computer or inside an account only they can open, you hold the site's appearance but not the site itself.

What should my web designer give me?

A straight answer from a web person sounds like this. They name your registrar and give you the login, or confirm the domain is already registered in your own account. They tell you where the site is hosted and that the account is in your name. They give you a way to edit your own content, and a way to take the files and content elsewhere if you ever leave. Nothing about your site lives somewhere you cannot reach.

A vague answer is the warning sign. "Don't worry, I handle all of that," or "it's on my account, I'll keep it running for you," or not being able to tell you who your registrar is: each of those means control sits with them, not you. It is a fair and ordinary thing to ask for, and a good answer is specific.

How should ownership be set up from the start?

The cleanest version of this is when ownership is never in question to begin with. At ADK Creatives, the domain and hosting are set up in your own accounts from day one, and the studio works with delegated access rather than holding anything itself. Nothing about your site sits inside the studio's accounts, so there is never a transfer to wait on at the end. You can change your own words and images whenever you like, your analytics live in your own account, and on a redesign your existing content is carried across as part of the job. You can read how that works on the page for web design built so ownership starts on day one.

What if you already do not own part of your site?

If you have checked and one of the three is not in your name, it can usually be moved. A domain can be transferred to a registrar account you control. Hosting can be moved to an account in your name. Content can be migrated to a site you own. None of it has to stay where it is.

This page is about knowing where you stand while you still have access. If you have already been locked out of your own accounts, or the person who built your site has gone quiet and will not hand anything over, that is a different and more urgent situation than the calm check described here, and there is a page for exactly that: how to recover your site when your web designer has disappeared.

When you do move, the standard to hold out for is the one above: a site where the domain, hosting and code are all in your name from the start. That is how ADK approaches every web build.

Want a site that is yours from day one?

Whether you are building fresh or moving a site you have lost hold of, the studio sets the domain, hosting and code up in your name from the start.

See how a build stays yours