Who actually owns your website and your domain?

"My website" sounds like one thing you either own or you do not. It is at least four things, and they can be held by four different parties, which is how a business that has paid for everything ends up controlling none of it.

The four things

The domain name. Your address on the internet. Owned by whoever is named as the registrant at the registrar, irrespective of who paid for it. This is the one that matters most and the one most often wrong.

The hosting. The account where the files sit. Belongs to whoever holds the account.

The content. Text and photographs. If you wrote and shot them, they are yours. If a copywriter or photographer was paid for them, ownership depends on the contract.

The design and code. Copyright in creative work generally stays with the creator unless it is assigned in writing or produced by an employee in the course of their job. A clause saying rights transfer on final payment is standard, and its absence is common.

In practice the last two rarely matter, because rebuilding is cheap now. The first two decide whether you have a problem.

Check it in ten minutes

The domain. Run your domain through a WHOIS lookup. Privacy services hide the individual's contact details, but you can see the registrar, the creation and expiry dates, and often the organisation. For .uk domains, Nominet's WHOIS shows more.

What you want to see: your business named as registrant, an email address you control, and an expiry date comfortably in the future with auto-renew on.

The hosting. Look for a recurring payment to a hosting company on your bank or card statements. If your supplier pays for it and bills you, the account is theirs, not yours.

The Google Business Profile. Sign in and check you are listed as owner rather than manager. Only the owner can transfer or remove it, and a profile owned by a former marketing agency is a genuine nuisance.

Why the registrant field matters so much

If a supplier registered the domain in their own name, they can, entirely lawfully, refuse to transfer it, let it expire, or point it somewhere else.

That is not a hypothetical. It leaves a business unable to use the address printed on its van, its invoices and every card it has handed out for six years, and unable to receive email at it.

Everything else is recoverable. New host, new site, new design, all achievable in days. The domain is the one asset where somebody else's name in a field is a real hold over you.

Fixing it

If the domain is in a supplier's name, ask for it, in writing, without drama:

Could you transfer the domain to our own registrar account, and send the authorisation code? Happy to cover any transfer fee.

Most people do it without complaint, because most of the time it was administrative convenience rather than a strategy. If they refuse or do not respond, go to the registrar, then to Nominet's dispute process for a .uk domain. The route exists, it is just slower than asking.

If hosting is in a supplier's name, either move it, or accept it and make sure you can get a copy of the site whenever you want one.

If the design rights were never assigned, it is worth an email asking for confirmation in writing. In practice, if the relationship ends badly you will rebuild rather than litigate, so treat this as tidiness rather than urgency.

Getting it right next time

One line in any web design agreement prevents almost all of this:

The domain will be registered in the client's name, with the client as registrant and administrative contact. The client will hold administrator access to hosting and the Google Business Profile.

If a supplier objects to that, you have learned something useful before signing rather than after. It is the first item in what to check in a quote, and it is first for a reason.

And if you are reading this because the relationship has already gone quiet, the recovery order is in my web designer has disappeared. Start with the domain.