Sorry, you need to enable JavaScript to visit this website.

ICANN Contractual Compliance 2017 Quarterly Reports

2017 Quarter Four (October-December 2017) Registry Closed Complaints by Closure Code

This report presents the number of closed complaints for registries by closure code. When a complaint is closed, a description is selected which best describes the resolution of the complaint. The codes are categorized into three groups - Resolved, Out of Scope and ICANN Issue.

  • Resolved = the reporter's complaint has been resolved or the contracted party has reviewed the complaint, responded to ICANN and/or demonstrated compliance.
  • Out of Scope = the complaint cannot be addressed by ICANN because it is invalid or out of scope of ICANN's agreements/policies; or does not meet the minimum threshold for processing.
  • ICANN Issue = the complaint should not have been sent to contracted party due to ICANN error; or internal ICANN process needs to be completed before the Compliance process can continue.

A fourth category - Other - represents complaints previously closed which have been reopened and are currently active.

2017 Quarter Four (October-December 2017) Registry Closed Complaints Summary

Closure Code Category # of Complaints
Resolved189
Out of Scope103
ICANN Issue2
Other0
Registry Closed Complaints Total = 294

2017 Quarter Four (October-December 2017) Registry Closed Complaints Detail by Category and by Complaint Type

Resolved

The reporter's complaint has been resolved or the contracted party has reviewed the complaint, responded to ICANN and/or demonstrated compliance.

Complaint Types Closure Code Description # of Complaints
Bulk Registration Data AccessThe registry corrected its noncompliance.19
Bulk Zone File Access (ZFA)The registry corrected its noncompliance.3
Code Of ConductThe registry demonstrated compliance.2
Monthly ReportThe registry corrected its noncompliance.12
Registry Data EscrowICANN received the required registry data escrow notification.16
Registry FeesThe registry paid its ICANN fees.2
Registry OtherThe registry corrected its noncompliance.5
The registry demonstrated compliance.2
Reserved Names/Controlled InterruptionThe registry corrected its noncompliance.2
Service Level Agreement AlertsThe registry corrected its noncompliance.22
The registry demonstrated compliance.1
Uniform Rapid Suspension (URS)The registry corrected its noncompliance.2
Zone File AccessThe registry corrected its noncompliance.13
The registry demonstrated compliance.82
The request for zone file access was already approved by the registry operator at the time of processing the complaint.6
Resolved Category Total189

Out of Scope

The complaint cannot be addressed by ICANN because it is invalid or out of scope of ICANN's agreements/policies; or it does not meet the minimum threshold for processing.

Complaint Types Closure Code Description # of Complaints
Abuse Contact DataThe complaint is out of scope because it is about a requirement that is not applicable to the selected registry.50
The complaint is out of scope because it is regarding a country-code top-level domain.2
The complaint is out of scope because the complainant did not provide the requested information.1
Bulk Registration Data AccessThe complaint is out of scope because it is regarding a country-code top-level domain.1
Code Of ConductThe complaint is out of scope because it is about a requirement that is not applicable to the selected registry.1
The complaint is out of scope because it is regarding a country-code top-level domain.1
Registration Restrictions Dispute Resolution ProcedureThe complaint is out of scope because it is a duplicate of an open complaint.1
The complaint is out of scope because it is about a requirement that is not applicable to the selected registry.7
Registry OtherThe complaint is out of scope because it is a duplicate of an open complaint.5
The complaint is out of scope because it is incomplete or broad.5
The complaint is out of scope because it is regarding a country-code top-level domain.1
The complaint is out of scope because the complainant did not provide the requested information.8
Reserved Names/Controlled InterruptionThe complaint is out of scope because it is a duplicate of an open complaint.2
The complaint is out of scope because it is regarding a country-code top-level domain.1
The complaint is out of scope because the complainant did not provide the requested information.5
Service Level AgreementThe complaint is out of scope because it is about a requirement that is not applicable to the selected registry.1
The complaint is out of scope because the complainant did not provide the requested information.1
Zone File AccessThe complaint is out of scope because it is a duplicate of a closed complaint.1
The complaint is out of scope because it is a duplicate of an open complaint.9
Out of Scope Category Total103

ICANN Issue

The complaint should not have been sent to contracted party due to ICANN error; or an internal ICANN process needs to be completed before the Compliance process can continue.

Complaint Types Closure Code Description # of Complaints
Zone File AccessThe matter has been withdrawn due to an ICANN issue.2
ICANN Issue Category Total2