ICANN Contractual Compliance Dashboard for January 2020
ICANN provides a monthly dashboard summarizing contractual compliance complaints activity for the month. These monthly metrics show the complaint volume as they advance through the overall contractual compliance Informal & Formal process. Learn more about this dashboard report »
Registrars
Registrar Complaint Volume & Distribution
| Complaint Type | January 2020 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Abuse | 113 | 135 |
| Customer Service | 21 | 23 |
| Data Escrow | 55 | 0 |
| Domain Deletion | 42 | 36 |
| Domain Name System Security Extensions (DNSSEC), Internationalized Domain Names (IDN), Internet Protocol Version 6 (IPv6) | 9 | 2 |
| Domain Renewal | 105 | 69 |
| Failure To Notify | 8 | 1 |
| Fees | 5 | 0 |
| Privacy/Proxy | 1 | 0 |
| Registrar Contact | 14 | 15 |
| Registrar Information Specification (RIS) | 14 | 23 |
| Registrar Other | 3 | 6 |
| Transfer | 269 | 207 |
| Uniform Domain-Name Dispute-Resolution (UDRP) | 26 | 9 |
| WHOIS Format | 6 | 6 |
| WHOIS Inaccuracy breakdown in italics | 679 | 798 |
| Quality Review | - | - |
| Bulk Submission | - | - |
| Individual Submission | 679 | 798 |
| Accuracy Reporting System | - | - |
| WHOIS Service Level Agreements | 2 | - |
| WHOIS Unavailable | 17 | 23 |
| Total | 1389 | 1353 |
Note: ”Closed before 1st Inquiry/Notice” represents complaints closed during the reporting period and can include complaints received in a prior period.
Compliance Process Volume & Turnaround Time
| January 2020 | Quantity Sent | Process Turnaround Time |
|---|---|---|
| Volume 1st Notice Sent | 149 | 11.5 |
| Volume 2nd Notice Sent | 44 | 16.5 |
| Volume 3rd Notice Sent | 14 | 7.5 |
| Volume Breach | - | - |
| Volume Suspension | - | - |
| Volume Termination | 1 | 20.0 |
| Volume Contract Non-Renewal | - | - |
| Volume Closed All - as of Current Month = 1,603 | ||
Note: “Quantity Sent” represents activity which occurred during the reporting period and can include complaints received in a prior period.
Additional Information on the Subject Matter of Complaints
| Details on Abuse Complaints | January 2020 |
|---|---|
| New gTLD | |
| N/A1 | 12 |
| Pharming, Phishing | 1 |
| New gTLD Total | 13 |
| Legacy gTLD | |
| N/A1 | 74 |
| Fraudulent, deceptive practices | 1 |
| Pharmaceuticals | 1 |
| Pharming, Phishing | 6 |
| Pharming, Phishing | Trademark or Copyright Infringement | Fraudulent, deceptive practices | 1 |
| Registrar Abuse contact | 1 |
| Spam | 1 |
| Trademark or Copyright Infringement | 2 |
| Legacy gTLD Total | 87 |
| Not Specified2 | |
| N/A1 | 13 |
| Not Specified Total | 13 |
| Details on Abuse Complaints Total | 113 |
| Details on Transfer Complaints | January 2020 |
|---|---|
| New gTLD | |
| N/A1 | 8 |
| Transfer | 3 |
| New gTLD Total | 11 |
| Legacy gTLD | |
| N/A1 | 169 |
| COR | 8 |
| Transfer | 52 |
| Unauthorized COR | 4 |
| Unauthorized Transfer | 8 |
| Legacy gTLD Total | 241 |
| Not Specified2 | |
| N/A1 | 17 |
| Not Specified Total | 17 |
| Details on Transfer Complaints Total | 269 |
| Details on WHOIS Inaccuracy Complaints | January 2020 |
|---|---|
| New gTLD | |
| N/A1 | 49 |
| New gTLD Total | 49 |
| Legacy gTLD | |
| NA 1 | 540 |
| Operability - WHOIS data inaccuracy | 23 |
| Legacy gTLD Total | 563 |
| Not Specified2 | |
| N/A1 | 67 |
| Not Specified Total | 67 |
| Details on WHOIS Inaccuracy Complaints Total | 679 |
1. "N/A" represents tickets which are in process and the detailed complaint type has not yet been determined, as well as tickets closed prior to 1st Notice.
2. "Not specified" represents complaints for which the TLD type is not specified. Domain Name or TLD information is not always provided in the complaint or November pertain to a Registrar or Registry.
Registrar Additional Information on Complaints Related to GAC Category 1 Safeguards
| Details on GAC Category 1 Type | Complaint Type | January 2020 |
|---|---|---|
| Intellectual Property | Abuse | 3 |
| Domain Deletion | 2 | |
| Domain Renewal | 2 | |
| Transfer | 3 | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | 1 | |
| WHOIS Inaccuracy | 17 | |
| Professional Services | Transfer | 2 |
| Total | 30 |
January 2020 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.
January 2020 Registrar Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 320 |
| Out of Scope | 1283 |
| Registrar Closed Complaints Total | 1603 |
January 2020 Registrar Closed Complaints Detail by Category and by Complaint Type
Resolved
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Abuse | The domain is suspended and suspension is a reasonable response to the abuse report. | 34 |
| The registrar demonstrated compliance. | 1 | |
| The registrar responded to the abuse report. | 3 | |
| Customer Service | The registrar demonstrated compliance. | 1 |
| Data Escrow | The registrar completed its data escrow deposit. | 4 |
| The registrar completed its initial data escrow deposit. | 1 | |
| Domain Deletion | The domain is no longer suspended. | 11 |
| The domain was not suspended at the time the complaint was processed. | 1 | |
| The registrar's deletion of the domain was compliant. | 2 | |
| Domain Renewal | The domain has been renewed with the same registrant. | 1 |
| The registrar corrected its Expired Registration Recovery Policy (ERRP) noncompliance. | 4 | |
| The registrar corrected its noncompliance. | 1 | |
| The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements. | 3 | |
| Registrar Other | The registrar corrected its noncompliance. | 32 |
| The registrar demonstrated compliance. | 3 | |
| Transfer | The change of registrant is not authorized. | 1 |
| The registrar corrected its noncompliance. | 1 | |
| The registrar demonstrated compliance with its contractual requirements. | 4 | |
| The transfer cannot be completed due to a dispute over the identity of the registrant or administrative contact. | 1 | |
| The transfer cannot be completed due to a transfer or registration within the past 60 days, or a change of registrant lock. | 3 | |
| The transfer cannot be completed due to evidence of fraud. | 2 | |
| The transfer cannot be completed due to lack of payment for the prior or current registration period. | 1 | |
| The transfer cannot be completed due to the change of registrant lock. | 1 | |
| The transfer has been completed. | 30 | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | The registrar demonstrated compliance with the Uniform Domain Name Dispute Resolution Policy (UDRP) requirements. | 3 |
| The registrar demonstrated compliance. | 1 | |
| The registrar verified the domain with the Uniform Domain Name Dispute Resolution Policy (UDRP) provider. | 3 | |
| The Uniform Domain Name Dispute Resolution Policy (UDRP) decision cannot be implemented due to an intervening lawsuit. | 1 | |
| WHOIS Inaccuracy | The domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint. | 95 |
| The registrar corrected its noncompliance. | 3 | |
| The registrar verified the domain's WHOIS information is correct. | 5 | |
| The WHOIS data has been updated. | 62 | |
| WHOIS Unavailable | The registrar's WHOIS service was restored. | 1 |
| Resolved Category Total | 320 |
Out of Scope
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Abuse | The complaint is out of scope because it is a duplicate of an open complaint. | 15 |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 13 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 97 | |
| Customer Service | 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. | 4 | |
| 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. | 12 | |
| The complaint is out of scope because the domain is not registered. | 1 | |
| Data Escrow | The complaint is out of scope because ICANN terminated the registrar's accreditation. | 1 |
| Domain Deletion | 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. | 22 | |
| The complaint is out of scope because the domain is not registered. | 1 | |
| Domain Name System Security Extensions (DNSSEC), Internationalized Domain Names (IDN), Internet Protocol Version 6 (IPv6) | The complaint is out of scope because it is regarding a country-code top-level domain. | 2 |
| Domain Renewal | The complaint is out of scope because it is a duplicate of an open complaint. | 12 |
| 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. | 52 | |
| Failure To Notify | The complaint is out of scope because it is a duplicate of an open complaint. | 1 |
| Registrar Contact | 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. | 5 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 9 | |
| Registrar Information Specification (RIS) | 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. | 10 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 3 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 9 | |
| Registrar Other | The complaint is out of scope because ICANN terminated the registrar's accreditation. | 3 |
| The complaint is out of scope because it is a duplicate of an open complaint. | 6 | |
| Transfer | 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 an open complaint. | 27 | |
| The complaint is out of scope because it is incomplete or broad. | 2 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 17 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 143 | |
| The complaint is out of scope because the complainant is not the transfer contact for the domain. | 2 | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | The complaint is out of scope because the complainant did not provide the requested information. | 8 |
| WHOIS Format | 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 an open complaint. | 1 | |
| 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. | 2 | |
| The complaint is out of scope because the domain is not registered. | 1 | |
| WHOIS Inaccuracy | 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 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 it is a duplicate of a closed complaint. | 1 | |
| The complaint is out of scope because it is a duplicate of an open complaint. | 21 | |
| The complaint is out of scope because it is irrelevant to ICANN's contractual authority. | 1 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 64 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 649 | |
| The complaint is out of scope because the domain is not registered. | 21 | |
| WHOIS Unavailable | 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. | 2 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 11 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 8 | |
| The complaint is out of scope because the domain is not registered. | 1 | |
| Out of Scope Category Total | 1283 |
ICANN Issue
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| ICANN Issue Category Total | 0 |
Registries
Registry Complaint Volume & Distribution
| Complaint Type | January 2020 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Abuse Contact Data | 5 | 3 |
| Bulk Zone File Access (ZFA) | 1 | 0 |
| Monthly Report | 5 | 0 |
| Registration Restrictions Dispute Resolution Procedure | 6 | 6 |
| Registry Data Escrow | 3 | 0 |
| Registry Fees | 3 | 0 |
| Registry Other | 3 | 13 |
| Service Level Agreement | 1 | 0 |
| Zone File Access | 131 | 74 |
| Grand Total | 158 | 96 |
Note: ”Closed before 1st Inquiry/Notice” represents complaints closed during the reporting period and can include complaints received in a prior period.
Compliance Process Volume & Turnaround Time
| January 2020 | Quantity Sent | Process Turnaround Time |
|---|---|---|
| Volume 1st Notice Sent | 69 | 8.8 |
| Volume 2nd Notice Sent | 6 | 4.8 |
| Volume 3rd Notice Sent | 1 | 3.5 |
| Volume Breach | - | - |
| Volume Suspension | - | - |
| Volume Termination | - | - |
| Volume Contract Non-Renewal | - | - |
| Volume Closed All - as of Current Month = 151 | ||
Note: “Quantity Sent” represents activity which occurred during the reporting period and can include complaints received in a prior period.
Registry Additional Information on Complaints Related to GAC Category 1 Safeguards
| Details on GAC Category 1 Type | Complaint Type | January 2020 |
|---|---|---|
| Bullying/Harassment | Zone File Access | 2 |
| Charity | Zone File Access | 1 |
| Corporate Identifiers | Registry Data Escrow | 1 |
| Zone File Access | 3 | |
| Intellectual Property | Zone File Access | 2 |
| Professional Services | Zone File Access | 2 |
| Total | 11 |
January 2020 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.
January 2020 Registry Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 122 |
| Out of Scope | 29 |
| Registry Closed Complaints Total | 151 |
January 2020 Registry Closed Complaints Detail by Category and by Complaint Type
Resolved
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Monthly Report | The registry demonstrated compliance. | 4 |
| Registry Fees | The registry paid its ICANN fees. | 1 |
| Registry Other | The registry corrected its noncompliance. | 3 |
| Zone File Access | The registry demonstrated compliance. | 61 |
| The request for zone file access was already approved by the registry operator at the time of processing the complaint. | 53 | |
| Resolved Category Total | 122 |
Out of Scope
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Abuse Contact Data | The complaint is out of scope because it is about a requirement that is not applicable to the selected registry. | 3 |
| Registration Restrictions Dispute Resolution Procedure | The complaint is out of scope because it is about a requirement that is not applicable to the selected registry. | 6 |
| Registry Other | 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 about a private dispute that does not implicate ICANN's contractual authority. | 1 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 11 | |
| Zone File Access | 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. | 2 | |
| The complaint is out of scope because it is about a requirement that is not applicable to the selected registry. | 2 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 2 | |
| Out of Scope Category Total | 29 |
Complaint Volume & Closure Rate
Volume Trend
| Jan-19 | Jan-19 | Feb-19 | Mar-19 | Apr-19 | May-19 | Jun-19 | Jul-19 | Aug-19 | Sep-19 | Oct-19 | Nov-19 | Dec-19 | Jan-20 |
| 2,274 | 1,934 | 2,244 | 2,130 | 1,948 | 2,705 | 2,155 | 1,589 | 1,616 | 1,702 | 1,580 | 2,579 | 1,547 |
Total Volume
| Counts | December 2019 | January 2020 |
|---|---|---|
| Total New | 2,579 | 1,547 |
| Total Closed | 1,742 | 1,754 |
Closure Rates
| Stage | December 2019 | January 2020 |
|---|---|---|
| Received All Target ≥ 55% | 44% | 58% |
| Current Month | 26% | 30% |
| Before 1st Inquiry / Notice | 37% | 48% |
| Before 2nd Inquiry / Notice | 5% | 8% |
| Before 3rd Inquiry / Notice | 1% | 1% |
ICANN Staff Average Turnaround Time
| Measures | December 2019 | January 2020 |
|---|---|---|
| Open to 1st Inquiry / Notice | 2.2 | 2.0 |
| 2nd WIP | 8.0 | 9.2 |
| 3rd WIP | 9.7 | 6.7 |
| Formal Notices | - | - |
Contractual Compliance Overall Process Turnaround Time
| Measures | December 2019 | January 2020 |
|---|---|---|
| Received to Closed | 19.1 | 23.0 |
Note: Average Turnaround Time is shown in business days.