{
  "id": "domain-name-registry",
  "title": "Domain name registry",
  "lang": "en",
  "source_lang": "en",
  "summary": "A domain name registry maintains registration records and delegation data for an Internet domain, usually a top-level domain, and operates the systems through which names are registered.",
  "category": "computer-science",
  "subcategory": "networks-security",
  "type": "concept",
  "aliases": [
    "Domain registry",
    "Domain name registry operator",
    "Registry operator"
  ],
  "generated_at": "2026-11-04",
  "model": "pro/gpt-6.1-sol",
  "url": "https://aiwiki.page/en/domain-name-registry/",
  "translations": {
    "zh-Hans": {
      "url": "https://aiwiki.page/zh/domain-name-registry/",
      "json": "https://aiwiki.page/zh/domain-name-registry.json"
    }
  },
  "sections": [
    {
      "heading": "",
      "text": "A domain name registry is the administrative and technical service that maintains the authoritative registration records for names within a defined part of the Domain Name System (DNS), usually a top-level domain such as .com, .org, or a country-code domain. The term can refer to the registration database, the service that maintains it, or the organization responsible for that service. A registry determines which names are registered under its authority and maintains the information needed to delegate those names in the DNS."
    },
    {
      "heading": "Registry, registrar, and registrant",
      "text": "Domain registration commonly involves three distinct roles:\n\nRole | Main responsibility\nRegistry | Maintains the authoritative registration database and the systems for its domain namespace.\n**[[domain-name-registrar | Registrar]]**\nRegistrant | Holds the contractual rights to use a registered domain name, subject to applicable policies and renewal requirements.\n\nFor example, a registrant seeking example.com normally deals with a registrar. The registrar checks availability and requests registration through the registry responsible for .com. If the request succeeds, the registry records the registration and the registrar becomes its sponsoring registrar.\n\nThis separation is common but not universal. Some registries offer registrations directly, and an organization may perform both registry and registrar functions. Retail resellers may also sell registrations without connecting directly to the registry.\n\nA registry is not necessarily a website host, an Internet service provider, or the operator of a registrant’s DNS servers. Registering a domain establishes rights and administrative records for a name; it does not by itself create a website or provide email service."
    },
    {
      "heading": "Position in the DNS hierarchy",
      "text": "The DNS is hierarchical. The root zone delegates top-level domains, and each top-level domain can delegate names beneath it. A registry normally administers registrations within one of these delegated namespaces.\n\nDifferent top-level domains use different registration structures:\n\n- Under many domains, registrations occur directly at the second level, as in example.org.\n- Some domains also use structured categories, such as example.co.uk.\n- Some namespaces restrict registrations to organizations meeting specified eligibility criteria.\n\nRegistry functions can also exist below the top level. An organization administering registrations beneath a particular second-level domain may operate registry-like services, although its authority derives from control of that domain rather than from a top-level delegation.\n\nFor the public DNS, the Internet Assigned Numbers Authority (IANA) functions maintain root-zone delegation information. A registry’s registration database is separate from the root zone: individual registrations such as example.com are not entered into the root."
    },
    {
      "heading": "Core functions",
      "text": "Registration database\n\nThe registry maintains a database of registered names and their administrative state. Depending on the registry model, records may include:\n\n- The domain name and its sponsoring registrar.\n- Creation, expiration, and update timestamps.\n- Registration status and transfer restrictions.\n- Delegated name servers.\n- DNS security delegation information.\n- Registrant and contact information, where collected by the registry.\n\nThe registry enforces uniqueness within its namespace. Two registrants cannot independently hold the same registered name at the same location in the public DNS hierarchy.\n\nRegistration data and DNS data are related but not identical. A domain can remain registered while being absent from the published DNS zone, for example because it has no name servers or is subject to a hold status.\n\nProvisioning interface\n\nRegistrars need systems for creating, renewing, updating, transferring, and deleting registrations. Many registries use the Extensible Provisioning Protocol (EPP), an XML-based protocol standardized through the Internet Engineering Task Force.\n\nEPP provides a common framework for managing domain-related objects, with extensions for registry-specific functions. Implementations generally use authenticated connections protected by Transport Layer Security. Other registries use proprietary interfaces or web-based registration systems.\n\nRegistry systems must handle competing requests consistently. When multiple registrars attempt to register the same available name, the system must produce a single authoritative result rather than create conflicting registrations.\n\nDNS publication\n\nA registry is responsible for ensuring that its zone’s authoritative DNS service reflects the delegations it administers, whether it operates that service itself or uses a technical provider.\n\nA typical delegation includes name-server records. It may also require glue records: address records needed to reach name servers whose names would otherwise create a circular dependency during resolution.\n\nRegistries supporting DNS Security Extensions publish cryptographic information that allows validating resolvers to authenticate DNS data. For a signed child domain, the parent zone can publish a delegation signer record linking the child’s keys into the DNS chain of trust. DNSSEC authenticates DNS responses; it does not encrypt website traffic or establish that a website’s content is trustworthy.\n\nRegistration data access\n\nRegistries may provide services through which users can retrieve registration information. Historically, WHOIS was widely used for this purpose. The Registration Data Access Protocol (RDAP) provides a standardized, structured alternative based on web protocols.\n\nThe information available through these services varies with registry policy, contractual requirements, and data protection rules. Publicly accessible registration information is not necessarily a complete copy of the registry’s internal records."
    },
    {
      "heading": "Types and organizational models",
      "text": "Generic top-level domain registries\n\nGeneric top-level domains include long-established domains such as .com and .org, as well as many later additions. Their operators generally work under registry agreements with the Internet Corporation for Assigned Names and Numbers (ICANN).\n\nPolicies differ among domains. Some accept registrations broadly, while others restrict eligibility to a community, profession, geographic connection, or designated organization.\n\nCountry-code top-level domain registries\n\nCountry-code top-level domains, such as .de, .jp, and .uk, are administered by designated managers. Operators include nonprofit organizations, companies, academic institutions, and public bodies.\n\nTheir governance, eligibility rules, registrar arrangements, and dispute procedures vary. Country-code registries do not all operate under the same contractual framework as generic top-level domain registries.\n\nRegistry operator and technical provider\n\nThe organization accountable for a namespace need not operate every technical component itself. A registry may contract a back-end provider to supply the registration platform, authoritative DNS, data access services, or operational support.\n\nThis distinction separates responsibility for the domain’s policies and obligations from the infrastructure used to deliver its services."
    },
    {
      "heading": "Registration lifecycle and policy",
      "text": "A registry implements rules governing registration, renewal, transfer, expiration, and deletion. A typical lifecycle includes initial registration, a period of active registration, renewal or expiration, and eventual deletion if the name is not retained.\n\nSome registries provide grace periods during which transactions can be reversed or expired names can be restored. Exact states, fees, and deadlines vary; there is no single lifecycle that applies to every top-level domain.\n\nTransferring a domain between registrars usually changes the sponsoring registrar without changing the registry responsible for the name. It is distinct from changing the registrant, moving a website to another hosting provider, or changing DNS servers.\n\nRegistry policy may also cover reserved names, premium pricing, eligibility checks, and internationalized domain names. Internationalized names allow labels derived from non-ASCII characters, subject to encoding and language-table rules. Character availability is therefore a policy and technical matter, not simply permission to register any Unicode string."
    },
    {
      "heading": "Reliability and security",
      "text": "Registry infrastructure is important because failures or unauthorized changes can affect many domain names simultaneously. Principal concerns include:\n\n- Service availability: provisioning, data access, and authoritative DNS services require resilient infrastructure.\n- Data integrity: unauthorized changes to delegation or registration records can redirect traffic or disrupt services.\n- Recovery: backups, tested recovery procedures, and, where required, data escrow support continuity.\n- Abuse resistance: controls address unauthorized transfers, compromised registrar credentials, and attacks on registry services.\n\nRegistry systems commonly use access controls, transaction logs, restricted administrative privileges, and redundant infrastructure. Some registries offer registry-lock services that impose additional verification before sensitive changes.\n\nAn outage of a registry’s registration interface does not necessarily make existing domains unreachable. Registration provisioning and DNS resolution are separate services, although the consequences of an incident depend on which systems are affected."
    },
    {
      "heading": "Historical development",
      "text": "Early Internet domain administration relied on relatively centralized registration arrangements. As commercial use expanded during the 1990s, registry and retail registration functions became more clearly separated. The introduction of competing registrars for major generic domains in 1999 helped establish the shared-registry model: multiple registrars submit transactions to a common registry system.\n\nSubsequent expansion of the top-level domain space increased the number and variety of registry operators. Specialized providers also emerged to operate technical platforms for multiple registries."
    },
    {
      "heading": "Governance and limits of authority",
      "text": "A registry controls registration and delegation within its assigned namespace; it does not control the entire Internet or the content hosted under every registered name.\n\nRegistry actions can nevertheless have broad effects. Removing a delegation or applying a hold can make services associated with a domain unreachable through ordinary DNS resolution. Such an action does not delete the underlying website files or other hosted data.\n\nRegistry governance therefore involves both technical administration and policy questions: eligibility, pricing, continuity, access to registration data, and the circumstances under which a name may be suspended or transferred. Disputes concerning intellectual property or unlawful activity may involve registrars, registries, courts, and designated dispute-resolution providers, with their respective roles determined by applicable rules and law."
    }
  ],
  "links": [
    "domain-name-system",
    "top-level-domain",
    "internet",
    "email",
    "database",
    "internet-engineering-task-force",
    "transport-layer-security",
    "data-privacy",
    "unicode",
    "data-backup",
    "disaster-recovery",
    "access-control",
    "intellectual-property"
  ],
  "sources": [],
  "license": "https://creativecommons.org/licenses/by/4.0/"
}