Summary

  • ICANN's Bylaws let an Independent Review Process Panel declare that the Articles of Incorporation or the Bylaws were violated, but give it only the power to recommend a stay or specific remedial action.
  • The Board must affirm or reject compliance on the public record; the decision stays final regardless, and enforcement moves to a court only if the Board rejects it without appealing to the en banc Standing Panel.
  • The first .WEB review found a violation in May 2021 and refused to order what the claimant actually wanted.
  • The second .WEB review ended in withdrawal in July 2026, the same day Verisign announced .WEB's delegation, with no public merits declaration.
  • The Empowered Community's stronger powers require agreement among five Decisional Participants; ALAC's petition on the ATRT4 deferral ended at that threshold, before any merits answer.

A binding finding, a recommendatory repair

What ICANN's Bylaws promise a challenger is narrower than the phrase "independent review" suggests. Under Article 4, Section 4.3(o), an Independent Review Process Panel may declare whether a Covered Action violated the Articles of Incorporation or the Bylaws. Its authority over the remedy is different in kind: it may recommend that ICANN stay an action or take interim or specific remedial action (ICANN Bylaws). The finding binds. The repair is advice.

Section 4.3(x) sets out what follows. ICANN "intends, agrees, and consents to be bound" by IRP Panel decisions as final, binding arbitration. Where feasible, the Board must consider its response at the Board's next meeting and affirm or reject compliance with the decision on the public record, based on an expressed rationale. The decision remains final regardless of that Board action. A decision may be appealed to the full Standing Panel sitting en banc within sixty days of issuance. And if the Board rejects a decision without appealing to the en banc Standing Panel, the Claimant or the Empowered Community may seek enforcement in a court of competent jurisdiction (ICANN Bylaws).

That sequence creates three distinct control points. The panel decides whether a violation occurred. The Board decides what to do about it, and must say so publicly. A court decides only if the Board refuses and does not take its own appeal. Only the first of the three is automatic.

What the .WEB record shows

The first .WEB review is the clearest example of a declaration without a self-executing outcome. In the proceeding brought by Afilias Domains No. 3 Limited, now Altanovo Domains Limited, under ICDR Case No. 01-18-0004-2702, the Panel's Final Declaration of 20 May 2021 found that ICANN had violated its Articles of Incorporation and Bylaws — and expressly denied the claimant's requests for a binding declaration that ICANN must disqualify a competing bid for .WEB and for an order directing ICANN to contract the .WEB registry agreement with the claimant (IRP Final Declaration, 20 May 2021). A violation was established. The remedy the claimant sought was not granted.

The second .WEB review ended differently. ICANN's docket page for Altanovo Domains Limited v. ICANN, ICDR Case No. 01-23-0003-2351, is titled "Withdrawn" and states that the claimant withdrew its request for independent review, carrying a 22 July 2026 date and a Procedural Order No. 11 among filings that begin with the 14 July 2023 request (ICANN IRP docket page).

That ending was not visible six weeks earlier. ICANN's Cooperative Engagement and Independent Review Processes status update of 25 June 2026 still listed .WEB under Active IRP Proceedings, recording the full panel confirmed on 29 March 2024 and a merits hearing held 17 to 21 November 2025, and recording no date of Board consideration of an IRP Panel Final Declaration for the proceeding (IRP/CEP status update, 25 June 2026).

On 22 July 2026, Verisign announced that .WEB had been delegated into the DNS root zone with Verisign as the designated registry operator, stating that the delegation followed "the successful resolution of all previous disputes related to the generic top-level domain (gTLD), the details of which are confidential", and that .WEB would be governed by ICANN's Base Registry Agreement (Verisign announcement, 22 July 2026).

The record establishes sequence, not causation. Two events falling on one date do not show that the withdrawal was part of a settlement, or on what terms. No public merits declaration followed the November 2025 hearing, so the substantive question the second proceeding raised was never answered on the record examined here.

When a challenge ends at the support threshold

The same architecture governs the collective route. The Empowered Community is composed of five Decisional Participants — the ASO, ccNSO, GNSO, ALAC and GAC — and ICANN lists nine community powers, including rejecting ICANN and IANA budgets and operating and strategic plans, rejecting standard Bylaw amendments, rejecting PTI governance actions, approving fundamental Bylaw and Articles amendments and asset sales, recalling the entire Board, appointing and removing individual Directors other than the President, and initiating community reconsideration, mediation or a Community IRP (Empowered Community).

Those powers are not individual rights. They are thresholds, and the ATRT4 episode shows what a threshold does. On 19 May 2025 the ICANN Board resolved to continue the deferral of the Fourth Accountability and Transparency Review pending a community dialogue on ICANN Reviews; the rationale records that ATRT4 had been deferred on 29 April 2024 for a limited time not to exceed twelve months, and the same meeting continued deferral of the SSR and RDS Specific Reviews and concluded the Pilot Holistic Review (Board resolutions, 19 May 2025).

The ALAC answered with a Community Reconsideration petition. On 11 July 2025 the Empowered Community Administration certified that the Community Reconsideration Initiation Process was terminated under Annex D, Section 4.3(b)(ii) of the Bylaws because no support from any other Decisional Participant was received within the Community Reconsideration Support Period that expired at 06:59 UTC on 11 July 2025 (ECA termination notice, 11 July 2025).

The petition was never decided on its merits. It ended because a second Decisional Participant did not join it. That is the mechanism working as written: the review schedule was contested, and the contest closed at a support count rather than on the substance.

Where the remedy actually lives

Put the two records side by side and a consistent picture appears. A declaration of breach is final and, in the Bylaws' own words, binding. What a challenger cannot obtain from the panel is the outcome — a disqualified bid, a signed registry agreement, a resumed review cycle. That depends on the Board's own recorded decision, on an internal appeal the Board may or may not pursue, or on a court that no one in the .WEB record has yet asked to rule. The Bylaws expressly contemplate that last route, which is also the clearest evidence that the earlier steps are not self-enforcing.

This matters beyond .WEB. Delegation of a contested top-level domain is irreversible in practice once the name resolves, and an accountability path measured in years can outlast the commercial and operational decisions it was meant to test. The observable signals that would confirm or falsify this reading are concrete: a Board resolution that affirms or rejects compliance with an IRP Panel decision, an en banc Standing Panel appeal, a court enforcement filing, or a Community Reconsideration that survives the support period and reaches a merits determination.

Until one of those appears, the honest summary is that ICANN can declare its own breach, and the remedy still needs another actor.