Who should own your website domain? You. Always. It should be registered in your name, on an account you control, with credentials your organisation holds. That is the short answer and there are no good exceptions.
This is not about trust. It is about risk. A domain is a business asset with real value. It carries your SEO history, every inbound link, every email address on your letterhead. If someone else holds the registration and the relationship sours, you are negotiating for your own property.
Registration vs DNS: the distinction that matters
There are two separate things people blur when they talk about ‘owning’ a domain.
Domain registration is whose name is on the record with the registrar: Nominet for .co.uk domains, ICANN-accredited registrars for .com. This is legal ownership. It determines who can transfer, renew, or let the domain lapse.
DNS management is where the domain’s nameservers point. This controls which server your site loads from, where your email routes, and how subdomains behave. It is entirely normal (and often sensible) to point your nameservers at your hosting provider’s infrastructure or your agency’s Cloudflare account. That is operational delegation, not a transfer of ownership.
The rule is simple: you hold the registration; you delegate the DNS to whoever is managing your hosting and infrastructure. If they need to configure DNS records, they don’t need to own your domain to do it.
Where problems actually start
The risky scenario is not a hosting company or established agency managing your domain alongside your infrastructure. That can be a perfectly sound arrangement, particularly with providers whose core business is hosting and domain management.
The risky scenario is a freelancer or small supplier who registered the domain on your behalf as part of a website build, using their own reseller account, three years ago. You may not even know the registrar. You almost certainly don’t have login credentials. The domain is technically theirs.
This matters on exactly two occasions, and you won’t see them coming:
- You want to move. New agency, new hosting, new anything. The current holder has to initiate the transfer, and there is no legal mechanism that makes them do it quickly. Even well-intentioned people take weeks. Badly-intentioned ones take months and an invoice.
- The domain lapses. If it’s in someone else’s account, the renewal notices go to them. If they’ve gone out of business, changed email addresses, or simply stopped paying attention, your domain drops – and domain squatters monitor expiry lists in real time.
Neither situation is hypothetical. Domain disputes are one of the most common post-separation complications in the agency–client relationship. ICANN’s transfer dispute resolution process exists for a reason, but it is slow, procedural, and entirely avoidable.
What to check right now
Run a WHOIS lookup on your primary domain — lookup.icann.org for .com, nominet.uk/lookup for .co.uk. You are looking for:
- Registrant name. Is it your organisation, or someone else’s?
- Registrant contact email. Is it an address you control?
- Registrar. Do you have an account with them? Can you log in?
If the answer to any of those is no, you have a task on your list.
How to take control
If someone else currently holds registration, the process is a domain transfer. The steps:
- Ask the current holder to unlock the domain and provide the authorisation (EPP) code.
- Initiate a transfer to a registrar of your choosing: Cloudflare Registrar, Namecheap, Dynadot, or any reputable ICANN-accredited provider.
- Confirm the transfer via the email on the existing registration record (which is why step one needs the current holder’s cooperation).
- Once transferred, update the registrant details to your organisation.
The whole process typically takes five to seven days. It should cost nothing beyond the standard annual registration fee at the new registrar. If someone is charging you a transfer fee on top of that, push back; it is not standard practice.
Do this while the relationship is good. The best time to move a domain into your own account is before you need to.
