ICANN Contractual Compliance Metrics January to December 2022
Top Five Registrar and Registry Complaints by Volume
| Registrar | JAN 22 | FEB 22 | MAR 22 | APR 22 | MAY 22 | JUN 22 | JUL 22 | AUG 22 | SEP 22 | OCT 22 | NOV 22 | DEC 22 | % of Total Received |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Received | 734 | 1925 | 1114 | 842 | 776 | 1399 | 854 | 2224 | 826 | 1132 | 738 | 886 | |
| Top 5 Complaint Types* | |||||||||||||
| Registrar Data Escrow | 39 | 1218 | 378 | 206 | 124 | 702 | 147 | 1397 | 131 | 478 | 124 | 221 | 38% |
| Abuse | 273 | 307 | 353 | 251 | 282 | 299 | 306 | 355 | 344 | 346 | 300 | 372 | 28% |
| Transfer | 146 | 148 | 150 | 140 | 129 | 141 | 100 | 109 | 151 | 103 | 145 | 112 | 12% |
| Registration Data Inaccuracy | 126 | 65 | 36 | 79 | 94 | 96 | 147 | 212 | 75 | 76 | 46 | 37 | 8% |
| Domain Renewal/Redemption | 50 | 61 | 58 | 64 | 53 | 59 | 52 | 54 | 48 | 43 | 44 | 41 | 5% |
* Top Five Complaint Types make up at least 88% of Received Complaints
| Registry | JAN 22 | FEB 22 | MAR 22 | APR 22 | MAY 22 | JUN 22 | JUL 22 | AUG 22 | SEP 22 | OCT 22 | NOV 22 | DEC 22 | % of Total Received |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Received | 82 | 133 | 126 | 282 | 80 | 60 | 93 | 1266 | 78 | 66 | 112 | 43 | |
| Top 5 Complaint Types* | |||||||||||||
| Registry Data Escrow | 14 | 63 | 68 | 239 | 34 | 34 | 49 | 1182 | 19 | 32 | 54 | 10 | 74% |
| Zone File Access | 50 | 59 | 36 | 35 | 31 | 14 | 31 | 67 | 41 | 24 | 45 | 18 | 19% |
| Abuse Contact Data | 6 | 4 | 4 | 3 | 4 | 2 | 3 | 6 | 3 | 4 | 2 | 5 | 2% |
| Generic Registry | 4 | 5 | 1 | 1 | 6 | 5 | 5 | 4 | 0 | 4 | 4 | 3 | 2% |
| Code of Conduct | 4 | 0 | 12 | 2 | 0 | 2 | 2 | 3 | 2 | 1 | 2 | 3 | 1% |
* Top Five Complaint Types make up at least 90% of Received Complaints
Explanations of Obligations Addressed within each Complaint Type (and source of obligation):
Transfer: Registrar requirements related to the transferring of domain names from one registrar to another, and to modifying Registrant information (Transfer Policy)
Abuse: Registrar obligations to investigate and respond to abuse reports, maintain abuse reports records and provide them to ICANN, and publish abuse contacts and description of abuse procedures on the registrar's website (Registrar Accreditation Agreement (RAA) Section 3.18))
Registration Data Inaccuracy: Registrar requirements to take reasonable steps to investigate and correct claimed Whois inaccuracies (RAA Section 3.7.8) and comply with validation/verification requirements (RAA Whois Accuracy Program Specification (“WAPS”))
Domain Renewal/Redemption: Registrar requirements related to the renewal/redemption of domain names, providing notice to registrants regarding domain name expirations, and providing domain renewal information on the registrar's website and in its registration agreement (Expired Registration Recovery Policy and Expired Domain Deletion Policy)
Registrar Data Escrow: Registrar requirement to escrow generic top-level domain (gTLD) registration data on a schedule, under the terms, and in a format specified by ICANN (RAA Section 3.6)
Registry Data Escrow: Registry requirement to comply with the registry data escrow procedures (Registry Agreement (RA) Section 2.3 and Specification 2)
Zone File Access: Registry requirement to provide third-party zone file access (RA Specification 4, Section 2.1)
Abuse Contact Data: Registry requirement to publish on its website abuse contact details, including a valid email, mailing address, and primary contact for handling inquiries related to malicious conduct in the top-level domain (TLD) (RA Specification 6, Section 4.1)
Generic Registry: Any registry requirement in the relevant RA or Consensus Policy with no dedicated complaint form. A requirement will not have a dedicated complaint form if, historically, the number of complaints received pertaining to the requirement has been very low (sometimes non-existent).
Code of Conduct: Registry requirement to abide by the Code of Conduct established in their RA which includes conducting internal reviews at least once per calendar year to ensure compliance with the Code of Conduct (Specification 9).