Summary
- ICANN's 2025 formal-notice totals close against its own monthly rows: breach notices add to ten, terminations to eight, and the two termination reasons add to eight again. The addition is mine; every input is ICANN's.
- The registrar complaint funnel does not close: its printed stage columns total 15,392 against 17,884 complaints received, a 2,492 residue, while the registry table sums above its received total exactly as ICANN's bundling caveat predicts.
The join that closes
Start with the part that works. ICANN's monthly obligations table for January to December 2025 prints registrar breach-notice volumes of 4, 1, none, none, 1, none, 1, none, 2, none, none and 1 (obligations report). Add those twelve cells and you get ten. The 2025 enforcement-reasons page prints ten Notices of Breach for registrars (enforcement reasons). The termination row reads 1, none, 4, none, 2, none, none, none, 1, none, none, none: eight. The reasons page prints eight Notices of Termination, and its two termination reason rows — six for failure to pay accreditation fees, two under 2013 RAA section 5.5.4 — sum to eight as well.
Registries get the same treatment with a different answer. Every month prints zero breach, suspension, termination and non-renewal notices for registry operators, and the reasons page prints no breach, suspension, termination or cured entries for registries in any reason row. A zero repeated in thirteen places is still a published figure, and it is checkable.
The funnel that does not
The complaint side is where the arithmetic stops cooperating. The 2025 registrar table prints a Total row of 17,884 complaints received, 12,933 closed before a first inquiry or notice, 2,043 first inquiry or notice, 249 second, 65 third, 84 escalated notices, 10 breach notices, no suspensions, 8 terminations and 14,830 closed (registrar complaints). Add the stage columns — 12,933 plus 2,043 plus 249 plus 65 plus 84 plus 10 plus 8 — and the sum is 15,392. The received cell says 17,884. The difference is 2,492.
Now read ICANN's own caveat. The monthly dashboard states that a single inquiry or notice may be based on one or several reporter complaints or on Compliance's own observations, that compliance actions may occur in a different month from the complaint's receipt, and that complaints closed before a first inquiry or notice can include complaints received in a prior period (January 2025 dashboard). Bundling and multi-stage passage both push a stage sum above the count of complaints. That is exactly what the registry table does: 1,373 plus 664 plus 73 plus 28 plus 21 gives 2,159 against 1,533 received (registry complaints). Read the same way, the caveat does not take the registrar sum below its received total. No page reviewed for this piece names a cause, and none is offered here.
The dashboard dictionary separates two units the annual tables place side by side: reporter cases are the complaints received by ICANN, while contracted party cases are the cases through which ICANN initiated investigations with a registrar or registry (data dictionary). One is an input, the other an output, and they are counted differently. That is why a complaint-to-notice ratio cannot be certified from these cells: numerator and denominator are not the same kind of object, and any reader who divides them inherits a denominator they chose themselves.
Two clocks on DNS Abuse
Two ICANN publications count DNS Abuse breach notices over two windows and neither reconciles the other. The corporate Annual Report covering 1 July 2024 to 30 June 2025 states that the first year of enforcing the new DNS Abuse requirements led to the mitigation of nearly 10,000 abusive domain names and the issuance of three Notices of Breach (Annual Report 2025). A blog post dated 20 October 2025 states that between 5 April 2024 and 5 August 2025 ICANN initiated 400 investigations, issued four formal Notices of Breach, mitigated nearly 20,000 malicious domain names and completed 31 remediation plans (ICANN blog). Different windows are not a contradiction. The missing bridge is the finding: a reader who wants one number for DNS Abuse breach notices is handed two, and no reviewed page says which frame to use. The September 2025 monthly report adds a third frame — to date in 2025, nine Notices of Breach and eight Notices of Termination, against 13 and none in 2024 (September 2025 report).
The report that once named the party
The one published format that joined a named contracted party to a cited contract provision and an outcome status still exists as a page and no longer exists as a report. Formal Notices (Enforcement) showed all enforcements with activity in a 13-month period, sorted by registrar or registry, with reasons grouped by status of Not cured, Cured, Suspended and Terminated (Formal Notices (Enforcement)). The instance retrieved here covers August 2019 to August 2020; it prints, for example, a registrar's 2013 RAA section 3.4.2-.3 reasons as not cured and then as suspended and terminated under section 5.5.4. ICANN's report index lists the format as retired (report list), while the 2025 enforcement-reasons page still directs readers to it. A pointer has outlived the report it points at.
The notices index does more than nothing. Entries are grouped by year and notice type, each is dated, each names the registrar and its IANA number, and annotations record escalation to termination, terminated accreditation agreements, cure-period extensions and cured breaches with dates (notices index). A single notice can carry the provision-level detail the summary report used to aggregate: the 27 August 2026 termination notice invokes 2013 RAA sections 5.5.4 and 5.5.6, takes effect 11 September 2026, recites the 21-day cure period, invokes the three-material-breaches-in-twelve-months ground and lists breach notices dated 10 June, 26 June, 16 July and 26 August 2026 — with the recipient's name redacted in the published copy (termination notice). A notice of breach is ICANN's allegation under a contract, not an adjudication of anything.
What no page prints, and who says so
What no reviewed page prints is the population behind an individual notice: how many complaints, from whom, over what period. Nor does any page reviewed here record an appeal, challenge or court proceeding following a 2025 or 2026 notice, or which enumerated ground carried a given disposition. Those are the cells that would let a stranger test one outcome rather than a total.
Two ICANN-community documents name the same design problem from the inside. The Registrar Stakeholder Group's comment of 17 October 2025 supports Compliance filtering unactionable complaints and lists limited transparency in mitigation actions and no clear escalation of sanctions for recurring non-compliance among the issues for possible policy work (RrSG comment). The ICANN84 GAC minutes record ALAC describing contractual compliance as curative — focused on remediation plans — rather than preventive, and questioning the thresholds used and their absence, while the GAC notes limits in Compliance data including double reporting, scope and quality (GAC84 minutes). Both concern DNS Abuse enforcement generally, not the fee-based de-accreditations of 2025, and neither is evidence about those cases.
Trade coverage credited to DomainIncite and republished on NamePros named four registrars terminated on 24 March 2025 — Zoo Hosting, Nerd Origins, Mixun Ltd and Mixun Network Technology — after January breach notices over unpaid accreditation fees, and reported no appeal (NamePros). The apparent originals did not open in this review.
Two statements, neither ranked
One more pair, printed by the same publisher and reconciled by neither page. The archived compliance reports page states that effective January 2019 no further Contractual Compliance Annual Reports will be published and refers readers to the corporate Annual Report, and that quarterly reports ceased after the second quarter of 2018 (archive page). The 2025 dashboard pages call themselves annual reports and carry no visible publication date. Whether the 2019 notice retired a narrative report and left the calendar-year dashboard series alone is not settled on either page.
So the record has two halves with different standing. The notices can be checked by anyone. The complaints behind them cannot: a reporter who quotes a percentage from these tables is quoting ICANN's denominator, not one they can rebuild.
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.






