Who owns a domain name?
A domain has a registrant, a registrar, and an account holder, and they are often three different parties. The one that matters when something goes wrong is the one with the login. Here is how to tell them apart, look a domain up, and get control back.
Last changed 26 October 2026, about 6 minutes to read
Three parties, three different things
- The registrant is the person or company the domain is registered to: the name on the record at the registry. That is who the domain belongs to.
- The registrar is the company the domain was registered through: GoDaddy, Cloudflare, Namecheap, a local registrar, often the web host. The registrant can move the domain to another registrar.
- The account holder is whoever has the login to the registrar account the domain sits in. This is the one that counts day to day: the account holder can change the nameservers, renew or not renew, and move the domain, whatever the record says.
The trouble comes when the registrant is the client, the account holder is a developer who registered it on their own account in 2019, and the renewal is charged to that developer’s card. Everything works until the developer leaves or the card expires.
How to look a domain up
Every registry publishes some of this. The domain expiry checker reads the registry’s own records (RDAP, or WHOIS for the registries without it, such as .co.za) and shows the registrar, the expiry date, whether the domain is locked against transfer, and whether it is on hold.
The registrant’s name and contact details are usually hidden now, behind privacy services or the registry’s own rules, so a lookup rarely tells you who the registrant is. It tells you where the domain is held, which is where to ask.
The nameservers, from the who-hosts check, say who serves the DNS, which is often a different company again and another account to find.
What owning the domain actually gives you
Registering a domain gives you the right to use it for the period paid, under the registry’s rules, and the right to renew it. It does not give you the website, the email or the content on it; those live in other accounts. And the rights sit with the registrant, so a domain registered in a developer’s name is, as far as the registry is concerned, the developer’s. This is not legal advice; disputes over domains have their own procedures, and a lawyer who knows them is the right call for a real dispute.
Getting control back
- If the registrant is right but someone else holds the account: ask them to transfer the domain into an account you control, at the same registrar or another. Transfers between registrars need the lock off and an authorisation code, and take up to five days. If they will not cooperate, the registrar’s own process for a registrant to recover a domain from an account they do not control is the next step, and it needs proof of who you are.
- If the registrant is wrong: ask the current registrant to update it, in writing. A registrant change at most registrars is a few clicks; refusing to make it is where disputes start.
- Then lock it, in your own account, on your own card. Turn on the transfer lock, turn on auto-renew, make sure the card belongs to the company and that someone checks the renewal notices.
Write down who holds it
The domain is the one layer with nothing above it: if it goes, nothing on the other layers can bring it back. Record the registrar, the account holder, where that login lives, who pays and the expiry date, with a date on each answer. Stackbrace keeps exactly that record for each site, warns 30, 14, 7 and 1 days before a domain runs out, and alerts at once when the nameservers or the registrar change, which is how a hijack shows first. Check a site now.