Summary
- Section 7.5 of the .ORG registry agreement, dated 30 June 2019, deems any direct or indirect change of control an assignment and bars it without the other party's prior written approval, "which approval will not be unreasonably withheld," with printed clocks (agreement text).
- Every consent clock runs against ICANN; the only timed consequence of its silence is deemed consent; and the operative criteria sit in a separate policy the clause cites without reproducing.
A veto, a notice floor and a response clock
Start with what the document prints. ICANN's registry agreements index lists the .ORG agreement with Public Interest Registry as dated 30 June 2019 and classified "Base, Non-Sponsored" (index entry). Section 7.5, titled "Change of Control; Assignment and Subcontracting," provides that neither party may assign its rights and obligations without the prior written approval of the other, that such approval "will not be unreasonably withheld," and that a direct or indirect "change of control" of the registry operator "shall be deemed an assignment."
That last sentence is what gives the rest its reach. The operator can change hands at the top of a corporate chain: the agreement treats it as an assignment all the same.
Then come the clocks. The operator must notify ICANN "no less than thirty (30) calendar days" before closing any transaction that may produce that change of control. ICANN may, within thirty calendar days of that notice, request information demonstrating compliance with the agreement and that the acquirer "and the ultimate parent entity" meet "the ICANN-adopted specification or policy on registry operator criteria then in effect." The operator then has fifteen calendar days to answer. Consent is also "subject to background checks" on the acquirer and its affiliates.
And if ICANN neither grants nor denies consent expressly within thirty days of the notice — or of receiving everything it asked for — "ICANN shall be deemed to have consented."
One further provision tightens the picture. Where the acquirer already operates a gTLD registry, the objection window drops to ten calendar days. And if ICANN reasonably refuses after the fact, the agreement does not unwind a closed deal: a consummated change of control "shall not be voidable by ICANN," and the named consequence is termination "pursuant to Section 4.3(g)."
The test: one adverb and a borrowed document
Return to the words that qualify the decision. "Will not be unreasonably withheld": that is the standard, and reasonableness is defined nowhere in the section. The substantive criteria — the ones that would let a third party ask whether a buyer's finances or engineering can sustain a top-level domain — are imported by reference to a separate policy on registry operator criteria, adopted by ICANN and "then in effect." The agreement does not print them. It points at them.
That policy was not obtained for this reading, and neither was Section 4.3(g), the termination route the clause names. The honest description of the control surface is therefore this: a reader holding the agreement can verify the trigger, the identity of the decision-maker, the notice floor, the information request, the clocks and the consequence of silence. A reader cannot verify the test, because the test lives in a document the agreement presupposes rather than contains.
The allocation is odd. The operator signs a contract; the criteria by which its ownership is judged are amended elsewhere, by the other party, in a different instrument with a different amendment procedure.
Whose clocks actually run
Count them and check the direction. Thirty days before closing, on the operator. Thirty days after notice for ICANN to ask for information. Fifteen days for the operator to answer. Thirty days for ICANN to decide, or consent is deemed given. Ten days for ICANN to object when the buyer already runs a registry.
Every clock that governs the decision runs against ICANN. The operator's only protection is deemed consent, and a ceiling on the other party's delay protects only if it holds. In the one transaction where this clause was used in earnest, it did not hold.
On 14 November 2019, Public Interest Registry gave ICANN thirty calendar days' notice under Section 7.5 of a planned indirect change of control: an Ethos Capital subsidiary would acquire 100 percent of PIR's shares from the Internet Society, with PIR as registry operator (notice). ICANN's board record then notes five mutually agreed extensions and a response deadline of 4 May 2020 (resolutions).
The arithmetic that follows is mine, not the document's. Thirty calendar days from 14 November 2019 land on 14 December 2019. The recorded deadline, 4 May 2020, sits 172 days from the notice and 142 days past that thirty-day mark. No document reviewed here prints either figure.
Whether the agreement as printed permitted those extensions, or whether they rested only on the parties' agreement, the papers read do not settle. What the record does establish is the practical result: the party whose silence the clause disciplines could move its own deadline five times, with the other party's assent, and the only cost of that delay was the delay itself. Deemed consent is a right the operator can waive. It is a bargaining chip, not a constraint.
What the decision record added
On 30 April 2020 the board adopted resolution 2020.04.30.01, directing ICANN's president and CEO "to withhold ICANN's consent to PIR's Change of Control Request pursuant to Section 7.5 of PIR's Registry Agreements, thereby rejecting PIR's request," and holding the refusal "reasonable in light of the balancing of all of the circumstances addressed or discussed by the Board."
The published rationale goes one step further: the action is "both reasonable and in the public interest," justified by the shift from a mission-driven nonprofit to a for-profit, a $360 million debt instrument, an untested Stewardship Council and ICANN's reliance as the ultimate backstop.
"In the public interest" is not in Section 7.5. The clause prints a reasonableness test and points to a criteria policy; it does not invite the decision-maker to weigh the character of the owner, still less to do so on the public's behalf. I am not arguing the board was wrong to think it. I am pointing at the instrument: one party to the contract applied a standard the contract does not contain, and no counterparty could have found it in advance by reading the agreement it signed.
The decision is otherwise unusually legible. The minutes record thirteen votes in favour, two against — Avri Doria and Danko Jevtović — one abstention by Sarah Deutsch and a statement of Doria's vote (minutes). The 1 May 2020 letter executed the decision formally, denying consent to all agreements listed in Annex A, which names the .org agreement dated 30 June 2019 (letter). Resolution 2020.04.30.02 left a door open: without prejudice to a renewed notice if PIR obtained court approval of the Pennsylvania conversion.
That separate gate deserves its name, because it is a reminder of how many decision-makers a registry sale actually has. PIR wrote to ICANN on 4 March 2020 that it had not yet begun the approval process before the Orphans' Court of Pennsylvania and that a Statement of Conversion would follow with the state (PIR letter). The EFF, on the day of the decision, noted that Pennsylvania courts had to approve the conversion to a for-profit and that the state attorney general was investigating (EFF). No Pennsylvania petition, order or merits ruling was obtained for this reading.
On 12 May 2020 PIR announced that the purchase agreement "has been terminated by the parties," that there would be no change of control and that it would not seek reconsideration (PIR statement). The clause never had a second application.
Where the external check stops
Three gaps bound everything above. The criteria policy cited in Section 7.5(b) was not obtained, so I cannot say whether the board's reasons fit the criteria the clause imports. Section 4.3(g) was not obtained either, so the real weight of a reasonable refusal — termination on what terms, on what notice — remains unknown here. And no judicial reading of "unreasonably withheld" was located, in this matter or any other: the adverb has never been measured against a buyer.
The record, by contrast, is clear about what happened and silent about the test. That is the finding, and it is not a scandal. It is a design. ICANN publishes its reasons, its vote and its dissent — a level of transparency many regulators do not reach — while keeping the operative standard in a document the affected party must go find, in a version that can change under a live transaction. The decision is verifiable as an exercise. The standard is not verifiable from the instrument.
Ownership of a registry operator is one of the few facts about a top-level domain in which the public has a real interest. If that decision is going to be discretionary, the discretion should be legible in the same document that grants it. Otherwise the consent right is a veto whose reasons are published afterwards, and the other side negotiates against a text it cannot read. BTW tracking this operator in its directory is the least of it; the point is that the clause puts a clock on one party's silence and leaves the other party's test somewhere else.
Print the criteria in the contract. Then a reader can verify the decision, instead of admiring the paperwork around it.
Member Briefing
Read the full trend briefing
Members read the full briefing with the source notes behind every finding.
Strategic Circle
A daily briefing in your language, built from changes we have verified.
Join for USD 20/monthCancel anytime.
Members also get the full research library, a daily briefing on the networks they follow and the private forum.






