In the context of new gTLDs (generic Top-Level Domains), a mandatory backend registry provider refers to a specialized organization that provides the core technical infrastructure and services necessary to operate a gTLD. ICANN (Internet Corporation for Assigned Names and Numbers), the governing body for domain names, requires all new gTLD applicants to utilize evaluated backend registry providers for the stable, secure, and reliable operation of their TLDs.
Here's a breakdown of what that entails:
Key Roles and Responsibilities of a Backend Registry Provider:
- Maintaining the Registry Database: This is the central database of all domain names registered under a specific gTLD. The backend provider ensures the accuracy, integrity, and availability of this data.
- Operating DNS (Domain Name System) Servers: They run the critical infrastructure that translates human-readable domain names (like "example.com") into IP addresses that computers use to find websites. This includes ensuring high availability and resilience of DNS services.
- Implementing DNSSEC (DNS Security Extensions): A crucial security measure that adds a layer of trust to the DNS by cryptographically signing data, protecting against certain types of attacks like DNS spoofing.
- Providing EPP (Extensible Provisioning Protocol) Services: EPP is the standard communication protocol between registries and registrars, enabling registrars to register, manage, and transfer domain names in the gTLD.
- Offering RDAP (Registration Data Access Protocol) Services: RDAP replaces the older WHOIS protocol, providing a standardized way to access registration data for domain names.
- Data Escrow: Backend providers are responsible for securely depositing a copy of the gTLD's registration data with a third-party escrow agent, ensuring data continuity in case of a registry operator's failure.
- ICANN Compliance: They play a significant role in ensuring the gTLD's ongoing compliance with ICANN's numerous technical, operational, and policy requirements, including reporting and abuse management.
- Emergency Back-end Registry Operator (EBERO) Program Support: ICANN has established the EBERO program to mitigate risks in case a gTLD operator fails. Backend providers contribute to this continuity framework.
- Abuse Management Support: Assisting the registry operator in handling reports of abuse, such as phishing, malware, or spam, within the gTLD.
Why is it "Mandatory"?
ICANN has established a Registry Service Provider (RSP) Evaluation Program for the New gTLD Program: Next Round. This program evaluates the technical capabilities of backend providers to ensure they meet the stringent requirements for operating a gTLD. All new gTLD applicants are required to use RSPs that have been successfully evaluated through this program. This streamlines the application process by separating the technical assessment of the backend from the gTLD application itself, and it ensures a baseline level of technical competence and security for all new gTLDs.
In essence, while a gTLD applicant owns the right to operate a specific TLD (e.g., .brand or .city), they often outsource the complex technical operations to a specialized backend registry provider. This ensures the stability, security, and smooth functioning of the gTLD for all its users.