Emergency Back-End Registry Operator EBERO Program Explained

The stability, security, and resiliency of the Domain Name System are fundamental to the operation of the global internet. Every top-level domain relies on back-end registry operators to manage critical technical functions such as maintaining authoritative name servers, processing domain name registrations, and ensuring accurate DNS zone file publication. Any prolonged failure or operational disruption at the registry level poses serious risks, not only for individual domain registrants but for the entire internet ecosystem that depends on reliable domain name resolution. To safeguard against such catastrophic failures, ICANN established the Emergency Back-End Registry Operator program, known as EBERO, as a contingency mechanism designed to step in when a registry operator is unable or unwilling to meet its obligations.

The EBERO program was created in anticipation of the large-scale expansion of the DNS under the New gTLD Program. As ICANN prepared to delegate hundreds of new top-level domains, the community recognized that the introduction of many new and sometimes relatively small or inexperienced registry operators increased the potential for operational instability. While most registry operators are highly professional entities with robust technical infrastructures, business failures, security breaches, legal disputes, or unforeseen events could leave some TLDs without effective management. In such cases, the continued functionality of the DNS—and the interests of registrants and internet users—could be severely impacted without a backup plan in place.

ICANN’s role as steward of the DNS includes ensuring the continued availability of domain name resolution services, even under extraordinary circumstances. The EBERO program was specifically designed to address situations where a registry operator is at risk of failing to meet critical technical functions that are essential to the operation of a TLD. These critical functions include DNS resolution and publication, operation of the Shared Registration System (SRS), maintenance of accurate and up-to-date registration data via the WHOIS or Registration Data Directory Services (RDDS), processing of EPP (Extensible Provisioning Protocol) transactions, and providing data escrow to protect registrant data.

The EBERO process is triggered when ICANN determines that a registry operator has become unable or unwilling to perform one or more of these critical functions at an acceptable level of service. This determination may result from business failures such as bankruptcy, technical outages that cannot be quickly remedied, breaches of contractual obligations that threaten DNS stability, or even security incidents that compromise registry integrity. The goal of the EBERO program is not to permanently replace the original registry operator but to provide a temporary stabilization period that preserves DNS continuity while longer-term solutions are explored.

To prepare for such contingencies, ICANN has contracted with a small number of highly qualified technical providers who serve as pre-approved Emergency Back-End Registry Operators. These EBERO providers undergo a rigorous qualification process, demonstrating their technical capacity, infrastructure redundancy, security protocols, and expertise in DNS operations. The selection of multiple EBERO providers in geographically diverse locations ensures that ICANN has flexible and reliable options available in the event of a registry failure, regardless of where or how the failure occurs.

Once ICANN determines that an EBERO transition is necessary, a carefully coordinated transition process begins. ICANN works closely with the failing registry operator, the affected registrars, and the designated EBERO provider to transfer relevant registry data, including domain registration records, DNS zone files, and escrow data. The integrity and security of registrant information are paramount throughout this process, and data escrow arrangements play a critical role in ensuring that accurate registration data is preserved even if a registry’s operational systems are compromised or inaccessible.

During EBERO operations, the emergency provider takes over the critical functions necessary to keep the TLD operational. Registrants continue to have uninterrupted access to their domain names, DNS resolution services remain functional, and new registrations or updates may still be processed, depending on the specific circumstances of the transition. This ensures that businesses, government services, communication platforms, and other internet-dependent functions that rely on the affected TLD can continue without disruption. The EBERO period provides a crucial window during which ICANN can assess options for either restoring the original registry operator’s capabilities, transferring management to a new long-term operator, or implementing other appropriate resolutions based on the specific situation.

The EBERO program has been invoked only a handful of times, which underscores both its importance and the general resilience of the DNS ecosystem. When it has been activated, it has functioned as intended, providing critical stability and continuity while protecting registrants from the potentially devastating consequences of registry failure. These real-world cases also serve to validate the extensive planning, testing, and coordination that underpin the EBERO model.

Beyond its operational function, the existence of the EBERO program also serves as a strong incentive for registry operators to maintain high standards of performance, security, and contractual compliance. Knowing that ICANN has the ability to step in if obligations are not met reinforces the seriousness of the responsibilities held by each registry operator. The program contributes to the overall trust and confidence in the DNS, reassuring stakeholders that even in the event of severe failures, robust safeguards are in place to protect the stability of the internet’s naming infrastructure.

As ICANN and the global internet community continue to prepare for future rounds of TLD expansion, the EBERO program remains a key pillar of DNS governance. The growing complexity of the DNS, the emergence of new business models, and the increasing threats posed by cybersecurity risks only heighten the importance of having reliable emergency contingency mechanisms. ICANN’s continued investment in refining and strengthening the EBERO framework ensures that the DNS can withstand unexpected failures while preserving uninterrupted access to one of the internet’s most essential resources. In the broader context of TLD governance, the EBERO program exemplifies the kind of proactive, carefully engineered policy innovation required to maintain the security, stability, and resiliency of the global Domain Name System.

The stability, security, and resiliency of the Domain Name System are fundamental to the operation of the global internet. Every top-level domain relies on back-end registry operators to manage critical technical functions such as maintaining authoritative name servers, processing domain name registrations, and ensuring accurate DNS zone file publication. Any prolonged failure or operational disruption…