Domain registrar — Which of the Four Companies Actually Holds Your Name?

Registries wholesale a namespace under an accreditation agreement and registrars retail it. The agreement is what obliges a registrar to keep the registrant record, to supply transfer credentials within defined timeframes on generic endings, and to publish a route for complaints. It is the reason a domain is portable at all.

Resellers sit on top of that. Buying through a reseller is perfectly ordinary and often cheaper, but it inserts a party with no direct authority at the registry. When something needs escalating, the reseller has to ask the registrar — and you cannot skip that queue unless you know who the registrar is.

On generic endings the registrar must maintain accurate registrant data, act on the registrant's instructions, supply the transfer authorisation code within the timeframes the policy sets, and not hold a name hostage. There is an escalation route above the registrar for when it does not, and that route exists precisely because names are valuable.

Country registries impose their own equivalents on their own accredited members. The obligations differ in detail; the principle that the registration is yours rather than the registrar's is common to both.

Look the name up over WHOIS or RDAP. The output names the registrar of record and, on generic endings, its IANA identifier. The status codes tell you whether a registrar lock is set. The dates tell you when the registration was created, last changed and expires.

If that registrar is not the company you pay, you have a reseller relationship — worth knowing before an emergency rather than during one.

The exit test. How a registrar behaves on the way out tells you more than its pricing page. The tests are simple: does it publish the transfer process, does it produce the auth code without a phone call, does it lift the lock when asked, and does it stop billing when you leave. A registrar that treats departure as a negotiation has told you exactly what it thinks the name is.

Our own answer is a request and a toggle in the client area. Unlock, take the code, go — and whatever term remains on the registration travels with the name.

Moving the registrar without moving the site. A registrar transfer moves the registration and nothing else. The zone does not follow it. If the gaining registrar starts you on default nameservers, the site and the mail stop the moment the delegation changes, and none of that is the registry's fault.

The safe order: copy the current zone out, recreate it where you are going, confirm the records answer, then transfer. Do that and the transfer is invisible to visitors.