Summary

  • In 2019, ICANN organisation negotiated and signed new ten-year .ORG and .INFO Registry Agreements with Public Interest Registry and Afilias. The contracts removed the previous maximum-price formulas and replaced them with notice, uniform-renewal-pricing and advance-renewal protections. More than 3,200 .ORG submissions and 514 .INFO submissions entered the public-comment record, but those submissions were inputs into institutional decision-making, not votes that could approve, reject or amend a bilateral contract.
  • Namecheap, an accredited registrar rather than a party to either Registry Agreement, obtained standing in an Independent Review Process by showing procedural injury linked to a concrete commercial interest and the present risk created by ten-year uncapped agreements. The panel found three categories of procedural non-compliance: inadequate openness and transparency, failure to obtain formal Board action for a policy decision, and failure to follow a compliant process directed to the global public interest. It did not hold that price caps were substantively mandatory.
  • The remedy followed the institution’s division of power. The IRP panel could declare Bylaw violations and recommend action, but it said it could not annul or reform the signed contracts or order the caps restored. The Board later conducted additional review and, in November 2024, formally maintained the uncapped terms. A California court confirmed the award but refused to convert recommendations into commands. The second IRP ended without a merits ruling, and the official agreement pages listed no cap-restoring amendment through 31 July 2026.

Four documents, one missing power

Four documents tell the case more accurately than the political shorthand that followed it.

On 3 June 2019, ICANN organisation published two staff reports. The .ORG report recorded more than 3,200 submissions. The .INFO report recorded 514. Both reports said ICANN organisation would consider the comments and make a decision in consultation with the Board. They also defended the proposed move towards the Base Registry Agreement’s pricing structure, which did not contain the historical maximum-price formulas.

Twenty-seven days later, ICANN and the incumbent operators executed the new .ORG Registry Agreement and .INFO Registry Agreement. Their section 2.10 provisions required advance notice of price increases, generally protected uniform renewal pricing and allowed registrants to renew for as many as ten years before an increase took effect. They did not set a maximum wholesale price or retain the former ten-per-cent annual ceiling.

On 23 December 2022, the panel in Namecheap v. ICANN declared that the decision to remove the caps was a policy decision for the ICANN Board, not merely an operational act that staff could complete without formal Board action. It also found that the decision process had not met ICANN’s obligations of openness, transparency and procedurally directed attention to the global public interest.

Then, on 10 November 2024, the Board adopted Resolution 2024.11.10.01. After reviewing the declaration, economic work, Namecheap’s response and the 2019 comments, it formally decided that the two agreements should remain without price-control provisions. On 31 July 2025, a California Superior Court order refused to turn the panel’s recommendations into orders requiring ICANN to approach the operators, alter its processes or seek amendments.

The documents are not contradictory. They concern different legal entities. The staff reports concern participation and institutional explanation. The contracts concern binding rights between ICANN and each registry operator. The IRP declaration concerns compliance with ICANN’s Articles and Bylaws. The later Board resolution concerns a formal policy choice. The court order concerns the limits of judicial enforcement of the award. The missing power was the ability of a commenter, registrar, review panel or confirming court to write a maximum-price clause back into a bilateral contract by its own act.

The legal entity was a legacy renewal, not a delegation contest

.ORG and .INFO were already delegated and operating top-level domains. The 2019 controversy did not involve an application score, a community objection, a contention-set auction, a new registry contract following evaluation or an IANA decision to add a new string to the root. It involved replacement agreements for incumbent legacy registries.

That distinction matters because the actor who can influence an application is not necessarily the actor who can change an executed registry agreement. The current .ORG IANA record identifies the live sponsoring organisation, while the .INFO IANA record does the same for .INFO. Those records establish the continuing technical delegation layer. They do not contain a wholesale pricing rule, decide whether ICANN complied with its Bylaws or supply a remedy to a registrar challenging contract terms.

The case must also be separated from the later proposed transfer of Public Interest Registry to Ethos Capital. The Board’s final determination on Reconsideration Request 19-2 expressly treated that transaction as outside the request. Parts of the first IRP dealing with the proposed change of control were likewise disposed of separately. The proposed sale affected the identity and incentives of the .ORG operator; it did not convert the 2019 price-cap challenge into a change-of-control proceeding.

The operative question was narrower and more institutional: who controlled the renewal drafts, who had to make the policy decision, who could sign, who could review compliance, and what instrument could change the resulting contracts after signature?

What the 2013 baseline did—and did not establish

The 2013 agreements provide the necessary baseline. They show what was removed, but they do not prove that the removed terms were legally immutable.

Under section 7.3 of the 2013 .ORG Registry Agreement, the maximum fee for a domain-name registration was US$8.25 through 31 December 2013. From 1 January 2014, the maximum could rise by no more than ten per cent over the previous year’s maximum. Public Interest Registry was required to provide at least six months’ notice before a permitted increase and generally to charge the same service fee to all accredited registrars, while making discount and marketing programmes available on equivalent terms.

The 2013 .INFO Registry Agreement used the same structure with different starting figures. The maximum was US$7.42 through 31 August 2013 and US$8.16 from 1 September 2013. Beginning in 2014, the annual maximum could not exceed 110 per cent of the prior year’s maximum. Afilias likewise owed six months’ notice and uniform treatment of registrars.

These provisions constrained the registry operator’s wholesale charge. They did not directly regulate the retail price that a registrar charged a registrant, but they placed a ceiling on a core input price. The notice period gave commercial actors time to react; the cap limited how far the underlying charge could move. Those are different protections. A long notice period without a ceiling can postpone surprise while leaving the ultimate price unconstrained. A ceiling without adequate notice can limit magnitude while still creating operational disruption. The 2013 contracts contained both.

Section 4.2 made the renewal question more complicated than a simple copy-forward rule. It required renewal terms to be similar to those of comparable gTLDs, but expressly excluded the price of Registry Services from that comparability exercise; it also said the excluded terms would remain unchanged. Namecheap argued that the comparability language supported caps like those in .COM and .NET, and the panel rejected that argument because price was excluded. The panel expressly noted, however, that Namecheap had not separately argued that the “shall remain unchanged” sentence itself compelled retention of the 2013 caps, and it questioned whether a non-party could rely on those contracts. The declaration therefore did not adjudicate an automatic carry-forward theory based on that sentence.

This boundary is important. The strongest adjudicated case against the 2019 process was not that ICANN had no lawful capacity to agree to uncapped contracts. It was that ICANN made a consequential policy choice without the formal Board decision and reasoned public-interest process required by its own governing instruments. A procedural defect can be serious without establishing that the prior formula survived by operation of contract.

The old clauses therefore performed two roles in the dispute. Commercially, they were the protection Namecheap and many commenters wanted to preserve. Institutionally, they marked the scale of the change. Removing a quantified ceiling from two legacy agreements was not simply a technical clean-up. It altered the allocation of pricing discretion between the registry operator and the rest of the domain-name market.

Who sat at the negotiating table

The public record describes the proposed renewals as the product of bilateral discussions. The .ORG public-comment proceeding said the proposal resulted from discussions between ICANN organisation and Public Interest Registry. The parallel .INFO proceeding identified ICANN organisation and Afilias. Each page published a clean draft, a redline and related material, and each stated plainly that the proposed section 2.10 would remove existing price caps.

That description locates the first control point. ICANN organisation and the two registry operators controlled the bilateral negotiation. They could exchange drafts, accept or reject proposed wording and decide whether they were prepared to sign. Registrars, registrants and civil-society organisations did not sit at that table as counterparties. Public comment could affect the institutional process and the negotiating position of ICANN, but it did not give a commenter authority to mark up the agreement or withhold contractual assent.

The second control point concerned internal ICANN authority. In denying reconsideration, the Board said staff had acted within delegated authority, had briefed the Board and had its support. The later IRP declaration drew a sharper line. Staff may administer contracts and implement established policy, but the panel concluded that removing the caps was itself a policy decision. Under the Bylaws provisions it applied, that decision belonged to the Board and required formal Board action.

The distinction is not merely about hierarchy. A formal Board decision creates procedural consequences: it identifies the responsible body and ordinarily produces a recorded action and published rationale capable of being tested against the record. Informal support in a workshop may indicate that directors knew what staff intended. It does not perform the same governance function as a recorded resolution adopted through the prescribed process.

The panel was particularly troubled by the absence of a usable non-privileged record explaining the internal reasoning. ICANN invoked privilege broadly, and the Board workshop on 21–23 June 2019 was not a formal decision meeting with a recorded vote and rationale. The panel did not create a comprehensive new document-retention rule, but it found the available record inadequate for an institution bound to act openly and transparently.

This produces a two-part account of the 30 June signatures. Contractually, ICANN and each operator executed an agreement. Institutionally, ICANN later defended staff’s authority to do so. The IRP did not declare the signatures physically unreal or the agreements nonexistent. It declared that the underlying policy choice had not been made through the required Board process. The contract could remain operative while the decision procedure that produced it violated ICANN’s governing rules.

Public comment created duties, not a vote

The volume of opposition made the controversy politically powerful and analytically easy to misstate. The public-comment mechanism was neither meaningless consultation nor a binding plebiscite.

The two proceedings opened on 18 March 2019 and closed on 29 April. The proposal pages said the staff reports would be available for Board consideration. The .ORG staff report counted more than 3,200 submissions; the .INFO report counted 514 posted submissions. Those figures should be described as submissions, not as a verified number of unique voters. The complete corpus was not independently deduplicated and coded for this article, and public-comment systems can contain form letters, repeated organisational positions and submissions of very different evidential weight.

The principal objections nevertheless formed a coherent institutional record. Commenters argued that legacy top-level domains were not interchangeable with hundreds of newer strings; that .ORG had a distinctive identity and a registrant base that included charities and public-interest organisations; that switching a long-used domain imposed branding, search, email, security and user-recognition costs; and that these costs could give an incumbent registry market power even if many other top-level domains existed. They questioned whether the Base Registry Agreement’s notice and advance-renewal provisions were substitutes for a maximum price.

They also asked why ICANN had not commissioned economic analysis before proposing removal.

.INFO drew related concerns. Commenters disputed the idea that formal availability of alternative strings established practical substitutability. A domain name is not only an address purchased for one year. It can become embedded in email accounts, certificates, marketing, software configurations, incoming links, user habits and organisational identity. That history can make exit possible in theory and expensive in practice. The relevant market question was therefore not simply how many top-level domains existed, but how registrants and registrars would respond to price changes once a name had accumulated reliance value.

There were also arguments supporting uncapping. Some submissions contended that ICANN should not act as a price regulator, that competition among a much larger set of top-level domains constrained registry behaviour, and that alignment with the Base Registry Agreement would promote consistency. The staff reports adopted much of this logic. They pointed to the expansion of the domain-name market, invoked market mechanisms, stressed the protections in section 2.10 and treated contractual standardisation as operationally useful.

The reports are important evidence of what ICANN organisation said and considered. They are not independent findings that the market was competitive or that every material objection had been answered. Their institutional author was the organisation proposing to proceed with the renewals. A staff summary can demonstrate that concerns were received and categorised while still failing to show why a decision-maker accepted one view over another.

That was the accountability problem identified by the IRP. The Bylaws did not require ICANN to follow the numerical majority. A public-comment process would become unworkable if every high-volume campaign automatically controlled a contract. Institutions must be able to distinguish evidence, legal relevance, expertise, duplication and consequences. But the absence of majority rule does not release the decision-maker from reason-giving. The process had to be open and transparent, show meaningful consideration of material concerns and connect the outcome to ICANN’s commitments and core values.

The panel found the explanation inadequate in several respects. ICANN did not sufficiently explain why the price caps were no longer necessary for these legacy registries. It did not adequately address the possible differentiation of .ORG, the economic significance of switching costs, the possibility of market power, or the limits of notice and advance renewal as safeguards. Nor did the record show a sufficiently directed process for determining what the global public interest required.

The defect was therefore qualitative, not arithmetical. The problem was not that 3,200 was a magic number that required rejection. It was that the institution changed a consequential legacy-registry term without a formal Board decision and without a public rationale that engaged the strongest material concerns. Had there been fifty well-supported submissions rather than thousands, the duty to confront the relevant evidence would still have existed. Had there been ten thousand form submissions saying only “do not proceed”, the number alone would still not have supplied a contractual veto.

This distinction protects both participation and decision-making. Treating public comment as a vote would exaggerate community control. Treating it as a ceremonial inbox would empty transparency of content. The Bylaw duty lay between those positions: receive the record, identify the material issues, place them before the competent decision-maker and explain the institutional choice.

The new contracts protected notice, not a maximum price

The executed agreements reveal why a procedural declaration could not itself restore the old terms. They are operational instruments with identified parties, defined pricing rules and amendment machinery.

Section 2.10 of the 2019 .ORG agreement and the equivalent provision in the 2019 .INFO agreement retained several protections. For initial registrations, a registry operator generally had to give registrars thirty days’ notice of a price increase. For renewals, the general notice period was 180 days, subject to limited exceptions. Before a renewal increase took effect, registrars could obtain renewals at the existing price for periods of one to ten years. Renewal pricing also had to be uniform, subject to defined exceptions involving disclosed registrant agreements and qualified marketing programmes.

These rules address surprise and discrimination. They do not answer the maximum-price question. A registrar may have time to notify customers and a registrant may be able to prepay, yet the price after the protected period can still be higher than the former ceiling would have allowed. Advance renewal shifts part of the risk to the registrant, who must have cash, confidence and an appetite for a long commitment. It gives an established registrant a hedge; it does not impose a ceiling on the operator.

The agreements had ten-year initial terms and presumptive renewal provisions. They also identified only ICANN and the respective registry operator as parties. Section 7.8 disclaimed third-party beneficiaries, expressly including registrars and registered-name holders. Namecheap’s accreditation and commercial exposure therefore did not make it a beneficiary with a contractual right to enforce or rewrite section 2.10.

The amendment clauses locate the decisive post-signature power. Section 7.6(i) provides, subject to the agreement’s specified mechanisms, that an amendment is not binding unless it is in writing and executed by both parties. It also preserves bilateral amendments negotiated solely between ICANN and the operator. The ordinary Special Amendment route is constrained because an amendment specifying registrar prices is treated as a Restricted Amendment except to the extent the subject is addressed in section 2.10.

The safest description is not that price provisions can never be amended collectively, but that a tailored written bilateral amendment is the clearest direct route to restoring a maximum-price term.

That route required two assents. The Board could decide that ICANN should seek caps and authorise a negotiating position. ICANN organisation could conduct the negotiation. But Public Interest Registry, and the applicable successor counterparty for .INFO, would ordinarily have to execute the amendment. A Board resolution expressing a preference would not, without more, place new text in the agreement. Nor could a registrar’s successful accountability claim substitute for the operator’s contractual assent.

Reconsideration tested process, but did not transfer control

Namecheap filed Reconsideration Request 19-2 on 12 July 2019. The reconsideration docket records the Ombudsman stage, the proposed determination, Namecheap’s rebuttal and the Board’s final action on 21 November.

Reconsideration is not an appeal with unlimited authority to substitute a preferred policy. The applicable test required Namecheap to identify Board or staff action contrary to ICANN’s Mission, Commitments, Core Values or established policies, or action taken without material information or through materially false or inaccurate information. Namecheap argued that staff lacked authority to remove the caps without Board action, that the public comments had not been meaningfully considered and that the public record did not contain an adequate explanation.

It described commercial uncertainty and the risk of future wholesale increases, and it sought reversal of the uncapped terms.

The Board’s final determination denied the request. It characterised the challenged act as staff execution within delegated authority. It said the comments had been reviewed, that the Board had been briefed and supported proceeding, and that public comment did not require ICANN to follow the numerical majority. It also treated Namecheap’s harm as insufficiently present because no excessive increase had yet occurred.

Some of that reasoning would later fail before the IRP panel. The panel accepted standing based on procedural injury and present commercial risk, and it rejected the idea that informal Board involvement was an adequate substitute for formal Board action on the policy choice. But the reconsideration denial still demonstrates the route’s institutional limits. The Board was reviewing an alleged failure within ICANN’s own accountability framework. It was not adjudicating a contract claim brought by a beneficiary, because Namecheap was not one. And the request did not place the later PIR–Ethos transaction within its scope.

Reconsideration therefore gave Namecheap access to a reasoned institutional response and created a record for further review. It did not give the registrar the ability to withhold ICANN’s signature, compel an operator’s signature or amend the executed contracts directly.

Standing opened review, not contractual control

The first IRP produced Namecheap’s most important victory. It is also the point at which standing, merits and relief must be separated.

Under the Bylaws test applied in the Final Declaration, a claimant had to be materially affected by injury or harm directly and causally connected to the challenged action or inaction. ICANN argued that Namecheap had not shown a qualifying price increase and was neither a party nor a third-party beneficiary to the Registry Agreements. The panel nevertheless found standing.

The injury was not purely ideological. Namecheap was an accredited registrar purchasing registry services and serving customers whose renewal decisions could be affected by wholesale prices. The new ten-year agreements removed the prior constraints and created a present risk of future increases beyond the old formula. The panel treated a procedural injury connected to that concrete commercial interest as sufficient, even though the feared increase had not yet occurred.

This was an important accountability holding. A claimant need not wait until the final economic consequence becomes irreversible if a procedurally defective decision has already altered the legal environment in which the risk arises. But standing did not convert Namecheap into a contract party. It answered who could ask the panel to review ICANN’s compliance; it did not answer who could insert a clause into the agreements.

On the merits, Namecheap prevailed on three categories of claim set out in paragraph 486 of the declaration.

First, the panel found that approval of the uncapped agreements violated ICANN’s openness and transparency obligations. The decision record did not adequately explain the treatment of the material public comments or the basis for concluding that the legacy price controls should be removed.

Second, it found that uncapping was a policy decision for the Board. The Board had not formally approved that choice before the agreements were signed and had not followed the procedures associated with formal Board action. Knowledge, briefings or informal support could not replace the act required from the legally responsible body.

Third, the panel found that ICANN had not followed a compliant process for ensuring that its action promoted the global public interest and benefited the Internet community as a whole. The holding was procedural. It did not define a particular wholesale price as the global public interest or declare that the Bylaws required permanent caps.

The panel did not accept every theory Namecheap advanced. It rejected the claim that different treatment of .ORG and .INFO, compared with other legacy top-level domains, established a simple unlawful discrimination case. It treated .BIZ claims and several later-added theories involving historical policy and vertical integration as untimely or outside the proper scope. Claims connected to the proposed PIR change of control were handled separately and did not decide the price-cap merits.

Those limits matter because they prevent the declaration from becoming a general judgment on legacy-domain economics. The panel did not decide the optimal price for .ORG or .INFO. It did not find that every legacy registry had to be treated identically. It did not decide the PIR–Ethos transaction. It did not disturb an application evaluation or a delegation. It found that ICANN had used the wrong institutional decision path and had failed to build and disclose a sufficiently reasoned record for this policy change.

The distinction between a procedural and substantive holding is sometimes treated as an attempt to minimise a violation. It should not be. Procedure allocates power. Requiring the Board to act formally determines who must own the decision, what record must be considered and what rationale must be exposed to scrutiny. A failure at that level can undermine institutional legitimacy even when the same substantive outcome remains legally available after a compliant process.

But procedure also defines the remedy. If the panel had held that a binding legal rule required a particular cap, enforcement might have focused on compliance with that substantive command. Instead, it found that ICANN had to make the policy choice through the correct body and process. That left room for a properly acting Board to reach the same commercial result.

What Namecheap won—and what the panel said it could not give

The IRP Bylaws distinguished between declarations and recommendations. The panel could declare whether covered ICANN action or inaction violated the Articles or Bylaws and could recommend specific action. It did not treat those powers as authority to annul or reform a contract.

Namecheap sought relief capable of restoring the caps. The panel declined to order that the agreements be rescinded, rewritten or renegotiated. It reasoned that directing the contracts to be annulled would go beyond a declaration and amount to an order of specific action outside its authority. It also recognised the practical legal fact that ICANN had signed ten-year bilateral agreements. Changing them would ordinarily require negotiation with the registry operators, which were not respondents in the IRP and were not bound to accept new pricing terms merely because Namecheap prevailed against ICANN.

The panel instead recommended a sequence of institutional steps. The Board should determine how to respond to the declarations. It should conduct an open process concerning price controls and the global public interest, give particular attention to the .ORG issues, and retain an economist to examine the relevant marketplace and possible market power or explain why it chose not to do so. If the Board concluded that caps served the global public interest, ICANN should seek appropriate amendments. The panel also suggested that ICANN could approach the operators voluntarily and should consider clearer decision-making guidance.

The conditional language is the remedy boundary. The Board first had to decide the policy question through a compliant process. A conclusion in favour of caps would then support an ICANN effort to negotiate amendments. The recommendation did not predetermine that conclusion, compel the operators to agree or itself alter section 2.10.

Namecheap did receive concrete ordered relief on costs. ICANN had to bear the IRP administrative and panel costs and reimburse Namecheap US$58,750 that the registrar had paid. Each party remained responsible for its own legal and expert fees. That award was enforceable because it was part of the express disposition, not an aspirational next step.

The result was therefore a real but bounded victory. Namecheap established standing, obtained three declarations of non-compliance, defeated ICANN’s attempt to characterise the matter as routine staff implementation and recovered a defined sum. It did not obtain the commercial clause it wanted. The difference was not an accidental gap in drafting; it followed from the panel’s understanding of its jurisdiction and from the contractual rights of operators that were not parties to the IRP.

Implementation changed the decision-maker, not the contract text

The Board’s response unfolded in stages. On 21 January 2023, the Board adopted resolutions acknowledging the declaration, authorised the US$58,750 reimbursement and referred the non-binding recommendations for further evaluation. On 11 June 2023, it directed ICANN organisation to retain an economist to assess the .INFO and .ORG marketplace and the market-power questions raised by the panel.

The commissioned economic analysis dated 14 February and published on 5 March 2024, prepared by Gregory K. Leonard of Charles River Associates, concluded that .ORG and .INFO did not possess substantial and durable market power. It relied on registration and pricing data through June 2023, comparisons with other top-level domains, observed behaviour after uncapping, the availability of advance renewal and the incentives associated with Public Interest Registry’s non-profit status. It noted that .ORG had not raised its wholesale price and that .INFO’s price had not exceeded the level the old formula would have permitted over the relevant period.

That report was an expert input commissioned by the institution responding to the declaration. It was not a new adjudicative holding and did not replace the panel’s procedural findings. A period without a price increase can be evidence about operator conduct; it does not by itself prove that no market power exists over the life of a ten-year agreement. Likewise, registration trends and comparisons can inform a market assessment while leaving contested questions about semantic identity, switching costs and long-term reliance.

Namecheap’s 15 April 2024 response attacked the report’s methodology, transparency and treatment of substitution and switching. It argued that the analysis did not adequately address the distinct value of established legacy names or the limits of the ten-year renewal option. A 31 August 2024 supplemental report defended the use of post-uncapping experience, benchmark comparisons and qualitative substitution evidence, and maintained the conclusion that the registries lacked substantial and durable market power.

The Board was entitled to weigh those competing inputs. The accountability question was whether it did so through the competent body and gave a reasoned account, not whether an economist’s conclusion became legally incontestable. In its 10 November 2024 resolution and rationale, the Board said it had considered the Final Declaration, the recommendations, the commissioned report, Namecheap’s response, the supplemental report, the 2019 comments and the work of its accountability committee. It then formally determined that the 2019 .INFO and .ORG agreements would be maintained without price-control provisions.

This was the formal policy decision the panel found missing before signature. It did not erase the historical violation or convert the 2019 process into a compliant one retroactively. It changed the prospective institutional position: the body responsible for the policy choice had now taken that choice on the record after additional analysis. The commercial text remained the same because the Board chose not to pursue restoration.

The resolution also directed the interim President and CEO, or a designee, to consider whether additional clarity in ICANN’s decision-making and public-comment processes would be useful. No public implementation artefact specifically answering that direction was located on ICANN’s official site in a review through 31 July 2026. That is a bounded observation, not proof that no internal work occurred. It illustrates the continuing difference between a direction to consider process improvement and an adopted, published procedure that changes institutional practice.

The Board’s route reveals the counterfactual embedded in the IRP. If the Board had formally made the uncapping decision before 30 June 2019, on a disclosed record that directly addressed the strongest comments, the panel’s central findings would have been substantially weaker even if the contracts contained exactly the same section 2.10. The procedural breach arose from who decided, how the record was handled and what reasons were given—not from a rule that the Board could only choose caps.

Court confirmation did not expand the award

Namecheap sought judicial confirmation in Los Angeles County Superior Court, Case No. 24SMCP00066. The official litigation docket collects the petition, judgment and later enforcement motion.

In a judgment entered on 18 February 2025, the court confirmed the 23 December 2022 IRP award as a judgment. It denied Namecheap’s further requested relief without prejudice and awarded US$1,563.58 in court costs. Confirmation gave the express award judicial status. It did not change the content of the award.

Namecheap then asked the court to enforce the judgment by requiring ICANN to take steps associated with the panel’s recommendations, including approaching the operators, changing decision processes and seeking amendments if the Board found caps to be in the global public interest. The 31 July 2025 order denied the motion. The court held that it could enforce the award as confirmed but could not enlarge recommendations into binding commands or add obligations the panel had not ordered.

By then, the Board had considered the recommendations and had formally maintained the uncapped agreements. The court would not use confirmation doctrine to substitute a different policy choice or manufacture a contractual remedy. Judicial enforcement followed the same boundary as the IRP: an express declaration or monetary award could be confirmed; a recommendation could not be transformed into an order merely because the claimant preferred a more concrete result.

The second IRP closed without a merits decision

Namecheap initiated a second .INFO/.ORG IRP on 13 September 2024, before the Board’s November resolution. It amended the claim in January 2025. The official second IRP docket records the pleadings and later closure.

On 26 November 2025, Namecheap sent a termination letter voluntarily ending the proceeding without prejudice. The parties were to bear their own costs, and the provider closed the file on 15 December 2025. The closure was not a merits declaration, a settlement finding or an order restoring caps. It left the Board’s 2024 policy determination and the 2019 contract text in place.

The sequence prevents a common but serious overstatement. There was one successful merits declaration concerning the 2019 process. There was not a second decision invalidating the Board’s 2024 response. Voluntary termination preserved whatever arguments might be available in a future proceeding, but it supplied no additional remedy.

The published record through 31 July 2026

Current contract pages provide the narrowest reliable operational test. ICANN’s .ORG agreement page identifies Public Interest Registry and the 30 June 2019 agreement. Its published amendments section contains no instrument restoring the historical maximum-price clause. The current .INFO agreement page identifies the successor operator and publishes assignment and related history, but likewise lists no cap-restoring amendment.

The conclusion must remain bounded to that public record. The official pages publish agreement materials in several formats and designate the Word file as controlling where formats differ. Any status check must therefore include that controlling text and the full published assignment, assumption, addendum, fee-notification and amendment history, particularly for .INFO’s operator succession. The evidence supports the statement that no cap-restoring amendment was publicly listed through 31 July 2026. It does not justify a claim about every undisclosed communication or hypothetical side arrangement.

The IANA records show continuing delegation. They do not show a price-policy intervention, redelegation or technical consequence arising from Namecheap’s review proceedings. The published proceedings assigned the root-zone chain no role in calculating a wholesale cap, and a root-zone change could not have rewritten section 2.10.

Who could restore the caps?

The answer depends on the institutional stage.

Before signature, the Board could have required a different policy outcome and authorised ICANN organisation to negotiate agreements retaining price controls. Public comment could have influenced that decision, and a sufficiently reasoned record might have persuaded directors that the global public interest required some ceiling. The registry operators would still have been counterparties whose assent was needed for the final contracts.

After signature, the clearest route was a written bilateral amendment executed by ICANN and the applicable operator under section 7.6(i). The Board could decide that caps should be pursued and direct ICANN organisation to negotiate. ICANN organisation could propose the language. The operator could accept, reject or bargain over it. A completed amendment would bind because the parties with contractual authority had executed it.

A court or other competent legal authority might in principle issue an enforceable instrument reaching the contracting parties, but no such order emerged here. The IRP panel expressly declined to reform or annul the agreements. The California court confirmed that award and refused to enlarge its recommendations. Namecheap could create evidence, obtain standing, win declarations, recover specified costs and seek enforcement of express relief. It could not sign for ICANN or for a registry operator.

A future renewal could reopen pricing terms, but presumptive renewal does not automatically reinstate the 2013 formula. The 2019 agreements’ ten-year initial terms point towards 2029 as the next major contractual horizon. Any change would still require lawful institutional decision-making and an instrument that binds the relevant parties. Process reform alone would make future choices more legitimate; it would not insert a number into an existing price clause.

This power map explains why the 2022 declaration was both consequential and limited public evidence. It established that ICANN could not treat uncapping as routine contract administration under the process used. It required ICANN’s response to confront Board ownership of the policy decision and exposed weaknesses in the public record. It generated economic study, a formal resolution and judicially confirmed findings. Yet every accountability forum operated within a remedial perimeter. None possessed the combined authority to decide the policy, negotiate the contract and compel the operator’s assent.

The counterfactual confirms the boundary. Had the Board acted formally in June 2019, with an adequate record addressing market power, switching costs, legacy differentiation and the limits of section 2.10, it could still have chosen uncapped agreements. The opposition would not have acquired a veto. Had the Board, after the 2022 declaration, concluded that caps served the global public interest, ICANN could have sought amendments; Namecheap’s victory would not have guaranteed operator agreement. Only a valid amendment or another enforceable instrument binding the contract parties could change the operative result.

The lasting institutional lesson is not that public comment was powerless or that accountability review was futile. Participation generated the record on which the procedural failure was exposed. Standing allowed a non-party registrar to test ICANN’s compliance before an independent panel. The declaration prompted the competent policy body to act and created a judgment that preserved the findings. Those are meaningful forms of accountability.

But accountability is not the same as control. A forum may establish that an institution used the wrong process without possessing authority to reconstruct every legal relationship created by that process. Once ICANN and the operators signed ten-year agreements, the dispute acquired contractual inertia. The review system could identify the defect, allocate costs and recommend a cure. Restoring the caps required a different legal act from actors who controlled a different institutional entity. Through 31 July 2026, that act had not appeared in the published record.