Registry

A registry is the organization responsible for managing the central database and technical infrastructure for a specific domain extension, such as .com, .it, or a new gTLD. It maintains registration information and communicates with registrars through defined protocols and procedures. Each TLD has an operator, along with a set of policies, pricing, and rules that may vary. The registry is distinct from the client’s registrar and typically does not offer the commercial interface used to purchase a domain directly. This separation ensures clear operational boundaries between the core infrastructure provider and the service layer.

Roles in Registration

The registrant selects a name and contacts a registrar or reseller. The registrar then submits requests to the registry, including registration, renewal, updates, transfers, or deletions. The registry verifies availability according to TLD rules and updates the authoritative database. The DNS for the individual domain is often hosted by a provider chosen by the owner. The root zone lists TLDs and their respective delegations, while each registry manages data under its own extension. These distinct levels are part of the delegation chain.

In the case of gTLDs, many registries operate under ICANN agreements and policies; ccTLDs are often managed by national or territorial organizations with different models. A registrar may be accredited for some TLDs but not others. That a domain is registrable through a provider does not mean that provider is the registry. For billing or account recovery matters, customers contact the registrar; for extension policy details, they can consult the official registry. This distinction ensures proper accountability and service delivery across the domain name ecosystem.

Policy and Infrastructure

The registry defines eligibility rules, reserved names, dispute procedures, and often pricing or renewal tiers. It also manages database systems, TLD DNS, and technical interfaces for registrars. The infrastructure must remain available and consistent to ensure registrations and delegations are accessible. Policy changes can affect pricing, transfers, expiration dates, or requirements; domain owners should monitor official communications for critical TLDs. These policies shape the operational environment and user experience across different domain extensions.

The registry may publish a WHOIS or RDAP zone and consultation services, but the amount of public data depends on policy and privacy considerations. Lookup service responses may be limited or obfuscated and do not always substitute contractual proof of ownership. In disputes, registries and registrars may retain data and enforce decisions according to established processes, though their roles and responsibilities differ. This separation supports legal compliance and dispute resolution within the domain system.

Selection and Continuity

Customers typically do not choose which registry manages a TLD; the extension determines the operator. They can, however, select a registrar that offers pricing, support, and tools. Before adopting an extension, stability of the operator, terms, renewals, restrictions, and support mechanisms are evaluated. Registrar migration does not change the registry, while transferring an entire portfolio may require coordination with multiple registries, each with distinct rules. This process highlights the importance of understanding domain infrastructure layers.

In summary, the registry manages a TLD and its registration database, whereas registrars and DNS providers perform different functions. The registry oversees the extension level and enforces common rules for names registered under that TLD. Understanding this distinction helps identify the correct source for policy, renewals, transfers, and technical configuration. This clarity is essential for effective domain management and legal compliance.