Who owns your domain name (and how to check)

The check that settles it

Most people arrive at this question sideways. A renewal notice turns up addressed to a name you only half recognise, or the person who built the site five years ago stops answering emails, or a new supplier asks for details you cannot produce and you realise you have never once seen the account the domain lives in.

The answer is written down in one place, and it is not a search engine. Log in to the account at the registrar where the domain is held and read the registration details yourself. Four things are worth reading while you are in there: the registrant name, whether the admin contact is an address somebody actually reads, the renewal date, and who else holds the login. The small business website security checklist puts that on a wider list of things to check when nothing is wrong; this is the long version of it.

If you cannot log in at all, you have still learned something. It means somebody else holds the account, and the rest of this is about what to do next.

Why a WHOIS search will not tell you

The standard advice for this question is to run a WHOIS lookup, and for a UK business it mostly does not work. Nominet is the registry behind the whole .uk namespace, which covers .uk, .co.uk, .org.uk and .me.uk. On those domains the public record does not show the registrant's name or address unless the registrant has given explicit consent for that data to be published, a change made for data protection reasons.

So a blank result is not evidence of anything. It does not mean the domain is yours and it does not mean it belongs to somebody else. Almost every guide written for this search term hands you a lookup tool anyway, because those guides are written for people trying to find the owner of a domain they want to buy, not for a business checking its own.

Nominet is also phasing the .uk WHOIS service out, and has advised registrars to move to the Registration Data Access Protocol, or RDAP, instead. That is a change for registrars to handle rather than anything you need to act on.

The way this usually goes wrong

The common failure here has nothing to do with hacking. It is that the domain was registered by whoever built the site, in their own name or under their own account, rather than in the name of the business paying for it. WebSmiths, a web design firm writing about its own trade, calls this a documented and common problem, and the consequence is the part that bites: the party named as registrant is the one legally able to control the renewal, the DNS and any future transfer.

It is rarely a trap. A designer registers the domain on the client's behalf because it is quicker than talking a busy plumber through a registrar signup, means to hand it over properly later, and never gets round to it. The arrangement holds for years, right up to the week the designer retires, falls out with you, or stops replying.

Two questions sort most people quickly. Have you ever logged in to a registrar account yourself, and can you name the company the domain is held with? If renewal reminders go somewhere else, or you have never seen one, that is the same answer arriving by another route. So is a launch that came with no handover conversation and no login details. Whose name the domain is in is one of the things a website quote quietly leaves out, which is why it tends to surface years later rather than at the start.

If the registrant is not you

Start by asking, because in most cases that is the whole fix. A short email to whoever registered it, asking for one of two things: that the registrant details are changed to your business name, or that the domain is moved into an account you control. Say which one you want rather than leaving it open, and expect the change of registrant to be the smaller job of the two.

Before you send it, work out which kind of domain you have. The mechanics are genuinely different for a .co.uk and a .com, and asking for the wrong thing is how these conversations stall for a fortnight.

A .co.uk does not move the way a .com does

Most transfer guides describe an authorisation code, also called an EPP code: a per-domain password you get from the current registrar and hand to the new one. That is how the generic extensions work. Under the ICANN Transfer Authorization Code policy, which took effect on 19 November 2024, the code for a .com, .net or .org is generated on demand and valid for no more than 14 calendar days, so there is no sense asking for one weeks before you plan to move.

A .uk or .co.uk domain does not use that system at all. Those domains move between registrars using an IPS tag, which identifies the registrar the domain is going to rather than acting as a password for one domain. If somebody tells you they cannot find the auth code for your .co.uk, that is because there is not one.

One more thing if you are dealing with a .com. ICANN's rules lock a domain against transfer to a new registrar for 60 days after a change of registrant, a rule that took effect on 1 December 2016 and applies to domains under the ICANN-contracted registries. Change the name on the record and then try to move the domain the same week, and that is the wall you hit. It is not established that the same lock applies to .co.uk domains, so do not assume it either way.

What owning it properly looks like

Once the name on the record is right, keeping it right is mostly dull habit. The renewal date sits in a calendar somewhere instead of arriving as a surprise, and the contact address on the registration is one somebody still reads. The login belongs to the business rather than to a person, so it survives that person leaving.

None of that means doing the work yourself. A designer, an agency or an IT person can hold access and handle renewals perfectly well, and most small businesses are better off for it. The distinction is between somebody managing the domain for you and somebody owning it instead of you, and the registrant name is what decides which of those you have got.

The questions that come up

Who legally owns a domain name, the person who registered it or the business that uses it? The registrant on the registration record, which is exactly why that name is the thing worth checking. Paying every invoice, running your email on it and building ten years of business on top of it do not change what the record says.

Why can I not find the registrant's name on a WHOIS search for my .co.uk domain? Because Nominet does not publish it without the registrant's explicit consent. The absence of a name there is not a sign that anything is wrong.

What if the person who registered it has disappeared? Then it becomes a recovery job rather than a polite email, and it is worth getting somebody who has done it before to take it on.

What happens if a domain is allowed to lapse? The website and the email go with it, because both hang off the domain rather than the other way round. Whether it can be recovered after that, and at what cost, depends on your registrar and the type of domain, so ask yours rather than trusting a general figure off the internet.

How I handle it, and what to do if it has already gone wrong

Every site I look after has the domain registered in the client's name, and it stays there. The domain and its renewal are part of the care plan rather than a separate thing for you to remember, and the domain, the content and the accounts are in the client's name throughout, so there is nothing to argue about if you ever decide to leave. Moving an existing domain over is free. The services page sets out what that covers.

If the check at the top of this page came back badly, that is a job rather than a disaster. Website rescue and moves is built for this: a developer who has disappeared, or a handover that never happened, with the domain and the email taken over alongside the site itself.

Do the check today

Log in and read the registrant name. It is a short job if you hold the login, and it tells you something you need to know if you do not. Either way it is a better use of a morning than finding out mid-argument, or a week after a renewal nobody was watching.