Who Actually Controls Your Domain Name, and How to Find Out

Find Out in Two Minutes

Look your domain up at lookup.icann.org, where the Registrar field shows who your registrar is (ICANN, 2026). Then answer a harder question: can you personally log in to that registrar account, or does somebody else hold the login.

Start with the fact rather than the assumption, because the assumption is wrong more often than owners expect.

If you do not know who your registrar is, ICANN says you can look it up by searching for your domain name at lookup.icann.org, and that the Registrar field shows you who your registrar is (ICANN, 2026). That takes about thirty seconds and tells you which company the domain actually sits with.

The second question is the one that matters more, and no lookup can answer it: can you log into that account yourself, right now, without asking anyone. Knowing the registrar is not control. Holding the credentials is.

Three separate things get confused here and they can sit in three different places. The registrar is where the domain is registered. DNS is what points the domain at a server, and may be run somewhere else entirely. Hosting is where the website files actually live. An owner can genuinely control one of those and none of the others, which is why the honest answer to who controls your website is often more complicated than the person answering realizes.

What You Are Actually Entitled To

ICANN states plainly that it is your right to transfer your domain name registrations between registrars, that an Auth-Code is required to do so, and that your registrar must provide you with that code within five calendar days of your request (ICANN, 2026).

Owners in a bad relationship with a provider often assume they are stuck. Usually they are not, and the rules are more on their side than they expect.

ICANN states that it is your right to transfer your domain name registrations between registrars (ICANN, 2026). That is the starting position, not a favor that has to be negotiated.

The practical instrument is the authorization code, also called an Auth-Code, AuthInfo code, EPP code or transfer code. ICANN describes it as a code created by a registrar to help identify the domain name holder and prevent unauthorized transfers, states that it is required in order to transfer a domain from one registrar to another, and says that your registrar must provide you with the AuthInfo code within five calendar days of your request (ICANN, 2026).

Five calendar days is a specific, quotable obligation, and it is worth knowing before you ask rather than after. A provider stalling for a month on a code they are obliged to supply within five days is not experiencing a delay, and being able to say so calmly and precisely usually resolves the situation faster than any amount of frustration.

The Only Reasons a Transfer Can Be Refused

The list is short and defined. A registrar may deny for fraud, a genuine identity dispute, money owed on a previous registration period, written objection from the holder, lock status, or within 60 days of initial registration or a previous transfer, and it is required to specify a reason when it denies (ICANN, 2026).

This is the section worth keeping, because a refusal that sounds official often is not.

ICANN lists the limited circumstances in which a registrar may deny a transfer request: evidence of fraud, a reasonable dispute over the identity of the person authorizing the transfer, the domain being on hold due to payment owed for a previous registration period, an express written objection from the domain name holder, the domain being in Lock status, being within 60 days of initial registration, or being within 60 days of a previous transfer (ICANN, 2026).

On Lock status specifically, ICANN notes that registrars must provide a readily accessible and reasonable means for name holders to remove it (ICANN, 2026). A lock is not a wall. It is a switch you are entitled to reach.

There is also a shorter list of circumstances in which a registrar must deny: a UDRP proceeding, a court order from a court of competent jurisdiction, a TDRP proceeding, a URS proceeding or suspension, or a domain subject to the 60-Day Change of Registrant lock (ICANN, 2026).

And the sentence that does the most work in a difficult conversation: your registrar is required to specify a reason when denying your transfer request (ICANN, 2026). Vagueness is not one of the permitted grounds, so asking which specific listed reason applies is a reasonable and answerable question.

The Lock Most People Trip Over Is One They Caused

You cannot transfer to a different registrar within 60 days of changing the registrant name, organization or email address (ICANN, 2026). Tidying up your contact details immediately before a planned move is the most common way owners lock themselves out of it.

There is a particular trap here that catches careful people, precisely because they were being careful.

ICANN states that you cannot transfer a domain name to a different registrar within 60 days of making changes to the registrant name, organization or email address, or the administrative contact email address where there is no registrant email address (ICANN, 2026). Some registrars may offer an option to opt out of that lock at their discretion, but they are not required to, and ICANN notes the rule exists to protect against unauthorized transfers (ICANN, 2026).

Picture how that happens in practice. An owner decides to get organized. They update the domain from a former employee’s email to their own, or correct the company name after an incorporation change. Sensible housekeeping, and it starts a 60-day clock on a move they were planning for next week.

ICANN’s own advice on the sequencing is the useful takeaway: if your ultimate goal is to transfer the domain name, consider completing the transfer process before changing your contact information (ICANN, 2026). Move first, tidy second.

You Probably Do Not Need to Transfer the Registrar at All

ICANN notes you may change web hosting providers instead of registrars, avoiding the inter-registrar transfer process and lock altogether, and that you may update your nameservers or the hosting IP address assigned to your domain (ICANN, 2026). Most of the friction above does not apply to changing where a site is hosted.

Everything above concerns moving the registration itself. Changing where your website is hosted is a smaller operation, and conflating the two costs people weeks.

ICANN states that you may have the option to change web-hosting providers instead of registrars, avoiding the inter-registrar transfer process and the lock altogether, and that you may update your domain name’s nameservers or change the hosting IP address assigned to your domain (ICANN, 2026).

That is worth reading twice if you are considering a move. The 60-day locks, the authorization code and the denial grounds all govern moving the registration between registrars. Pointing an existing domain at a new host is a DNS change made from inside the account you already have, and none of that machinery is involved.

It also keeps you inside the lower risk category from a search perspective, because the URLs do not change. Google treats a hosting or CDN change that keeps the same URLs as its own case and documents the expected effect as a temporary drop in Googlebot crawl rate that recovers over the following days (Google, 2026).

So the honest sequence for most businesses is: confirm you can log in to the registrar, keep the registration where it is if that is easier, and change only what actually needs to change. If you would rather have the current picture measured than assumed, our site migration service covers the move properly, and our free audit reports what is publicly reachable and readable on your domain and costs nothing.