What is Registry? Definition and meaning
A registry is the authoritative database operator responsible for maintaining the master list of registered domain names within a specific top-level domain (TLD), setting the technical and contractual rules under which registrars may sell names in that zone.
The registry sits at the apex of the domain name system for its zone. It does not sell domains directly to end users – that function belongs to registrars, which are the accredited resellers through which registrants purchase and manage names. The registry publishes the zone file, enforces registration policies, and operates the infrastructure that resolves queries. For any domain dispute or acquisition, knowing which registry governs the zone is the first step in understanding which rules and remedies apply.
The distinction matters practically. When a brand owner files a UDRP complaint to recover a .com, ICANN contracts with the registry (Verisign for .com) to implement the eventual transfer order – not with the registrar the respondent used to register the name. Understanding that chain is essential before any domain due diligence.
What a registry is – and what it is not
A registry maintains the authoritative database for its TLD: the zone file that tells the global DNS which name server answers for each domain. It is not the organization that signed your registration contract. That contract is with a registrar – the retail layer. Confusing the two is the single most common error in domain due diligence and in instructions to counsel at the outset of a dispute.
The terms are sometimes used interchangeably in press coverage, but they describe distinct, separately accredited actors under ICANN's system. The registry operates under a Registry Agreement with ICANN. The registrar operates under a Registrar Accreditation Agreement. A single corporate group may hold both functions, but the legal relationships are separate. A registrant's rights run against the registrar, not directly against the registry – until a transfer order from a UDRP panel or a court requires the registry to act.
The nearest term readers confuse with registry is registrar. A simple test: if you can log in and change your name servers, you are dealing with a registrar. The registry is the layer you almost never interact with directly.
How does a registry fit into the domain name rules?
Registries for generic TLDs are bound by ICANN's Registry Agreement, which mandates participation in consensus policies including the UDRP. When a UDRP panel orders a transfer, the registrar – not the registry – implements the technical change. However, the registry's own policies govern whether the zone accepts a transfer at all, whether the domain is locked pending proceedings, and what eligibility conditions apply to registrations.
For ccTLDs the picture differs. A national registry authority administers the zone under a delegation from IANA, ICANN's address authority function. That authority sets its own registration and dispute policy. Nominet administers .uk; since 7 July 2026 its Domain Resolution Service is administered by the WIPO Arbitration and Mediation Center. EURid administers .eu under a distinct ADR procedure. DENIC administers .de and offers no UDRP equivalent – disputes there go to the German courts with a DENIC DISPUTE entry blocking transfer while litigation proceeds.
For new gTLDs – the hundreds of strings delegated since ICANN's first expansion round and the current round whose application window closed 12 August 2026 – each has its own registry operator under a Registry Agreement that includes the UDRP and the URS (Uniform Rapid Suspension). Brand owners monitoring for abusive registrations in these zones need to know not only the registrar but the specific registry's sunrise and claims period rules, which flow from the Trademark Clearinghouse mechanism ICANN requires of new gTLD registries.
How does a registry function in practice – three recognizable patterns?
Three situations illustrate where the registry's role becomes the deciding factor in a domain dispute or acquisition.
Pattern one: the UDRP transfer order. A complainant wins a UDRP proceeding before WIPO and receives a transfer order. The order goes to the registrar of record. The registrar places the domain in a registrar lock and, after the ten-business-day waiting period – during which the respondent may seek a court stay – implements the transfer within the registrar's own system. The registry's zone file is updated automatically through the standard EPP protocol. The brand owner never contacts the registry directly. But if the domain is in a new gTLD whose registry has suspended services or gone into escrow, the registry-level position matters enormously to whether the transfer can be completed at all.
Pattern two: registry eligibility in ccTLDs. A company acquires a business that holds a .eu domain. Before closing, due diligence must confirm that the target entity meets EURid's eligibility requirements – an EU/EEA nexus. If post-acquisition the registrant loses that eligibility, EURid may revoke the registration. The registry's rules, not the registrar's terms, govern that outcome. This is a due diligence risk that purchasing the domain or the business without checking the registry policy leaves entirely unaddressed.
Pattern three: registry data in a dispute investigation. Registration data for individual registrants is now largely redacted following data-protection rules. As of 28 January 2025, ICANN no longer requires registrars to operate a WHOIS service; RDAP is the standard. A brand owner investigating a potential cybersquatting registration typically needs an RDAP lookup at the registrar level plus a disclosure request through ICANN's Registration Data Request Service – but the registry's zone file confirms whether the domain is actually delegated, which name servers it uses, and whether a registry-level lock is in place. Both the registrar layer and the registry layer carry information that the other does not.
Why does the registry matter to brand owners and domain investors?
For brand owners, the governing registry determines which dispute procedure applies, which TLD eligibility rules must be met, and which sunrise or claims-period protections were available at launch. A trademark recorded in the Trademark Clearinghouse before a new gTLD's launch window gives the brand owner a right of first registration in the sunrise period and a claims notice if a third party later registers a matching name – both mechanisms that the registry is contractually required by ICANN to operate. Missing that window because no one tracked which registry was launching, and when, is a recoverable but expensive problem.
For domain investors, the registry's history of a domain – including prior dispute outcomes, registry-level locks, and any redemption grace period status – is part of chain-of-title due diligence that should precede any five-figure acquisition. A domain that was previously the subject of a UDRP proceeding carries that record permanently. Panels in subsequent disputes will read it. A registry-level lock placed by a prior registrar action may also affect the new owner's ability to transfer the domain to a preferred registrar after purchase.
We regularly advise buyers who discover, mid-transaction, that the domain they are about to close on has an adverse UDRP history or a registry-level restriction they were not told about. In our practice, the due diligence on a domain acquisition covers chain of title, dispute history, registrar status, registry eligibility, and any pending proceedings – not simply whether the name is technically available.
If you are about to acquire a domain and want a full check of the registry position, registrar history, and prior dispute record, contact info@cognomenlaw.com.
Related terms and common misconceptions
The term registrant describes the entity that holds the registered domain name – the end user in the chain. The term registrar describes the accredited reseller. The term registry describes the zone operator. All three are distinct legal actors under ICANN's contracts. A domain dispute always involves at least the registrant and the registrar; it implicates the registry whenever a transfer order must be implemented, a lock must be placed or lifted, or eligibility must be confirmed.
A related misconception: many brand owners believe that a registrar can simply "take back" a domain on the brand owner's instruction. Registrars cannot transfer a domain without the registrant's authorization or a formal order from a UDRP panel, a URS examiner, or a court. The registry's zone-file update follows the registrar's implementation of that order. Neither actor acts unilaterally on a rights-holder's complaint alone.
For new gTLDs specifically, the concept of the registry operator is intertwined with the concept of the string itself. Disputes over new gTLD applications – including Legal Rights Objections filed with WIPO during the application evaluation window – target the string before any registrations are made. In that context the "registry" is not yet an operating database; it is an applicant whose rights to operate the TLD are themselves in dispute. Brand owners who hold marks similar to a new gTLD string being applied for should confirm the current ICANN schedule for objection windows with counsel, as those windows are set by ICANN and do not repeat.
COGNOMEN handles domain-name disputes and transactions exclusively. We recover, defend, and transact internet domains across generic and country-code zones, before WIPO, the Forum, CAC, ADNDRC, and national procedures. We act for brand owners, domain investors, and registrants, including respondent-side defense and reverse domain name hijacking matters. To discuss a domain dispute or acquisition, contact info@cognomenlaw.com.
Related at COGNOMEN
Frequently asked questions
What is registry?
A registry is the authoritative database operator for a top-level domain zone – the entity that maintains the master list of registered domain names in that zone, sets technical and policy requirements for registrars, and operates the infrastructure that resolves DNS queries. It is not the organization from which a domain is purchased; that is a registrar. Knowing which registry governs a given TLD is the starting point for any domain dispute analysis or acquisition due diligence.
How is registry proven or established?
A registry's authority over a zone is established through its delegation from IANA and, for gTLDs, through its Registry Agreement with ICANN. In a domain dispute, the applicable registry is identified by the TLD of the domain at issue – for example, .com is administered by Verisign under ICANN contract; .uk is administered by Nominet; .eu by EURid. No proof is needed in the evidentiary sense; the registry is a matter of public record through IANA's Root Zone Database.
Why does registry matter to my domain?
The registry governing your domain determines which dispute procedure applies if a third party challenges your registration, which eligibility conditions you must maintain to keep the domain, and which sunrise or claims-period protections existed at launch. It also controls whether a UDRP transfer order can be implemented, whether a registry-level lock affects a post-dispute transfer, and – for ccTLDs – whether your jurisdiction or corporate structure meets the zone's ownership requirements. Registry-level issues are among the most common surprises in domain acquisitions and the most easily avoided with early due diligence.
Author: Cordelia Roe — UDRP complainant practice & gTLD recovery; domain transactions and brand protection. Meet the team.
Speak with Cognomen Law
For a scoped view of your domain matter, contact info@cognomenlaw.com. Discuss your matter
This publication is general information and does not constitute legal advice. For advice on your situation, contact info@cognomenlaw.com.