Registrar vs Registry: What Each One Actually Does
"Registrar" and "registry" sound like they might be interchangeable terms for the same thing, and the confusion is understandable — most domain buyers only ever interact with one of them directly. But they're distinct roles in the domain system, with different responsibilities, different customers, and an important hierarchy between them that explains a lot about how domain pricing, availability, and policy actually work.
The Registry: One Per Top-Level Domain
A registry is the organization responsible for operating a specific top-level domain's authoritative database — maintaining the master record of every registered domain under that extension, running the TLD's core DNS infrastructure, and setting policies specific to that extension (pricing wholesale rates, any eligibility restrictions, and technical requirements). There's exactly one registry per TLD: Verisign operates .com and .net, Public Interest Registry (PIR) operates .org, and each ccTLD has its own designated national or territorial registry operator, as discussed in the piece on ccTLD residency rules elsewhere on this blog.
The Registrar: Your Actual Point of Contact
A registrar is the ICANN-accredited company you actually interact with to register, renew, and manage a domain — GoDaddy, Namecheap, Google Domains' successor Squarespace Domains, and hundreds of others. Registrars don't operate the underlying TLD infrastructure themselves; instead, they're authorized resellers with a direct technical and contractual relationship to one or more registries, submitting registration, renewal, and transfer requests to the registry's systems on a customer's behalf through a standardized protocol (EPP, the Extensible Provisioning Protocol).
Why This Two-Tier Structure Exists
The separation was a deliberate policy decision, formalized when ICANN was established in the late 1990s specifically to introduce competition into what had previously been a single-company monopoly over domain registration. By splitting the registry function (running the authoritative database for a TLD, a natural single-operator role) from the registrar function (selling and servicing registrations, an inherently competitive retail role), the system allows dozens of competing registrars to sell the same .com domains at different prices and service levels, while all ultimately writing to the same single, authoritative Verisign-operated registry database underneath.
What This Explains About Domain Pricing
Every registry sets a wholesale price it charges registrars per domain, per year, for each TLD it operates — this wholesale rate is a real cost floor that every registrar building a retail price on top of it has to account for. This is why certain "premium" TLDs (some newer generic extensions with a higher registry-level base cost) show meaningfully higher prices across every registrar simultaneously, regardless of which one you use — the price floor is set at the registry level, and registrar competition only affects the margin layered on top of it, not the underlying wholesale cost itself.
Why Some Registries Have More Policy Latitude Than Others
It's worth knowing that legacy gTLDs like .com operate under long-standing agreements with ICANN that constrain how much the registry can change wholesale pricing or policy unilaterally, providing a degree of long-term stability that both registrars and registrants have come to rely on. Newer gTLDs, launched under ICANN's expanded program, generally operate under more flexible agreements giving their registry operators somewhat greater latitude over pricing and policy changes, which is part of why pricing volatility and occasional significant fee increases have been more commonly reported among some newer extensions than among the older, more heavily constrained legacy TLDs.
What Happens if a Registrar Goes Out of Business
Understanding the registry/registrar split also explains why a registrar failing doesn't mean your domain simply vanishes. Because the registry maintains the authoritative record independent of any single registrar, ICANN has an established de-accreditation and transfer process for exactly this scenario — domains under a failed or de-accredited registrar get bulk-transferred to a designated successor registrar, preserving the underlying registration even though the original point-of-sale company is gone. This is a direct, structural consequence of the registry being the permanent record-keeper and the registrar being a replaceable retail layer on top of it. Customers affected by this kind of bulk transfer are typically notified by the successor registrar and given an opportunity to move the domain elsewhere afterward if they prefer, but critically, the domain's registration itself is never actually at risk purely from a registrar's business failure — the risk that does exist involves account access and billing continuity during the transition, not the underlying registration disappearing.
Why This Matters When Something Goes Wrong
Knowing which layer actually controls what helps direct support escalation correctly. A registrar's customer support can help with account access, billing, and standard management tasks — but registry-level policy questions (like a ccTLD's eligibility rules, or a generic TLD's specific registration restrictions) ultimately trace back to decisions the registry made, which a registrar has no authority to override even if a customer insists their particular registrar should "just make an exception." Recognizing this distinction saves considerable frustration when a request genuinely can't be granted by the party you're actually talking to, and it's worth phrasing a support inquiry accordingly — asking a registrar to clarify whether a limitation is their own policy or a registry-imposed one often gets a faster, more useful answer than repeatedly escalating a request that no amount of internal escalation at that specific company could ever fulfill.
The Takeaway
The registry is the single, authoritative record-keeper for a given TLD; the registrar is the competitive retail layer that sells and manages access to that record on your behalf. Nearly everyone only ever deals with the registrar directly, but understanding the registry sitting behind it explains domain pricing floors, what happens when a registrar disappears, and why some policy questions simply can't be resolved at the registrar level no matter how the request is phrased.
Tags: domain infrastructure, domain registry, ICANN, registrar