ICANN Contractual Compliance Performance Reports

Performance measurement provides metrics to the community on compliance enforcement activities through a monthly dashboard, as well as targeted reports related to specific enforcement areas and trends.

ICANN Contractual Compliance reports are available on:

• Enforcement of DNS Abuse Mitigation Requirements
• Enforcement of Non-Public Registration Data Disclosure Request Obligations
• Metrics and Dashboards
• Twelve-Month Trends

Currently, the reports appearing on the Contractual Compliance Monthly Dashboard contain a variety of metrics reflecting activity for each specific month. These metrics describe, for example, volume of complaints received across the several types through which ICANN Contractual Compliance enforces the obligations in ICANN policies and agreements. The Monthly Dashboard also includes complaint-specific details such as those related to the Temporary Specification for generic top-level domain (gTLD) Registration Data requirements.

A new series of summary reports is being added with more granular data on the complaints received, the obligations enforced and the process through which these obligations are being enforced. To illustrate historical trends over time, these reports are published on a twelve-month rolling basis, beginning from January 2021 to December 2021, and will be updated monthly.

Additional Data

Additional Contractual Compliance related data can be found at:

• Competition, Consumer Trust and Consumer Choice (CCT) Metrics Reporting, specifically in the Compliance category and the Right Protection Mechanisms category
• ICANN Accountability Indicators under Objective 4. Promote ICANN's role and multi-stakeholder approach, and section 4.4.
• WHOIS Accuracy Reporting System Contractual Compliance Metrics (WHOIS ARS) based on the types of validation identified in SAC058.
• The following ICANN Community Wiki links for the New gTLD Subsequent Procedures Policy Development Process, regarding the Working Group’s questions about vertical integration of ICANN contracted parties, ICANN’s Public Interest Commitments and ICANN’s processing of Controlled Interruption violations.
• The ICANN Community Wiki links subgroups' questions and ICANN Contractual Compliance's answers:
  • Input to the Compliance Subgroup focused on assessing implementation of WHOIS1 Recommendation #4;
  • Input to the Privacy Proxy Services Subgroup focused on assessing the implementation of WHOIS1 Recommendation #10
  • Input to the Data Accuracy Subgroup focused on assessing the implementation of WHOIS1 Recommendations # 5 to 9
  • Input to the Anything New Subgroup focused on assessing the effectiveness of today’s WHOIS (the now current gTLD RDS, including cumulative changes made to the then-current RDS which was assessed by the prior RT)
  • Input to the Workstream #1 – SSR1 Review focused on reviewing the implementation of the first Security, Stability and Resiliency (SSR1) Review Team's work and drafting a document outlining the effectiveness of said implementation.
  • Input to various questions/items received from the Expedited Policy Development Process (EPDP).
  • Input to the Workstream #2 – ICANN SSR responsible for reviewing the completeness and effectiveness of ICANNs internal security processes and the effectiveness of the ICANN security framework. See SSR2’s questions and answers here.