Ddeepnom

BlogDomain Education

Registrars, registries, and ICANN — who actually controls a domain name

A clear map of the three layers of the domain system — why your name is managed by a registrar, tracked by a registry, and governed by ICANN — and what that means when something goes wrong.

The Deepnom Desk·April 17, 2026·3 min read·9 views
Registrars, registries, and ICANN — who actually controls a domain name

When you buy a domain, you’re interacting with a chain of organizations whose roles are easy to confuse. Knowing which layer handles what saves time when transfers stall, prices change, or a dispute arises. This is the short version.

The three layers

Three groups sit between you and your domain name.

Registrars are the companies you buy domains from — GoDaddy, Namecheap, Cloudflare Registrar, Porkbun, and hundreds of smaller resellers. A registrar’s job is to sell you domains, manage your DNS, bill you, and act as your interface to the registries above them.

Registries sit one level up. Each top-level domain (.com, .net, .io, .xyz) has exactly one registry that operates its database. Verisign operates .com and .net. Identity Digital operates dozens of newer TLDs. Afilias runs .info. The registry is the authoritative source of truth for which domain names exist under its TLD and who currently holds them.

ICANN (the Internet Corporation for Assigned Names and Numbers) is the non-profit at the top. It doesn’t run any specific TLD — it sets the rules, accredits registrars, delegates TLDs to registries, and handles disputes. When people say “ICANN charges $0.18 per domain,” they mean ICANN collects a small fee from registries and registrars that ultimately lands in your annual renewal cost.

What actually happens when you buy a domain

The transaction looks like this:

  1. You register example.com at Namecheap.
  2. Namecheap (a registrar) forwards the request to Verisign (the .com registry).
  3. Verisign writes you into the .com zone database.
  4. Namecheap writes you into their customer database as the holder.
  5. ICANN oversees the rules both parties operated under.

The domain is yours but it lives in three databases simultaneously: ICANN’s accreditation records, Verisign’s zone file, and Namecheap’s customer records.

Why this matters in practice

A few real-world consequences:

Transferring your domain moves it between registrars, not between registries. Moving example.com from GoDaddy to Porkbun changes the registrar of record but the domain stays in Verisign’s .com zone. This is why transfers are fast and cheap — nothing fundamental changes, only the billing relationship.

Losing access to your registrar does not lose the domain. If your Namecheap account is compromised, the domain still exists at Verisign. You can work with Namecheap’s support (or escalate to ICANN if needed) to regain control. This is your safety net.

Pricing floors are set at the registry. Verisign sets the wholesale price of .com; registrars add their margin. When Verisign raises wholesale .com prices, every registrar’s retail price rises too. Shopping between registrars optimizes the margin, not the underlying cost.

TLD-specific quirks come from the registry. Some TLDs have premium pricing tiers (a dictionary-word .xyz can cost $500/year). Some have trademark-based restrictions. Some require a physical address in a specific country. These rules are set by the registry, not the registrar.

When things go wrong, escalate up the chain

Small issues — renewal billing, DNS not propagating, support unresponsiveness — are registrar problems. Start there.

Medium issues — transfer disputes, ownership challenges, bad-faith registrations — can escalate to the registry or to ICANN’s accredited-registrar rules. ICANN has a formal dispute process (UDRP) for trademark-based claims.

Extreme issues — TLD going under, court-ordered seizures, national-level takedowns — involve ICANN and sometimes governments. You will likely never deal with these unless you hold a domain in a legally contested space.

Practical takeaways

The three-layer system looks complicated on paper but is mostly invisible in daily use. You interact with your registrar, your registrar interacts with everything else. When something breaks, knowing which layer owns the problem tells you where to send the support ticket.

Edit

More from the blog