Summary

  • The emergency transition of .WED was legally and operationally possible because the 2013 Registry Agreement combined measurable critical-function obligations with escrow, zone-data access, a Continued Operations Instrument and advance authority for ICANN to arrange necessary IANA changes. Those mechanisms gave ICANN and its designated provider temporary custody of the records and interfaces needed to preserve service; they did not transfer permanent ownership of the string or automatically select a successor.
  • ICANN’s 8 December 2017 announcement attributed the activation to a Registration Data Directory Services failure and named Nominet as the emergency interim operator. Yet the public record does not include the underlying monitoring calculation, the signed .WED Event Activation Order, the released escrow package or the contemporaneous Event Director record. It therefore supports the fact of emergency placement, but not a precise reconstruction of every internal step or the duration of the triggering outage.
  • Emergency custody and permanent disposition followed separate tracks. ICANN later terminated the original Registry Agreement effective 5 October 2020 after mediation, arbitration and an additional cure period concerning unpaid registry-level fees. It then determined in 2021 that a successor process was required because third-party registrations existed. As of 31 July 2026, the authoritative IANA record still describes .WED as being in caretaker operations, with ICANN’s EBERO programme as sponsoring organisation and Nominet in the technical role. That is evidence of continuing custody, not proof of a completed successor delegation.

Two IANA records, and the institutional gap between them

On 8 December 2017, IANA published a transfer report for .WED. The proposed manager was neither Nominet, which operated the registry systems, nor Atgron, the original operator. It was the “Emergency Back-End Registry Operator Program - ICANN.” IANA’s transfer report records contact verification, technical conformity and completion of the processing needed to change the public administrative and technical arrangement. It does not say that the string was sold, confiscated or permanently awarded.

The live record supplies the second half of the contrast. The current IANA .WED page states that the domain is in caretaker operations. It lists the ICANN EBERO programme as sponsoring organisation, an ICANN Event Director as administrative contact and Nominet in the technical role. It links a delegation report dated 17 January 2014 and the 8 December 2017 transfer report, gives 12 December 2013 as the registration date, and was last updated on 30 January 2025. It identifies no completed successor delegation, restored original operator or retired string.

IANA describes caretaker operations as a temporary transitional state for sustaining basic TLD functions. “Temporary” identifies the legal character of the arrangement, not a guaranteed short duration. A state may remain temporary in law while persisting for years because a separate exit decision has not been completed.

Different institutions performed different acts. ICANN’s contract supplied emergency designation authority. Under the current published architecture, the Event Director provides the operational decision check and authorises associated IANA requests. The provider operates under ICANN’s order. IANA processes the public delegation changes. Contractual compliance, mediation and arbitration address breach and termination. Section 4.5 and the Registry Transition Process address permanent succession. None substitutes for another.

Date Institutional act What it established—and what it did not
1 October 2013 ICANN and Atgron entered the .WED Registry Agreement. It supplied duties and emergency powers, but did not itself place .WED in the root.
12 December 2013–17 January 2014 The live IANA record gives 12 December 2013 as the registration date; IANA published its delegation report on 17 January 2014. Delegation followed contracting as a separate root-zone act; the report date is not the registration date.
7–8 December 2017 ICANN issued a compliance notice, Nominet began EBERO service under an activation order, ICANN announced placement and IANA recorded the emergency transfer. The public record establishes RDDS-based activation and caretaker implementation, not the undisclosed threshold calculation or permanent succession.
16 September–5 October 2020 An arbitrator found a fee-related breach, according to ICANN; termination then became effective under the termination notice. Atgron’s operating right ended; Nominet did not thereby become permanent operator.
7 April–19 May 2021 ICANN consulted on and made a final Section 4.5 successor determination. It authorised successor selection, not a completed award.
30 January 2025 IANA last updated the caretaker record; ICANN and Nominet also extended their master EBERO agreement to 30 November 2027. Caretaker operations remained the published state; the amendment did not disclose a .WED-specific successor or the current .WED activation order.

The emergency chain reached an executable condition. The disposition chain did not reach a publicly evidenced endpoint. The case can be understood only by separating application, contract, delegation, custody, termination and succession rather than treating them as one transfer.

Before the emergency: application, contract and delegation were separate legal states

A successful new-gTLD application did not itself make the applicant the operator of a live top-level domain. The application supplied representations and commitments. The Registry Agreement converted relevant commitments into a contractual relationship and imposed the conditions under which the registry could operate. IANA’s root-zone process then implemented a distinct delegation. The .WED record contains all three stages, and each carried a different form of authority.

The executed .WED Registry Agreement was the central legal object. It designated the operator for contractual purposes subject to the necessary root-zone approvals and incorporated specified application commitments. It also required performance records, data escrow, a Continued Operations Instrument and cooperation with emergency transition. The contract was not an unconditional grant of the string. It was a conditional operating arrangement whose continuation depended on compliance with service, financial and other obligations.

The January 2014 IANA delegation report documents the next institutional layer: party matching, contact confirmation, technical conformance and other processing. The live root record, however, gives 12 December 2013 as .WED’s registration date, while the report is dated 17 January 2014. The safe conclusion is not that publication of the report itself inserted .WED into the root on 17 January. It is that contracting and root-zone delegation were separate acts. A contract can exist before delegation, and termination can occur before the root-zone arrangement has been permanently reassigned or removed.

The same distinction operates in reverse during failure. ICANN could invoke contractual emergency provisions without first resolving all claims about breach or permanent entitlement. IANA could implement changes necessary for caretaker operation without deciding who should hold the registry agreement permanently. An emergency provider could operate the technical system without acquiring the original operator’s corporate assets, intellectual property or permanent position.

The architecture depends on these divisions because emergency continuity cannot wait for a final adjudication of every contractual dispute, while permanent succession should not be smuggled through a technical emergency change.

The contractual position was also more conditional than the language of “winning” a new gTLD sometimes suggests. Application evaluation opened a path to contracting; contracting imposed obligations and authorised future operation; delegation made the string visible in the root. None of those stages created an untouchable asset insulated from later performance conditions. Equally, failure at one stage did not erase the procedural protections attached to another. Atgron could lose operational custody before losing its contract, and could lose its contract before ICANN completed a permanent root-zone disposition.

That sequence is not accidental friction. It is the mechanism by which immediate continuity and later adjudication were kept separate.

This is also why the linked directory record, Emergency Back-End Registry Operator Program - ICANN, is best understood as an institutional control point rather than a conventional registry-company profile. The EBERO programme is the temporary custody mechanism through which ICANN can arrange continuity. Its appearance as the sponsoring organisation in IANA’s public record identifies the current caretaker arrangement; it is not a statement that ICANN owns .WED as property.

The threshold architecture: escalation was not the same as emergency

The emergency power did not begin with an undefined belief that a registry was unreliable. Specification 10 of the Registry Agreement defined critical functions and thresholds. DNS unavailability across all name servers, and failure of proper DNSSEC resolution, each reached the emergency threshold at four total hours during a week. The Shared Registration System/EPP and Registration Data Directory Services thresholds were twenty-four hours during a week. Data escrow had a separate trigger tied to failures defined in the escrow specification.

Specification 10 also created a lower escalation point. At ten per cent of an emergency threshold, ICANN’s emergency operations were to initiate an escalation that included notice, evidence of monitoring failures, cooperative troubleshooting and a commitment to begin rectification. The specification expressly said that escalation and investigation did not themselves imply that the monitored service had failed its performance requirements. Ten per cent was a reason to investigate and prepare, not an automatic emergency declaration.

The distinction protects continuity and procedural accuracy. Waiting for a full threshold before collecting evidence could waste time; treating every warning as an emergency could displace an operator before the contractual condition existed. The functions were also distinct. DNS, DNSSEC, SRS/EPP, RDDS and escrow support different parts of registry operation. Failure of one did not prove failure of all five.

That point controls the reading of .WED. The 7 December 2017 notice alleged unavailable port 43 and web Whois services, presentation defects, missing published materials, no DNSSEC Practice Statement and unpaid fees. The 8 December activation announcement specifically attributed EBERO placement to an RDDS failure. The record supports that function as the public activation basis, not every item in the notice as an emergency trigger.

The public record does not disclose the probe logs, weekly calculation, ten-per-cent escalation notice or exact time at which the full threshold was crossed. Activation under Section 2.13 supports the limited inference that ICANN treated the RDDS emergency condition as satisfied. It cannot supply a precise outage duration or show how the calculation was reviewed.

The currently published Common Transition Process Manual is version 3.0, dated August 2019. It describes states such as Ready, Heightened Alert, Event Declared, Transition-In, Stabilised and Transition-Out, together with present decision roles and alert examples. Its version history shows earlier manuals, but the contemporaneous 2017 text and decision record are not in the reviewed set. The current version explains the later architecture; it does not prove that every present step or interval governed the .WED activation in identical form.

Who could observe, who could advise and who could decide

Many actors could participate without holding decision power. Monitoring systems and technical staff could detect an outage. Compliance personnel could document breaches and demand cure. Escrow agents could report invalid deposits. A provider could prepare systems; registrars could supply records or report effects. None could appoint the emergency operator merely by supplying evidence.

Section 2.13 of the Registry Agreement placed designation authority with ICANN once a defined emergency threshold was reached. The operator had already agreed to cooperate, supply necessary data and permit ICANN to make necessary IANA-database changes to DNS and registration-directory records. The legal power came from the contract, not from Nominet’s technical capacity or IANA’s ability to process a change.

The current published manual identifies an operational decision check. The Event Team reports through an Event Director to the EBERO Executive Committee. The Event Director reviews and confirms whether an event is under way and whether emergency transition is required, authorises EBERO action and related IANA requests, and later declares the event ended. Advisers may investigate; under that later process, the Event Director converts preparation into authorised activity.

The .WED evidence is less complete. The source set contains neither the contemporaneous Event Director record nor the original signed Event Activation Order. The .WED-specific addendum confirms that Nominet began services on 7 December 2017 under such an order and that the event continued into the later framework. It proves existence and start date, not the order’s instructions, price or service plan.

The 2019 ICANN–Nominet agreement shows the contractual form: ICANN designates a failed TLD through an accepted order; Nominet performs only ordered services and remains under Event Director direction. IANA then implements approved public delegation changes. Compliance and arbitration deal separately with breach; Section 4.5 deals with succession. The emergency worked because these bounded powers connected, not because one actor held them all.

This also explains why the same evidence could have different legal significance in different rooms. An RDDS monitoring record could support an emergency declaration; a compliance notice could use related facts to demand cure; an arbitrator could consider only the claims and defences formally submitted; IANA could verify that an authorised technical change met its processing requirements. Participation in one stage did not enlarge an actor’s jurisdiction in another. The reliability of the chain depended on each institution acting within its own decision boundary.

What made the order executable: escrow, zone data, funding and root authority

An emergency declaration contains no registration records, nameserver data, DNSSEC material, registrar relationships, funding or root-zone authority. The Registry Agreement therefore built continuity around pre-positioned records and permissions.

Specification 2 required daily deposits with an independent escrow agent and made ICANN a third-party beneficiary. A full deposit was due each Sunday; a full or differential deposit was due on the other six days. The files were designed to contain the objects needed to reconstruct service: domains, contacts, nameservers, registrar relationships and other operational data. Release could follow specified critical-function failure, termination, insolvency and defined escrow failures. During the agreement term, release licensed relevant deposit rights to ICANN or its designee for operation, maintenance or transition; after the term, ownership rights in the deposits were assigned to ICANN. Those are rights in the data package, not ownership of the string or a permanent registry franchise.

The public record does not contain the .WED release instruction, deposit inventory or decrypted files delivered to Nominet. It proves that ICANN had release rights and Atgron had deposit duties, not which deposit was used or how complete it was.

Specification 4 supplied a second source. It required continuous bulk zone-file access for ICANN, at least daily, and continuous access for ICANN-designated Emergency Operators. The zone identifies active DNS material but is not a complete registration database. It complements escrow by showing nameserver and DNSSEC information that must remain coherent.

The current transition manual describes reconstruction as reconciliation. The provider obtains the available zone and relevant full and incremental deposits, preserves the source material, builds the SRS and records discrepancies; RDDS follows from the reconstructed system. The design recognises that the newest valid zone and escrow deposit may represent different moments. It does not prove which .WED records were used or what conflicts arose.

Registrar data formed a third evidentiary layer. The 2013 Registrar Accreditation Agreement requires registrars to maintain records and, in specified circumstances, provide active data needed to reconstitute a registry after unrecoverable failure or a change of operator. Registrars were not emergency decision-makers, but they could hold evidence needed to correct reconstruction errors.

Specification 8 supplied a time-limited funding backstop through a Continued Operations Instrument, using a standby letter of credit or cash escrow. The required amount was keyed to when termination occurred: three years of critical-function funding for a termination on or before the fifth anniversary, and one year for a termination after the fifth but on or before the sixth. The operator was to use best efforts to keep the instrument in effect for six years, while Section 2.13 allowed ICANN to retain and enforce its rights in it during an emergency. No reviewed source establishes whether ICANN drew on .WED’s instrument, in what amount or for which costs.

Finally, Section 2.13 authorised ICANN to make necessary IANA-database changes for DNS and registration-directory records during emergency transition; Section 4.5 supplied related post-termination authority. That consent prevented the failing operator from vetoing technical and contact changes once the contractual conditions were met, while IANA retained its processing role.

The executable chain was therefore distributed: monitoring evidence, ICANN’s designation, escrow, zone access, registrar records, funding, a provider order and IANA changes. Remove a major link and the declaration becomes far less capable of preserving a coherent TLD.

Nominet’s temporary mandate—and the clauses that kept it temporary

Nominet’s role was broad enough to preserve the registry and narrow enough to avoid converting operation into ownership. Under the 2019 agreement, it could be ordered to operate DNS, DNSSEC, RDDS and SRS/EPP and to make fresh escrow deposits. It had reporting and transition-out duties and remained subject to the Event Director’s direction.

Its authority was derivative. It existed because ICANN issued an Event Activation Order that Nominet accepted. The provider could not activate itself, expand the event unilaterally or continue after ICANN directed cessation. Service could end through return to the original operator, transition to a successor or another provider, cancellation or termination of the order.

The agreement imposed two important limits. It did not require ordinary customer support, billing or technical assistance to registrars and registered name holders. It also expressly denied third-party-beneficiary status to those groups. ICANN could enforce the provider’s duties; a registrant was not thereby made a direct claimant under the ICANN–Nominet contract.

The agreement further denied Nominet property rights or interests in the failed TLD or its string. That clause separated operational possession of nameservers, registry data and public technical contacts from permanent entitlement.

The .WED addendum records that service began on 7 December 2017 under the 2014 EBERO agreement and that the existing activation order was carried into the 2019 framework. It strongly establishes continuity of the assignment. It cannot prove that every later clause appeared in identical form in the contract governing the event’s first days, because the 2014 agreement and signed order are not in the reviewed set.

A 30 January 2025 amendment extended the 2019 master EBERO agreement to 30 November 2027 because Nominet was still serving several failed TLDs under active orders. The amendment did not identify .WED by name or disclose its current order, scope or fee record. Read with the live IANA page and the .WED addendum, it supports continuing caretaker capacity, not permanent succession.

Transition-out was part of the mandate under the later agreement, not an optional favour to a future operator. The provider had to cooperate in moving data and services to the original operator, a successor or another emergency provider when ICANN directed. That duty is a further boundary on custody: the systems and records were held for continued operation and hand-off. A provider that could refuse to deliver them would possess a practical veto over disposition even without formal ownership. The contract denied that veto by making exit cooperation an enforceable obligation to ICANN.

December 2017: what the public record proves, and what it leaves unproved

The visible .WED emergency record begins with two documents issued within a day of each other. ICANN’s 7 December 2017 breach notice catalogued alleged contractual failures and required cure by 6 January 2018. It identified RDDS availability and presentation defects, missing required published materials and unpaid fees. It warned that failure to cure could lead to termination proceedings and noted that an RDDS failure could produce emergency transition.

The next day, ICANN announced that .WED had been placed in the EBERO programme. The announcement said Atgron had experienced an RDDS failure and that Nominet, as the designated emergency interim registry operator, had stepped in to restore the service. The later addendum fixes the operational start at 7 December under an Event Activation Order. IANA’s transfer report records the associated public delegation change on 8 December.

These documents establish four propositions with high confidence. The registry was subject to the emergency provisions of its agreement. ICANN publicly identified RDDS failure as the activation basis. Nominet began emergency service under an order from ICANN. IANA implemented the administrative and technical changes necessary to represent the caretaker arrangement.

They do not establish several tempting additions. The notice does not prove that every alleged breach was ultimately found. The activation announcement does not disclose the number of hours of RDDS unavailability. The IANA report does not show the contents of the Event Activation Order. The addendum does not reveal the escrow deposit used, the SRS reconstruction method or the time at which each service reached a stable state. No public transition activity report in the reviewed source set supplies those details.

The chronology also does not prove that the compliance notice caused the emergency in a simple linear sense. Compliance and EBERO were connected but distinct processes. Compliance staff documented a wider set of alleged breaches and opened a contractual cure path. The emergency process responded to a critical-function failure. The same underlying facts could inform both tracks, but the legal consequences differed. The notice did not itself appoint Nominet, and the appointment did not itself terminate Atgron’s agreement.

This distinction guards against a common institutional error: treating an official announcement as if it were the underlying decision record. The announcement is primary evidence that ICANN said it had activated the programme for RDDS failure and that Nominet had stepped in to restore service. It is not the monitoring log, the technical threshold calculation or the signed authorisation. The public can see the institutional conclusion and its operational outcome while still lacking the evidence that would permit an independent reconstruction of the internal decision.

That is transparency of result, not full accountability for process. Accountability would require enough contemporaneous material to test whether the threshold was calculated consistently, whether lower-level escalation occurred, who reviewed the evidence, which services were unavailable, what data were released and whether the provider met transition-in targets. The absence of those records does not disprove a valid emergency. It limits the claims that can be made about how validity was established.

Registrant protection was real, but direct remedy was limited

The current stabilised-state model protects registrants mainly by freezing the commercial state while preserving critical functions. Under ICANN’s Registry Transition Processes and the current manual, the provider ordinarily rejects creates, deletes, renewals and transfers; names do not expire or automatically renew. Specified registrant, contact, nameserver and DS updates remain possible, with exceptional transactions handled through controlled procedures. The reviewed record does not establish that every present rule applied in identical form from the first day of the .WED event.

The model prevents names from expiring while ordinary renewals are unavailable and limits the caretaker’s ability to reshape the registration base. It also removes ordinary market options. A registrant may be unable to renew or transfer in the normal way. The protection is continuity, not restoration of normal registry commerce.

The current correction process allows evidence from registrars and affected parties to be compared with zone and escrow records. That supplies review access, not a guaranteed correction. The source set does not identify a .WED registrant who used the process or a case-specific outcome.

Standing was also limited. The Nominet agreement expressly disclaims third-party beneficiaries, including registrars and registered name holders, and does not require ordinary end-customer support. ICANN may enforce Nominet’s obligations; a registrant may complain or supply evidence. Those are not the same as a direct contractual right to compel performance.

The registrar contract offers a separate route. Under the 2013 Registrar Accreditation Agreement, ICANN can enforce duties concerning registration records and registrar conduct. A compliance complaint asks ICANN to use that authority; it is not automatically a private judgment or damages remedy. Any direct claim would have to arise from the applicable registration agreement, external law or another source not established here.

The 2021 consultation shows the same boundary. ICANN’s preliminary determination invited comments on whether a successor was necessary. Participation allowed evidence into the record but did not transfer the Section 4.5 decision or give registrants a veto.

Registrant protection was therefore layered: continuity duties, a transaction freeze, registrar records, correction channels, compliance enforcement and public comment. The reviewed documents do not establish a direct claim against Nominet, a guaranteed correction, renewal on demand or control over permanent disposition.

This is the difference between a system designed to reduce aggregate harm and one designed to adjudicate individual entitlements. EBERO could keep the namespace coherent for all affected users without deciding every dispute over a particular name. That triage is defensible during restoration. It becomes less satisfactory as time passes, because frozen transactions and limited support may leave an individual registrant with a technically surviving name but no ordinary route to exercise the commercial incidents of registration. Duration therefore changes the practical adequacy of the remedy even when the formal protection remains the same.

Emergency placement did not terminate the Registry Agreement

The original Registry Agreement survived the December 2017 activation. That fact is central to the case because the emergency track and the enforcement track addressed different questions. EBERO asked whether critical services had to be placed in temporary custody. Contractual compliance asked whether the operator had breached the agreement and whether the contractual conditions for termination were met.

Section 4.3(a) of the Registry Agreement required a structured sequence for termination based on breach. ICANN had to provide a specific notice and a cure opportunity; termination then depended on a final arbitral or judicial determination and a further opportunity to cure. The agreement separately supplied mediation and binding ICC arbitration procedures, and ICANN’s later notice records that the .WED parties used both. The process prevented an emergency service intervention from functioning as an unreviewed forfeiture of the operating contract.

ICANN’s 2 October 2020 termination notice describes the path followed in .WED. It refers back to the 7 December 2017 notice, states that the parties proceeded through mediation and arbitration, and reports that an arbitrator on 16 September 2020 found Atgron in breach for non-payment of registry-level fees. ICANN then gave the additional contractual cure period. When the breach was not cured, termination became effective on 5 October 2020.

The public termination notice is authoritative evidence of what ICANN did and of the arbitrator’s fee-related finding as ICANN reported it. It is not the full award. Without that award, the article cannot state the complete issues submitted, the tribunal’s reasoning, the relief ordered or whether other allegations were accepted, rejected or left unresolved. In particular, the notice does not justify saying that the arbitrator validated the original RDDS emergency determination.

The timing is revealing. Nominet had already been operating .WED under EBERO for nearly three years when the contract was terminated. If emergency custody had automatically extinguished Atgron’s rights, the cure, mediation, arbitration and additional cure process would have been superfluous. The continued enforcement path demonstrates that ICANN treated operational custody and contractual entitlement as separate legal states.

Termination then changed one state without completing another. Section 4.6 ended the original operator’s right to operate the registry, subject to surviving duties. Section 4.5 required data cooperation and gave ICANN authority to determine whether transition to a successor was necessary. Nominet’s existing EBERO role continued under its own agreement and activation order. It did not become the permanent operator by operation of the termination notice.

The current Registry Agreement Termination Information Page reflects this distinction in its status language. It records the effective termination date, the contractual basis and implementation of the final determination. A termination-status entry confirms that the original agreement ended. It is not, by itself, evidence that a new registry agreement was signed or that IANA completed a successor delegation.

Section 4.5 opened the disposition track, but did not finish it

After termination, ICANN still had to decide the TLD’s future. Section 4.5 contemplated consultation and a public-interest determination rather than automatic transfer. It also recognised that a successor might be unnecessary where registrations were confined to the operator and affiliates. .WED did not fit that position because third-party registrations existed.

In its 7 April 2021 preliminary determination, ICANN concluded that transition to a successor was necessary to protect the public interest and opened a thirty-day comment period. The decision did not select Nominet or any other candidate.

The 19 May final determination recorded that no comments had been received and said ICANN would proceed through the Registry Transition Process and a request for proposals. No comments meant no additional submissions; it did not convert consultation into consent or complete the procurement.

ICANN’s Registry Transition Processes distinguish a proposed-successor route, an RFP route after termination and temporary EBERO service. An active emergency provider may compete under the ordinary rules, but custody supplies no entitlement. Candidates must satisfy financial, technical and operational requirements. If none qualifies, the process permits sunset rather than automatic award to the caretaker.

An ICANN blog published the same day described an intended open RFP and said a successor would initially preserve third-party registrations and work with registrars about possible renewal. Its projected timetable is evidence of intention, not an award or delegation.

Completion would require candidate qualification, registry contracting, data reconciliation, system testing, transition-out cooperation and authorised IANA changes. The current IANA record still shows caretaker operations, ICANN’s programme as sponsor and Nominet in the technical role. The termination status page confirms that Atgron’s agreement ended and that the final determination entered implementation; it does not show a successor contract.

No primary source located in this review through 31 July 2026 establishes an RFP award or cancellation, completed successor transfer, sunset decision or root removal. The supported conclusion is narrower: ICANN authorised successor selection, but the authoritative operational record does not show permanent disposition.

The records still missing from a fully reconstructable account

The sources are strong on formal authority and public milestones but incomplete on case-specific execution. Several gaps remain material.

The original .WED Event Activation Order, the 2014 provider agreement in force in December 2017 and the contemporaneous version of the manual have not been located. The later addendum proves the order’s existence and start date, not its instructions or terms. The SLA logs, exact RDDS calculation, escalation notices and contemporaneous Event Director record are also absent, preventing independent reconstruction of the threshold decision.

No reviewed transition package supplies the zone snapshot, escrow-release instruction, deposit inventory, SRS reconstruction, discrepancy report, DNSSEC transition record, restoration metrics, Continued Operations Instrument draw or emergency-cost invoices. Those records would show how authority became infrastructure and whether the rebuilt registry matched the pre-failure state.

The full ICC award and any releasable mediation record are missing. ICANN’s notice supports the reported fee finding and failed cure, but not a complete account of the tribunal’s reasoning or treatment of other allegations.

The post-2021 disposition record is likewise incomplete: no reviewed source establishes the RFP package, bids, evaluation, award, non-award, cancellation or explanation for continued custody. The IANA record proves only that no completed successor delegation is presently reflected.

Registrant-level evidence is thin. Affected names, sponsoring registrars, notices, renewal handling, correction requests, compliance complaints and registration agreements have not been assembled. Accountability dockets and courts must also be searched systematically before asserting that no reconsideration, IRP, arbitral challenge or litigation occurred.

Finally, although the 2025 amendment discloses the master agreement’s term through 30 November 2027, the current .WED-specific activation order, scope, fee record and exit instructions remain unconfirmed. Any case-specific sunset plan would need to address notice, DNS shutdown, escrow and personal-data retention, deletion and root removal.

These absences do not negate the established record. They mark its boundary: authority, activation, limited provider custody, termination and the successor determination are documented; the complete internal hand-off and the reason for the unresolved exit are not.

The difference between missing evidence and a disproved event must be maintained throughout. The absence of a public escrow-release instruction does not show that no release occurred. ICANN’s announcement that Nominet was restoring RDDS supports an inference that sufficient operational data were obtained or assembled through an authorised route, but it does not identify a deposit, its age, its contents or any discrepancies. Likewise, continued caretaker status does not prove that no procurement work occurred after 2021. It proves only that no such work culminated in a successor delegation reflected in the authoritative record.

Institutional scepticism requires both restraint and precision, not automatic suspicion.

Why both halves of the architecture were necessary

The continuity track can be tested through a simple counterfactual. Suppose ICANN had possessed a contractual right to declare an emergency but no independent escrow deposits, no zone-file repository, no registrar records, no Continued Operations Instrument and no advance authority for IANA changes. The declaration would have identified a governance conclusion without supplying an operational registry. A provider might know that it had been appointed but lack the data needed to answer RDDS queries, provision updates or publish coherent DNS. It might also lack funding or the public root-zone contacts required to act.

Legal authority without records and implementation rights would have been largely symbolic.

Now reverse the counterfactual. Suppose ICANN could seize the technical records and install a provider but faced no separate cure, mediation, arbitration, termination, Section 4.5, successor-selection or sunset process. Emergency custody could then harden into permanent control by inertia. The operator would lose its position without the contractual review path, and the caretaker could become the de facto successor without qualification or a distinct appointment. Technical continuity would come at the price of procedural confiscation.

The .WED system avoided the first failure. Nominet was able to enter emergency service and the root-zone arrangement was changed rapidly. It also preserved the formal separation required to avoid the second failure: the original agreement continued until the contractual enforcement path concluded, and permanent succession required a later public-interest determination and transition process. Yet the length of caretaker operations reveals a third risk. A formally temporary state can become durable when no publicly evidenced final disposition follows.

That is the institutional lesson. EBERO is not ownership because its authority is bounded by purpose, direction, data rights and an exit obligation. But the legitimacy of that boundary depends on more than contractual wording. It also depends on a visible transition from emergency custody to cure, succession or retirement. The public record demonstrates the first transition with reasonable clarity. As of 31 July 2026, it does not demonstrate the second.