Summary

  • A working list of gTLDs in emergency back-end mode exists: seven entries on a registrar-facing page maintained by Nominet, with start dates from 8 December 2017 to 16 July 2024, read on 17 November 2026.
  • ICANN's reviewed documents describe the machinery and promise that a designation will be publicly announced; they do not carry the activation log. The record a reader can actually date is maintained by the party paid to run the backstop, and the page holding it is undated.

Five functions, one temporary switch

The Emergency Back-End Registry Operator programme is a New gTLD Program mechanism, temporarily activated when an operator is at risk of failing any of five critical registry functions: DNS resolution, the shared registration system, registration data directory services, registry data escrow, and maintenance of a properly signed DNSSEC zone. That list comes from ICANN's programme page, which also names the three contracted providers — CIRA, CNNIC and Nominet — and states that "the currently contracted organizations meet stringent technical requirements".

The scope is deliberately narrow. The 2013 FAQ limits EBERO services to critical registry functions and excludes extras such as web hosting and network analytics. This is not a takeover of a business. It is a temporary assumption of the plumbing a domain needs in order to keep resolving at all.

ICANN's transition-process page sets the shape of the event: the EBERO Temporary Transition Process is primarily for a new gTLD in breach when a critical function falls below an emergency threshold, and may also begin at the registry operator's own request. It lasts until the underlying problem is resolved or the gTLD moves to a different transition process. ICANN maintains at least two pre-selected operators under contract and runs a request for proposals every five years to renew or replace them.

Who decides, and how visibly

The Common Transition Process Manual, version 3.0, hands the operational sequence to a role rather than a committee: an Event Director confirms whether an EBERO event is underway, authorises the emergency transition, authorises the IANA changes, and ends the event. During Heightened Alert that role selects an EBERO and notifies its and IANA's 24x7 emergency contacts. Transition-In covers zone-file and DNSSEC preparation, root-zone and escrow actions, activation of the registration system and directory services, and subsequent escrow deposits. Transition-Out requires data transfer, reconciliation, DNSSEC rollover and root-zone updates. The manual describes what the role does; who holds it, who appoints it and what review attaches to its decisions were not established in the materials reviewed here.

The contract language is blunter than the manual. The CIRA EBERO agreement, effective 6 March 2025, states that "ICANN shall maintain the sole discretion to designate an EBERO to provide the EBERO Services for a Failed TLD." The same instrument sets conditions on that discretion: ICANN may not assign an Event Activation Order until CIRA completes the EBERO Readiness Exercise, may designate other parties or more than one EBERO for a failed TLD, and will publicly announce a designation.

Announce it will. Log it? That is a different promise, and the reviewed documents make only the first.

The logbook, and whose shelf it sits on

Nominet's registrar-facing registry page lists seven registries operating in EBERO mode: .desi, .nowruz, .pars, .shia, .tci, .wed and .xn--mgbt3dhd. Printed start dates run from 8 December 2017 to 16 July 2024, and some entries are labelled as unlaunched gTLDs. Subtract the two printed dates and the oldest entry spans nearly nine years — a span that the same page does not explain, because it shows a status and a start date rather than an event history.

That the December 2017 date is the beginning is Nominet's own account. Its 2019 reappointment release identifies the December 2017 .wed transition as its first EBERO activation, notes that it had first been appointed in 2014, and says that as of 28 August 2019 it was the only provider called upon to ensure continuity of a top-level domain — a claim explicitly time-bounded to that date.

The operational detail that matters most to a registrant sits on the same provider's EBERO page: in EBERO mode there are no new registrations, no deletions, no renewals and no transfers. Whatever else a backstop is for, that is what it means at the end of the chain. A domain inside one of those seven gTLDs cannot renew while the TLD sits in that state, and the list that tells you which TLDs are in that state is maintained by the company operating them.

Two calendars that do not line up

The FAQ describes providers as entering five-year contracts. The inspected CIRA agreement runs from 6 March 2025 to 30 November 2027, and Amendment No. 1 to Nominet's agreement, dated 30 January 2025, extends that term so it "shall now expire on November 30, 2027", while recording that Nominet had been designated for several failed TLDs with services ongoing. Two providers, one shared end date, and neither inspected instrument matches a five-year description running from award.

The chronology is also odd on its face. The FAQ is dated 2 April 2013 and simultaneously describes an open RFP issued in October 2018 and providers selected in 2019, which ICANN's 26 August 2019 announcement records as CNNIC, CIRA and Nominet, chosen with weight on experience, infrastructure and geographic diversity. Both documents are ICANN's. Neither explains the other. Report the discrepancy rather than resolve it by guesswork: that is what the record supports.

What this record can and cannot test

EBERO is a temporary continuity mechanism for specified critical functions, and the instruments reviewed here allocate designation and key transition decisions to ICANN-controlled roles. That is a description of a design. Whether the design has worked, how long any individual activation lasted, whether an event began with a breach determination or an operator's request, and what review followed: none of that was established from the documents reviewed for this piece.

So the honest limit is narrower and more interesting than a scandal. A reader who wants to know whether the backstop has been used must read a contractor's operational page, undated, which shows status rather than history. The coordinator's documents reviewed here promise a public announcement of each designation; whether each of the seven listed TLDs drew one was not tested. The difference between announcing an event and keeping a record of events is the whole gap.

That gap is not evidence of bad faith. It is evidence of where the record lives, and it should change what a registrar or a reseller asks before relying on a backstop whose logbook belongs to the firm that gets paid when the logbook grows.