Registrars & registries

What is a domain registrar (vs. a registry vs. a host)?

Three roles that often get mixed up — and which one to talk to when something goes wrong.

When you buy a domain, three different organizations are usually involved. They all have similar-sounding names, they all play a part in making your domain work, and they are easy to confuse. Knowing which one does what saves a lot of time when something breaks — and prevents you from arguing with the wrong company's support team.

The registry

The registry is the organization that operates a top-level domain. Verisign runs .com and .net. Public Interest Registry runs .org. Identity Digital runs hundreds of new gTLDs like .info, .live, and .xyz. Nominet runs .uk. There is exactly one registry per TLD, and they maintain the master database of every domain registered under it. The registry sets the rules — wholesale pricing, what characters are allowed, what happens at expiry, who is eligible to register — and they publish the data that WHOIS and RDAP queries return.

Registries do not normally sell domains directly to the public. They wholesale them to accredited registrars, who handle the customer-facing side.

The registrar

The registrar is the company you buy your domain from. Names like GoDaddy, Namecheap, Cloudflare Registrar, Squarespace Domains (formerly Google Domains), and Porkbun are all registrars. They are accredited by ICANN (and by individual ccTLD registries) to sell domains on behalf of the registry. Your control panel, your renewal notices, your billing, your support tickets — all of that lives at the registrar. When you change nameservers or update contact details, your registrar pushes the change to the registry on your behalf using the EPP protocol.

The host

The host is wherever your website, email, or app actually lives. That might be a shared hosting provider, a cloud platform like Vercel or Replit, an email service like Fastmail or Google Workspace, a CDN that fronts your origin, or a server you run yourself. The host has nothing to do with the registration of the domain — it just receives traffic that DNS sends to it. A host typically gives you an IP address or a hostname to point your DNS records at.

Which one do I talk to?

  • Renewing, transferring, or canceling a domain — your registrar.
  • Updating nameservers or DNS records — usually your registrar, sometimes a separate DNS host if you use one.
  • Website not loading — usually your host, unless DNS itself is broken.
  • Email not arriving — your email host (and check the MX records at your DNS host).
  • Need to dispute ownership of a domain — the registry, via the appropriate UDRP or local dispute procedure.
  • WHOIS shows the wrong contact info — your registrar.

Related guides

  • gTLDs vs ccTLDs

    The difference between generic top-level domains like .com and country-code domains like .uk.

  • How to transfer a domain

    Auth codes, transfer locks, and what actually happens when you move a domain between registrars.

  • Nameservers and DNS basics

    How a domain becomes a working website or email address — explained without the jargon.