ICANN Contractual Compliance 2018 Quarterly Reports
2018 Quarter One (January-March 2018) Registrar Closed Complaints by Closure Code
This report presents the number of closed complaints for registrars 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.
2018 Quarter One (January-March 2018) Registrar Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 4250 |
| Out of Scope | 6427 |
| ICANN Issue | 4 |
| Other | 79 |
| Registrar Closed Complaints Total | 10760 |
2018 Quarter One (January-March 2018) Registrar 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 |
|---|---|---|
| Abuse | The domain is suspended and suspension is a reasonable response to the abuse report. | 33 |
| The registrar demonstrated compliance. | 1 | |
| The registrar published the required abuse contact information. | 3 | |
| The registrar responded to the abuse report. | 42 | |
| The registrar's abuse contact information appears in the public WHOIS. | 2 | |
| CEO Certification | The registrar submitted its annual compliance certificate. | 24 |
| The registrar's annual compliance certificate has been corrected. | 1 | |
| Data Escrow | The registrar completed its data escrow deposit. | 32 |
| The registrar's data escrow file content issue is resolved. | 7 | |
| Domain Deletion | The domain is no longer suspended. | 33 |
| The domain was not suspended at the time the complaint was processed. | 14 | |
| The registrar restored the domain. | 2 | |
| The registrar's deletion of the domain was compliant. | 1 | |
| Domain Name System Security Extensions (DNSSEC), Internationalized Domain Names (IDN), Internet Protocol Version 6 (IPv6) | The registrar now supports Domain Name System Security Extensions (DNSSEC). | 1 |
| Domain Renewal | The domain has been renewed with the same registrant. | 12 |
| The registrant indicated the registrar provided the requested assistance for domain renewal. | 3 | |
| The registrar corrected its Expired Registration Recovery Policy (ERRP) noncompliance. | 2 | |
| The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements. | 21 | |
| The registrar demonstrated compliance. | 1 | |
| Fees | The registrar paid its ICANN fees. | 6 |
| Privacy/Proxy | The registrar's privacy/proxy provider issue is resolved. | 1 |
| Registrar Contact | The registrar's contact information is displayed on its website. | 1 |
| The registrar's contact information was updated. | 1 | |
| Registrar Information Specification (RIS) | The registrar demonstrated compliance. | 1 |
| Registrar Other | The domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint. | 1 |
| The registrar corrected its noncompliance. | 2 | |
| The registrar demonstrated compliance. | 5 | |
| Reseller Agreement | The registrar demonstrated compliance. | 2 |
| Transfer | The change of registrant has been completed. | 6 |
| The registrar corrected its noncompliance. | 1 | |
| The registrar demonstrated compliance with its contractual requirements. | 71 | |
| The registrar demonstrated compliance with the change of registrant requirements. | 9 | |
| The registrar demonstrated compliance. | 5 | |
| The registrar provided evidence that the transfer AuthInfo code was provided to the registrant and the public WHOIS shows the domain is unlocked for transfer. | 27 | |
| The transfer cannot be completed due to a dispute over the identity of the registrant or administrative contact. | 2 | |
| The transfer cannot be completed due to a transfer or registration within the past 60 days, or a change of registrant lock. | 21 | |
| The transfer cannot be completed due to a transfer within the past 60 days. | 4 | |
| The transfer cannot be completed due to evidence of fraud. | 10 | |
| The transfer cannot be completed due to express objection by the transfer contact. | 1 | |
| The transfer cannot be completed due to the change of registrant lock. | 6 | |
| The transfer cannot be completed due to the domain being in redemption grace period or pending delete status. | 4 | |
| The transfer cannot be completed without proof of the transfer contact's identity. | 5 | |
| The transfer has been completed. | 151 | |
| The transfer was denied because of a court order received by the registrar. | 1 | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | The registrar demonstrated compliance with the Uniform Domain Name Dispute Resolution Policy (UDRP) requirements. | 7 |
| The registrar locked a domain subject to a Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding. | 11 | |
| The registrar verified the domain with the Uniform Domain Name Dispute Resolution Policy (UDRP) provider. | 1 | |
| WHOIS Accuracy Reporting System (WHOIS ARS) | The domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint. | 339 |
| The registrar corrected its WHOIS format. | 6 | |
| The registrar demonstrated compliance. | 2 | |
| The registrar verified the domain's WHOIS information is correct. | 13 | |
| The WHOIS data has been updated. | 34 | |
| WHOIS Format | The registrar corrected its noncompliance. | 1 |
| The registrar corrected its WHOIS format. | 35 | |
| The registrar demonstrated compliance. | 1 | |
| The registrar's WHOIS format was compliant at the time the complaint was processed. | 4 | |
| WHOIS Inaccuracy | The domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint. | 2669 |
| The registrar demonstrated compliance. | 6 | |
| The registrar demonstrated the WHOIS information was previously verified as correct or corrected. | 16 | |
| The registrar verified the domain's WHOIS information is correct. | 96 | |
| The WHOIS data has been updated. | 399 | |
| WHOIS Quality Review | The domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint. | 8 |
| WHOIS Unavailable | The registrar demonstrated compliance. | 2 |
| The registrar's WHOIS service is now compliant. | 4 | |
| The registrar's WHOIS service was compliant at the time the complaint was received. | 4 | |
| The registrar's WHOIS service was restored. | 13 | |
| Resolved Category Total | 4250 |
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 | The complaint is out of scope because customer service issues are outside of ICANN's contractual authority. | 2 |
| The complaint is out of scope because it is a duplicate of a closed complaint. | 2 | |
| The complaint is out of scope because it is a duplicate of an open complaint. | 5 | |
| The complaint is out of scope because it is about a registrar that is not within ICANN's contractual authority. | 3 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 14 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 72 | |
| The complaint is out of scope because the domain is not registered. | 1 | |
| CEO Certification | The complaint is out of scope because ICANN terminated the registrar's accreditation. | 1 |
| The complaint is out of scope because the registrar voluntarily terminated its ICANN accreditation. | 1 | |
| Customer Service | The complaint is out of scope because customer service issues are outside of ICANN's contractual authority. | 10 |
| The complaint is out of scope because ICANN does not process complaints regarding website content. | 1 | |
| The complaint is out of scope because ICANN is not a registrar. | 6 | |
| The complaint is out of scope because it contains offensive language. | 1 | |
| The complaint is out of scope because it is a duplicate of a closed complaint. | 2 | |
| The complaint is out of scope because it is a duplicate of an open complaint. | 11 | |
| The complaint is out of scope because it is about a private dispute that does not implicate ICANN's contractual authority. | 4 | |
| The complaint is out of scope because it is about a registrar that is not within ICANN's contractual authority. | 4 | |
| The complaint is out of scope because it is about an illegal activity that is outside of ICANN's contractual authority. | 1 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 5 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 65 | |
| The complaint is out of scope because the domain is not registered. | 1 | |
| Domain Deletion | The complaint is out of scope because customer service issues are outside of ICANN's contractual authority. | 8 |
| The complaint is out of scope because ICANN does not process complaints regarding website content. | 5 | |
| The complaint is out of scope because ICANN is not a registrar. | 6 | |
| The complaint is out of scope because it is a duplicate of a closed complaint. | 4 | |
| The complaint is out of scope because it is a duplicate of an open complaint. | 22 | |
| The complaint is out of scope because it is about a private dispute that does not implicate ICANN's contractual authority. | 5 | |
| The complaint is out of scope because it is about a registrar that is not within ICANN's contractual authority. | 8 | |
| The complaint is out of scope because it is about an illegal activity that is outside of ICANN's contractual authority. | 3 | |
| The complaint is out of scope because it is not about an ICANN contracted party. | 1 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 16 | |
| The complaint is out of scope because spam is outside of ICANN's contractual authority. | 2 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 109 | |
| The complaint is out of scope because the domain is not registered. | 5 | |
| The complaint is out of scope because there is no evidence of an abuse report with the registrar. | 1 | |
| Domain Name System Security Extensions (DNSSEC), Internationalized Domain Names (IDN), Internet Protocol Version 6 (IPv6) | The complaint is out of scope because customer service issues are outside of ICANN's contractual authority. | 1 |
| The complaint is out of scope because it is a duplicate of an open complaint. | 1 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 7 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 1 | |
| Domain Renewal | The complaint is out of scope because customer service issues are outside of ICANN's contractual authority. | 2 |
| The complaint is out of scope because ICANN terminated the registrar's accreditation. | 1 | |
| The complaint is out of scope because it is a duplicate of a closed complaint. | 2 | |
| The complaint is out of scope because it is a duplicate of an open complaint. | 19 | |
| The complaint is out of scope because it is about a private dispute that does not implicate ICANN's contractual authority. | 1 | |
| The complaint is out of scope because it is incomplete or broad. | 3 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 12 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 148 | |
| Failure To Notify | The complaint is out of scope because it is about a private dispute that does not implicate ICANN's contractual authority. | 1 |
| The complaint is out of scope because it is about a registrar that is not within ICANN's contractual authority. | 1 | |
| The complaint is out of scope because it is incomplete or broad. | 1 | |
| 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. | 3 | |
| The complaint is out of scope because the domain is not registered. | 1 | |
| Privacy/Proxy | The complaint is out of scope because it is a duplicate of an open complaint. | 3 |
| The complaint is out of scope because the complainant did not provide the requested information. | 7 | |
| Registrar Contact | The complaint is out of scope because ICANN does not process complaints regarding website content. | 1 |
| The complaint is out of scope because ICANN is not a registrar. | 2 | |
| The complaint is out of scope because ICANN terminated the registrar's accreditation. | 1 | |
| The complaint is out of scope because it is a duplicate of a closed complaint. | 2 | |
| The complaint is out of scope because it is a duplicate of an open complaint. | 3 | |
| The complaint is out of scope because it is about an illegal activity that is outside of ICANN's contractual authority. | 2 | |
| The complaint is out of scope because it is incomplete or broad. | 1 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 4 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 12 | |
| The complaint is out of scope because the domain is not registered. | 5 | |
| Registrar Information Specification (RIS) | The complaint is out of scope because customer service issues are outside of ICANN's contractual authority. | 3 |
| The complaint is out of scope because ICANN does not process complaints regarding website content. | 1 | |
| The complaint is out of scope because ICANN is not a registrar. | 1 | |
| The complaint is out of scope because it is a duplicate of a closed complaint. | 2 | |
| The complaint is out of scope because it is a duplicate of an open complaint. | 4 | |
| The complaint is out of scope because it is about a registrar that is not within ICANN's contractual authority. | 1 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 5 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 25 | |
| The complaint is out of scope because there is no evidence of an abuse report with the registrar. | 1 | |
| Transfer | The complaint is out of scope because customer service issues are outside of ICANN's contractual authority. | 3 |
| The complaint is out of scope because it contains offensive language. | 2 | |
| The complaint is out of scope because it is a duplicate of a closed complaint. | 6 | |
| The complaint is out of scope because it is a duplicate of an open complaint. | 160 | |
| The complaint is out of scope because it is about a private dispute that does not implicate ICANN's contractual authority. | 11 | |
| The complaint is out of scope because it is about an illegal activity that is outside of ICANN's contractual authority. | 2 | |
| The complaint is out of scope because it is incomplete or broad. | 8 | |
| The complaint is out of scope because it is not about an ICANN contracted party. | 1 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 84 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 681 | |
| The complaint is out of scope because the complainant is not the domain registrant or the registrant's designated agent for purposes of a change of registrant. | 2 | |
| The complaint is out of scope because the complainant is not the transfer contact for the domain. | 23 | |
| The complaint is out of scope because the domain is not registered. | 17 | |
| The complaint is out of scope because the unauthorized transfer was due to hijacking. | 7 | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | The 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. | 3 | |
| 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. | 12 | |
| The complaint is out of scope because there is no Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding. | 18 | |
| WHOIS Accuracy Reporting System (WHOIS ARS) | The complaint is out of scope because ICANN terminated the registrar's accreditation. | 1 |
| The complaint is out of scope because it is about a domain with known compliant WHOIS. | 1 | |
| The complaint is out of scope because it is about information that does not exist in the domain's current WHOIS. | 384 | |
| The complaint is out of scope because it is about the WHOIS of a known privacy or proxy service. | 155 | |
| The complaint is out of scope because it is incomplete or broad. | 1 | |
| The complaint is out of scope because it is irrelevant to ICANN's contractual authority. | 2 | |
| The complaint is out of scope because the domain is not registered. | 102 | |
| WHOIS Format | The complaint is out of scope because customer service issues are outside of ICANN's contractual authority. | 8 |
| The complaint is out of scope because ICANN does not process complaints regarding website content. | 5 | |
| The complaint is out of scope because ICANN is not a registrar. | 18 | |
| The complaint is out of scope because it is a duplicate of a closed complaint. | 121 | |
| The complaint is out of scope because it is a duplicate of an open complaint. | 6 | |
| The complaint is out of scope because it is about a private dispute that does not implicate ICANN's contractual authority. | 2 | |
| The complaint is out of scope because it is about a registrar that is not within ICANN's contractual authority. | 8 | |
| The complaint is out of scope because it is about an illegal activity that is outside of ICANN's contractual authority. | 3 | |
| The complaint is out of scope because it is incomplete or broad. | 7 | |
| The complaint is out of scope because it is not about an ICANN contracted party. | 1 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 22 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 26 | |
| The complaint is out of scope because the domain is not registered. | 4 | |
| WHOIS Inaccuracy | The complaint is out of scope because customer service issues are outside of ICANN's contractual authority. | 22 |
| The complaint is out of scope because ICANN does not process complaints regarding website content. | 57 | |
| The complaint is out of scope because ICANN does not process WHOIS accuracy complaints regarding third-level domains. | 26 | |
| The complaint is out of scope because ICANN is not a registrar. | 41 | |
| The complaint is out of scope because ICANN terminated the registrar's accreditation. | 1 | |
| The complaint is out of scope because it contains offensive language. | 3 | |
| The complaint is out of scope because it is a duplicate of a closed complaint. | 72 | |
| The complaint is out of scope because it is a duplicate of an open complaint. | 208 | |
| The complaint is out of scope because it is about a domain with known compliant WHOIS. | 4 | |
| The complaint is out of scope because it is about a private dispute that does not implicate ICANN's contractual authority. | 30 | |
| The complaint is out of scope because it is about an illegal activity that is outside of ICANN's contractual authority. | 24 | |
| The complaint is out of scope because it is about information that does not exist in the domain's current WHOIS. | 90 | |
| The complaint is out of scope because it is about the WHOIS of a known privacy or proxy service. | 57 | |
| The complaint is out of scope because it is incomplete or broad. | 308 | |
| The complaint is out of scope because it is irrelevant to ICANN's contractual authority. | 24 | |
| The complaint is out of scope because it is not about an ICANN contracted party. | 2 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 321 | |
| The complaint is out of scope because it is regarding the complainant's own domain. | 201 | |
| The complaint is out of scope because it is regarding the complainant's own domain; include information about change of registrant for domain with privacy/proxy service. | 49 | |
| The complaint is out of scope because it is regarding the complainant's own domain; includes information about change of registrant. | 190 | |
| The complaint is out of scope because spam is outside of ICANN's contractual authority. | 5 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 1762 | |
| The complaint is out of scope because the domain is not registered. | 118 | |
| The complaint is out of scope because there is no evidence of an abuse report with the registrar. | 1 | |
| WHOIS Quality Review | The complaint is out of scope because it is a duplicate of an open complaint. | 1 |
| WHOIS Service Level Agreements | The complaint is out of scope because customer service issues are outside of ICANN's contractual authority. | 17 |
| The complaint is out of scope because ICANN does not process complaints regarding website content. | 20 | |
| The complaint is out of scope because ICANN is not a registrar. | 10 | |
| The complaint is out of scope because it is a duplicate of a closed complaint. | 5 | |
| The complaint is out of scope because it is a duplicate of an open complaint. | 4 | |
| The complaint is out of scope because it is about a private dispute that does not implicate ICANN's contractual authority. | 6 | |
| The complaint is out of scope because it is about a registrar that is not within ICANN's contractual authority. | 6 | |
| The complaint is out of scope because it is about an illegal activity that is outside of ICANN's contractual authority. | 3 | |
| The complaint is out of scope because it is incomplete or broad. | 7 | |
| The complaint is out of scope because it is not about an ICANN contracted party. | 1 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 7 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 26 | |
| The complaint is out of scope because the domain is not registered. | 1 | |
| WHOIS Unavailable | The complaint is out of scope because customer service issues are outside of ICANN's contractual authority. | 2 |
| The complaint is out of scope because ICANN does not process complaints regarding website content. | 3 | |
| The complaint is out of scope because ICANN is not a registrar. | 2 | |
| The 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. | 8 | |
| The complaint is out of scope because it is about a private dispute that does not implicate ICANN's contractual authority. | 4 | |
| The complaint is out of scope because it is about an illegal activity that is outside of ICANN's contractual authority. | 5 | |
| The complaint is out of scope because it is incomplete or broad. | 11 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 9 | |
| The complaint is out of scope because spam is outside of ICANN's contractual authority. | 1 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 31 | |
| The complaint is out of scope because the domain is not registered. | 1 | |
| Out of Scope Category Total | 6427 |
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 |
|---|---|---|
| Data Escrow | The matter has been withdrawn due to an ICANN issue. | 1 |
| Fees | Additional processing by ICANN Accounting is required before the Compliance process can continue. | 2 |
| WHOIS Inaccuracy | The matter has been withdrawn due to an ICANN issue. | 1 |
| ICANN Issue Category Total | 4 |
Other
This includes complaints previously closed which have been reopened and are currently active.
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Abuse | The complaint, previously closed, has been reopened and is currently active. | 1 |
| Transfer | The complaint, previously closed, has been reopened and is currently active. | 69 |
| WHOIS Inaccuracy | The complaint, previously closed, has been reopened and is currently active. | 7 |
| WHOIS Unavailable | The complaint, previously closed, has been reopened and is currently active. | 2 |
| Other Category Total | 79 |