ICANN Contractual Compliance Metrics September 2022 to August 2023

Top Five Registrar and Registry Complaints by Volume

Registrar	SEP 22	OCT 22	NOV 22	DEC 22	JAN 23	FEB 23	MAR 23	APR 23	MAY 23	JUN 23	JUL 23	AUG 23	% of Total Received
Received	826	1132	738	886	920	895	1234	1216	1405	1316	939	1511
Top 5 Complaint Types*
Abuse	344	346	300	372	445	412	676	571	439	372	432	474	40%
Registrar Data Escrow	131	478	124	221	88	92	112	186	598	582	165	665	26%
Transfer	151	103	145	112	112	132	138	120	116	139	128	149	12%
Registration Data Inaccuracy	75	76	46	37	73	98	98	148	87	46	43	66	7%
Domain Renewal/Redemption	48	43	44	41	72	57	84	62	67	72	53	51	5%

* Top Five Complaint Types make up at least 88% of Received Complaints

Registry	SEP 22	OCT 22	NOV 22	DEC 22	JAN 23	FEB 23	MAR 23	APR 23	MAY 23	JUN 23	JUL 23	AUG 23	% of Total Received
Received	78	66	112	43	61	69	61	437	149	85	56	99
Top 5 Complaint Types*
Registry Data Escrow	19	32	54	10	18	36	12	411	111	43	24	51	62%
Zone File Access	41	24	45	18	29	18	13	15	18	21	17	13	21%
Abuse Contact Data	3	4	2	5	3	5	6	4	9	2	5	7	4%
Generic Registry	-	4	4	3	5	8	4	2	8	9	6	2	4%
Code of Conduct	2	1	2	3	3	-	3	3	1	6	3	5	2%

* 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).

Reserved Names: Registry requirements to exclude certain domain names from registration in generic top-level domains (Base RA Specification 5 and provisions related to names reservation for gTLDs not in the Base RA).