Skip to main content
Resources

Compliance

Back to CCT Metrics Reporting page

These metrics are drawn from data compiled by ICANN's compliance department. This section will be updated quarterly, as the ICANN Contractual Compliance Annual Report is published.

1.6 Notices of Breach Issued to registry operators

The total number of notices of breach issued to registry operators by ICANN because of contract or policy compliance matters. [Updated Quarterly]

  2011 2012 2013 2014 2015 2016 Q1, 2016 Q2, 2016 Q3, 2016 Q4, 2016
Registry Breach Notices 1 0 0 0 0 0 2 0 1

Sources: ICANN Contractual Compliance Annual Report
Baseline: 2011-2013
CCT Review Category: Consumer Trust

1.7 Notices of Breach Issued to Registrars for Contract or Policy Compliance Matters

The number of notices of breach of the Registrar Accreditation Agreement that ICANN sent to Registrars. [Updated Quarterly]

  2011 2012 2013 2014 2015 Q1, 2016 Q2, 2016 Q3, 2016 Q4, 2016 2016
Notices of Breach 9 20 42 61 32 6 5 6 5 22
Suspensions 0 1 0 4 6 0 1 1 2 4
Terminations 1 3 11 7 8 0 24 0 2 4

Sources: ICANN Contractual Compliance Annual Report
Baseline: 2011-2013
CCT Review Category: Consumer Trust

1.8 Registry & Registrar General Complaints

The metrics reports on the number of general complaints, regarding both registries and registrars, published by ICANN Compliance. This includes information about registrars, WHOIS information, IP address issues, spam/viruses and website content. [Updated Quarterly]

  2012 2013 2014 2015 Q1, 2016 Q2, 2016 Q3, 2016 Q4, 2016 2016
Registrar Number of Complaints 48,711 26,188 39,869 45,926 9,806 8,912 11,621 12,817 43,156
Registry Number of Complaints N/A* N/A* 1,921 2,180 965 349 544 381 2230
Total Number of Complaints 48,711 26,188 41,790 48,106 10,771 9,252 12,166 13,198 45,386

Sources: ICANN Contractual Compliance Annual Report
Baseline: 2012-2013
CCT Review Category: Consumer Trust
*This data is not available because prior to 2014, there was no consolidated platform to collect data on Registry Complaints.

1.20 Complaints Regarding Inaccurate, Invalid, or Suspect WHOIS Records

This metric reports on the number of complaints regarding incomplete or incorrect WHOIS data published by ICANN Compliance. [Updated Quarterly]

  2012 2013 2014 2015 Q1, 2016 Q2, 2016 Q3, 2016 Q4, 2016 2016
Total WHOIS Complaints 30,751 15,283 29,857 36,354 9,806 8,912 11,621 12,817 43,156
WHOIS Unavailable Complaints 216 125 248 308 148 166 113 118 545
Inaccuracy Complaints 30,535 15,158 29,609 34,740 6,598 6,213 8,960 10,521 32,292

Sources: ICANN Contractual Compliance Annual Report
Baseline: 2012-2013
CCT Review Category: Consumer Trust

4.5 Total Number of Complaints Received by ICANN Regarding Improper Use of Domains

ICANN staff compiled a list of closure codes that may be related to confusion or misunderstanding of TLD functions. ICANN Compliance uses these codes to help classify complaints. Some examples of the closure codes included in this metric include: hijacking, website content, or spam. This metric reports on annual totals. [Updated Quarterly]

  2013* 2014 2015 Q1, 2016 Q2, 2016 Q3, 2016 Q4, 2016 2016
Total Number of Complaints N/A 765 993 213 268 251 231 963

Sources: ICANN databases
CCT Review Category: Consumer Trust

8.1 Total Number of Complaints Received by ICANN Related to Confusion or Misunderstanding of TLD Functions

ICANN staff compiled a list of closure codes that may be related to complaints that derive from confusion or misunderstanding of TLD functions. As with metric 4.5, ICANN Compliance uses these codes to classify complaints, and these closure codes have been used to determine the total number of complaints in this category. Some examples of these closure codes include: private dispute, domain a ccTLD, and complaint about a wrong website. This metric reports on annual totals. [Updated Quarterly]

  2013 2014 2015 Q1, 2016 Q2, 2016 Q3, 2016 Q4, 2016 2016
Total Number of Complaints 5 3,965 5,063 1,092 1,186 1,258 1,186 4,722

Sources: ICANN databases
CCT Review Category: Consumer Trust

8.3 Registries That Have Been the Subject of Public Interest Commitments (PICs)-related Complaints to ICANN As Reported in ICANN Compliance Reports

There have been no reported complaints related to Public Interest Commitments submitted to ICANN's compliance department and published in its Annual Report [Updated Quarterly]

Sources: ICANN Contractual Compliance Annual Report
CCT Review Category: Consumer Trust

8.4 Registries Losing a Dispute Resolution Procedure Related to PICs

This metric measures the number of registries that have lost a dispute resolution process related to their Public Interest Commitments (PICs). [Updated Quarterly]

There have been no DRPs related to PICs since the launch of the New gTLD Program.

Sources: ICANN Contractual Compliance Annual Report
CCT Review Category: Consumer Trust

Back to CCT Metrics Reporting page

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as""icann.org"" is not an IDN."