Who Owns Your Website Domain? How to Check and Fix It

The worry usually starts when a business owner wants to change developer, or a renewal email goes to someone else. Who owns my website domain, really? In short: the registrant, the person or business named as the holder on the domain registration, is the one the registrar and registry deal with, and who holds the rights that come with the registration, such as transferring it ^[1]. Not whoever built the site, and not whoever hosts it. If there is a genuine dispute about who is entitled to the name, that is a legal question for professional advice. The fix, if the wrong name is on it, is usually straightforward once you know where to look.

Registrant, registrar and host: who is who

• Registrant: the registered holder of the domain, which one hosting company says should be the company or person that truly owns the brand ^[4].
• Registrar: the company you bought the domain through, which manages the registration. Name.com explains that the registrar field tells you where the domain was bought, while the registrant is whoever owns it ^[6].
• Host: the company whose servers run your website. The company holding the hosting account is not necessarily the same as the domain registrant ^[4].

Your domain, your hosting and your website's code are three separate things, and each can be in a different name. Owning the domain does not automatically mean you own the code or content; that comes down to what your build agreement says, so get it in writing. If you are still choosing a name, start with how to choose a domain name.

How to find out who owns a domain

The public lookup is called WHOIS, and ICANN's lookup tool is a good starting point ^[5]. Search your domain and look for the registrant fields.

Do not be alarmed if it shows "REDACTED FOR PRIVACY". The vast majority of newly registered domains now use some form of privacy protection ^[5], so the public record often hides the owner. There is one exception to watch: with proxy registration, a third party is listed as the legal registrant, so the proxy technically "owns" the domain to the outside world ^[6].

Because WHOIS often hides the answer, the practical checks matter more:

• Can you log in to the registrar account yourself?
• Is the registrant email an address you control, on a domain you own?
• Are the renewal invoices in your business's name?

If any answer is no, you do not fully control your domain yet.

My developer registered my domain: how do I get access?

This happens more often than you would think. One hosting company describes the pattern: domains are often bought in a hurry, a colleague uses a personal card, an agency registers the domain to save time, or an old IT provider keeps everything under their own name ^[4]. It only becomes a problem when you need to move hosting or recover access ^[4].

Usually it is an oversight, not bad intent. Start with a polite written request:

• Ask for the registrant details to be changed to your business, with your email address. If you also plan to move the domain to another registrar, check the registrar's change-of-registrant and transfer-lock rules first, because changing registrant details can trigger a temporary lock on transfers ^[1].
• Ask for your own login to the registrar account, or for the domain to be moved to an account you hold.
• Ask for the authorisation code if you want to move it to another registrar.

For .com and similar domains, ICANN is clear that transferring between registrars is your right, that your registrar must provide the authorisation code within five calendar days of your request, and that a transfer cannot be denied because you have not paid the transfer fee ^[1]. A registrar can refuse in some limited cases, such as recent changes that trigger a lock ^[1], so a delay is not always bad faith. If you cannot reach the person at all, contact the registrar about its ownership dispute process, and get legal advice if needed. Choosing a developer who hands over cleanly avoids all of this; see how to choose a web developer.

How to transfer a .co.za domain

This is where South African guides and global guides differ. .co.za domains do not follow exactly the same process as .com. For .co.za and .org.za, transfers work through a voting process: the current registrar sends a voting ticket to the registrant email address, which is the only address authorised to accept the transfer ^[2], and the registrant has five days to accept ^[2].

At South African registrars, the authorisation code is also sent to the registrant email address ^[3]. That is why the registrant email is the real control point for a .co.za. If it goes to your old developer, they effectively hold the keys.

The reassuring part: a transfer moves the management of your domain from one registrar to another while you keep ownership, and ownership of the domain remains unchanged ^[3].

“For a .co.za, whoever reads the registrant email controls the transfer. Make sure it is you.”

Signs your domain is not really in your control

• Renewal reminders go to someone else, or you never see them.
• You have never logged in to the registrar account, or do not know which registrar it is.
• Your email address on the domain was set up by someone who has since left.
• Your developer has to make every DNS change for you, even small ones.

None of these means anyone has acted in bad faith. They mean the control sits with someone else, which is fine until the day you need it.

How I keep clients owning their own domains

I run every build with a client portal and a dated decision log, as I describe in how I run client web projects. Every scope, commercial and technical call goes into that log with a date, and in my view where the domain is registered and who holds the login belong there too. Months later, "who owns this?" should have a written answer, not a guess.

That is the habit worth asking any developer about: not just whether you will own the domain, but where that will be recorded.

What to do next

• Look up your domain on ICANN's WHOIS lookup and note the registrar.
• Confirm you can log in to the registrar account and that the registrant email is yours.
• If someone else holds it, ask in writing for the registrant details and access to be handed over.
• For a .co.za, make sure the registrant email reaches you before starting any transfer.
• Get domain, hosting and code ownership written into your agreement with any developer.
• Keep a one-page record of your registrar, host, email provider, logins and renewal dates somewhere only you control.

If you are not sure who controls your domain, send me the address and I will help you work out where it sits and how to get it into your name.