[ Technical ]

Registrar vs Registry: What Is the Difference?

You register domains with a registrar. The registry owns the TLD. They are different organisations with different roles — and the distinction matters when something goes wrong.

· · 5 min read

Registrar vs Registry: What Is the Difference?

Most people interact with one organisation when they buy a domain — a registrar like Namecheap, GoDaddy, or Cloudflare. Behind that transaction is a separate organisation they never deal with directly: the registry. Understanding the difference matters when domains are transferred, disputed, or suspended.

The Registry

A registry operates a TLD. Verisign operates .com and .net. Afilias operates .info. DENIC operates .de. For new gTLDs, various private operators hold registry agreements with ICANN.

The registry:

  • Maintains the authoritative database of all registered domains under that TLD
  • Sets the wholesale price for registrations (registrars pay this per registration)
  • Controls the registry DNS — the TLD's authoritative nameservers
  • Enforces registry-level policies (name restrictions, reserved domains, etc.)
  • Handles EPP status codes like serverHold or serverTransferProhibited

The registry does not interact with end customers. You cannot register a domain directly with Verisign.

The Registrar

A registrar is an ICANN-accredited reseller with access to one or more registries. You register, renew, and transfer domains through the registrar.

The registrar:

  • Provides the customer-facing interface (DNS management, WHOIS privacy, domain forwarding)
  • Sets the retail price (markup over registry wholesale)
  • Manages your account, handles payment, and sends renewal notices
  • Applies client-level EPP locks (clientTransferProhibited, clientDeleteProhibited)
  • Handles disputes and technical support at the customer level

Why the Distinction Matters

Transfers

When you transfer a domain between registrars, the process involves:

  1. Unlocking the domain at the registrar level (removing clientTransferProhibited)
  2. Obtaining an authorisation code (EPP auth code / transfer key) from the current registrar
  3. Initiating the transfer at the new registrar
  4. The old registrar has 5 days to approve or deny

The registry processes the actual transfer once approved. Delays are usually at the registrar level — not the registry.

Suspensions

If a domain is suspended, the reason determines who can fix it:

  • clientHold (set by registrar) → contact your registrar
  • serverHold (set by registry) → contact the registry, often requires legal or policy action, not just a support ticket
  • redemptionPeriod (set by registry after registrar deletion) → contact your registrar for redemption, but the fee and timeline are registry-defined

Price Changes

Registries set wholesale prices, which registrars pass through with varying markups. ICANN removed price caps on many legacy TLDs in 2019, allowing Verisign and others to raise .com and .net prices annually. When you see a domain renewing at a higher price than it originally cost, the increase typically originates at the registry.

The ICANN Layer

Both registries and registrars operate under contracts with ICANN (Internet Corporation for Assigned Names and Numbers). ICANN does not run registries or registrars — it sets policy and accredits the organisations that do.

For domain disputes (UDRP complaints), the process is administered through ICANN-approved dispute resolution providers like WIPO or NAF, operating independently from both registrar and registry.

What You See in RDAP

The RDAP response for a domain includes both registrar and registry data:

"entities": [
  {
    "roles": ["registrar"],
    "publicIds": [{ "type": "IANA Registrar ID", "identifier": "1068" }],
    "vcardArray": [...] // registrar name and contact
  }
]

The registrar field in BatchDomain's results is populated from this entity data. The registry itself is implicit from the TLD — .com means Verisign is the registry regardless of which registrar you used.