ICANN Contractual Compliance 2017 Annual Reports
2017 Enforcement Reasons for Registrars and Registries
This report presents data about the Formal Resolution Process broken out by enforcement reason. The measurement counts the occurrence of each reason during the calendar year. The suspension, termination and cured reasons could relate to breaches from the previous year. The # of unique column represents the number of registrars or registries related to each enforcement reason. The total of this column represents the number of unique registrars or registries, not the column total, as a registrar or registry could appear in the counts for multiple enforcement reasons. To view a list of enforcement activities for registrars and registries, go to: Formal Notices (Enforcement). To view enforcement notices for registrars and registries, go to: Notices of Breach, Suspension, Termination and Non-Renewal.
Registrars
Enforcement Reasons | Breach | Suspended | Termination | Cured | # of Unique Registrars |
---|---|---|---|---|---|
2009 RAA 3.4.2-.3 - Maintain and provide records | 1 | 1 | |||
2009 RAA 3.7.8 - Take reasonable steps to investigate claimed Whois inaccuracies | 1 | 1 | |||
2009 RAA 5.3.4 - Cure any 2009 RAA breach within 15 working days | 1 | 1 | |||
2013 RAA 3.15 - Complete and provide Compliance Certificate | 2 | 1 | 2 | ||
2013 RAA 3.15 - Respond to audits | 2 | 2 | 3 | ||
2013 RAA 3.17 - Maintain and provide information required by the Registrar Information Specification | 1 | 1 | 1 | ||
2013 RAA 3.3.1 - Provide Whois Services | 1 | 1 | |||
2013 RAA 3.4.2-.3 - Maintain and provide records | 7 | 4 | 8 | ||
2013 RAA 3.6 - Escrow registration data | 7 | 3 | 8 | ||
2013 RAA 3.7.8 - Take reasonable steps to investigate claimed Whois inaccuracies | 4 | 1 | 4 | ||
2013 RAA 3.7.8 and WAPS 1, 2, 4 - Validate and verify Whois contact information | 4 | 1 | 4 | ||
2013 RAA 3.9 - Pay accreditation fees | 4 | 3 | 5 | ||
2013 RAA 5.5.3 - Terminate officer judged to have committed fraud or breach of fiduciary duty | 1 | 1 | 1 | ||
2013 RAA 5.5.4 - Cure breaches of the RAA within 21 days | 3 | 4 | 7 | ||
Transfer Policy Section 1 & 3 - Allow RNH to transfer domain name (Section 1) or provide valid reason for denial (Section 3) | 1 | 1 | 1 | ||
Transfer Policy Section 5 - Provide AuthInfo code | 1 | 1 | 1 | ||
REGISTRAR Total | 36 | 4 | 6 | 18 | 29 |
Registries
Enforcement Reasons | Breach | Suspended | Termination | Cured | # of Unique Registries |
---|---|---|---|---|---|
2017 Amendment Section 2.3 - comply with data escrow procedures within 14 calendar days | 1 | 1 | |||
Base RA Article 6 - Pay past due fees | 2 | 2 | 3 | ||
Base RA Section 1 of Specification 4 - Operate a Whois service available via port 43 | 1 | 1 | |||
Base RA Section 2.1 of Specification 4 - Provide third-party zone file access | 1 | 1 | |||
Base RA Section 3.c. of Specification 11 - Operate top-level domain in transparent manner | 1 | 1 | 1 | ||
Base RA Section 7 of Specification 13 - Provide Annual Certification of Compliance | 1 | 1 | |||
Base RA Section 7.5 - Obtain ICANN's prior written approval for a change of control | 1 | 1 | |||
REGISTRY Total | 8 | 3 | 6 |
2017 Totals
Breach | Suspended | Termination | Cured | # Registries and Registrars | |
---|---|---|---|---|---|
2017 Total | 44 | 4 | 6 | 21 | 35 |