← All articles

Who Actually Owns Your Website?

March 14, 2026 · 4 min read · by the upkept/dev team

Owning your website is not one thing, it is four: the domain name, the hosting, the website files and code, and the logins to all of it. You can have paid for a site in full and still not control it, because the person who built it registered everything under their own account. If any of these four sits with someone else, you do not fully own your site. Here is how to check each one, and what to do if the answer is not you.

The four things you need to own

  1. The domain name. Your web address. Whoever holds the registration controls where the address points, which means they control your site and email.
  2. The hosting. The server your files live on. Whoever owns the account can move, suspend, or delete the site.
  3. The website files and code. The actual site. You want a copy and the right to take it elsewhere.
  4. The accounts and logins. Admin access, the registrar, the host, any third-party services. Without these you cannot make changes or move.

Own all four and you are free to leave any provider. Miss one and you can get stuck.

How do I check who owns my domain?

Start with the domain, because it is the one people most often do not control and the one that hurts most to lose. Look up your domain in ICANN's public lookup tool. It shows the registrar and, unless privacy protection is on, the registered contact.

If the details are yours, or your company's, good. If they are your developer's, or an agency you no longer work with, that is a problem to fix now rather than during a dispute. Even with privacy protection on, the key question is simple: do you have the login to the registrar account? If not, you do not control the domain.

Checking hosting, code, and accounts

For hosting, ask yourself whether you have a login to the hosting account in your name. If you only ever deal with your developer and have never seen a hosting bill or dashboard, the account is probably theirs.

For the code, you want a full backup of your site and confirmation that you are allowed to move it. Some page builders and proprietary platforms make this genuinely hard, so ask specifically.

For accounts, make a list: registrar, host, CMS admin, analytics, any plugins with their own logins. You want every one of them accessible under your own credentials, not your developer's personal account.

What to do if you do not own everything

Do not wait for a falling-out to sort this. It is far easier while the relationship is good.

  1. Ask, in writing and politely, to have the domain, hosting, and accounts transferred into your name, and for a full backup of the site.
  2. A cooperative developer will do this without fuss. It is normal and reasonable.
  3. If they resist or stall, that tells you something, and getting access when a developer will not reply covers your options.

If you are about to hire someone, put this in the agreement up front, so the domain, hosting, code, and accounts are all registered in your name from the start.

What to do next

Look your domain up in ICANN Lookup right now, then check whether you have logins to your hosting and registrar in your own name. If you can log in to all of it, you are in a strong position. If you cannot, start the transfer conversation this week, while it is a routine request rather than a dispute. If you are inheriting a site from a previous developer and are not sure what you have, taking over a website from another developer walks through the handover.

Part of our guide to website problems.

Not sure what is actually wrong with your site?

Our $250 site health audit checks performance, security, broken forms, and outdated dependencies. You get a written report and a prioritised fix list, credited toward your first month if you start maintenance within 30 days.

Book the $250 site health audit