ICANN Contractual Compliance Dashboard for February 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 | February 2020 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Abuse | 151 | 87 |
| CEO Certification | 22 | 1 |
| Customer Service | 19 | 15 |
| Data Escrow | 19 | - |
| Domain Deletion | 30 | 33 |
| Domain Name System Security Extensions (DNSSEC), Internationalized Domain Names (IDN), Internet Protocol Version 6 (IPv6) | 14 | 17 |
| Domain Renewal | 89 | 86 |
| Failure To Notify | 9 | 11 |
| Fees | 5 | - |
| Privacy/Proxy | 2 | 1 |
| Registrar Contact | 12 | 7 |
| Registrar Information Specification (RIS) | 9 | 9 |
| Registrar Other | 3 | - |
| Transfer | 253 | 177 |
| Uniform Domain-Name Dispute-Resolution (UDRP) | 20 | 11 |
| WHOIS Format | 2 | 4 |
| WHOIS Inaccuracy breakdown in italics | 575 | 582 |
| Quality Review | - | - |
| Bulk Submission | - | - |
| Individual Submission | 575 | 582 |
| Accuracy Reporting System | - | - |
| WHOIS Service Level Agreements | 7 | - |
| WHOIS Unavailable | 10 | 12 |
| Total | 1251 | 1053 |
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
| February 2020 | Quantity Sent | Process Turnaround Time |
|---|---|---|
| Volume 1st Notice Sent | 118 | 11.7 |
| Volume 2nd Notice Sent | 37 | 21.8 |
| Volume 3rd Notice Sent | 18 | 6.0 |
| Volume Breach | 1 | - |
| Volume Suspension | - | - |
| Volume Termination | - | - |
| Volume Contract Non-Renewal | - | - |
| Volume Closed All - as of Current Month = 1,218 | ||
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 | February 2020 |
|---|---|
| New gTLD | |
| N/A1 | 12 |
| Fraudulent, deceptive practices | 1 |
| Spam | 2 |
| New gTLD Total | 15 |
| Legacy gTLD | |
| N/A1 | 118 |
| Other | 1 |
| Pharming, Phishing | 3 |
| Registrar Abuse contact | 1 |
| Trademark or Copyright Infringement | 1 |
| Legacy gTLD Total | 124 |
| Not Specified2 | |
| N/A1 | 12 |
| Not Specified Total | 12 |
| Details on Abuse Complaints Total | 151 |
| Details on Transfer Complaints | February 2020 |
|---|---|
| New gTLD | |
| N/A1 | 4 |
| Transfer | 2 |
| New gTLD Total | 6 |
| Legacy gTLD | |
| N/A1 | 192 |
| Transfer | 31 |
| Unauthorized COR | 1 |
| Unauthorized Transfer | 1 |
| Legacy gTLD Total | 225 |
| Not Specified2 | |
| N/A1 | 22 |
| Not Specified Total | 22 |
| Details on Transfer Complaints Total | 253 |
| Details on WHOIS Inaccuracy Complaints | February 2020 |
|---|---|
| New gTLD | |
| N/A1 | 40 |
| Operability - WHOIS data inaccuracy | 1 |
| New gTLD Total | 41 |
| Legacy gTLD | |
| NA 1 | 452 |
| Operability - WHOIS data inaccuracy | 3 |
| Legacy gTLD Total | 455 |
| Not Specified2 | |
| N/A1 | 78 |
| Operability - WHOIS data inaccuracy | 1 |
| Not Specified Total | 79 |
| Details on WHOIS Inaccuracy Complaints Total | 575 |
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 | February 2020 |
|---|---|---|
| Intellectual Property | Abuse | 2 |
| Transfer | 1 | |
| WHOIS Inaccuracy | 5 | |
| Total | 8 |
February 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.
February 2020 Registrar Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 231 |
| Out of Scope | 986 |
| ICANN Issue | 1 |
| Registrar Closed Complaints Total | 1218 |
February 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. | 9 |
| The registrar corrected its noncompliance. | 1 | |
| The registrar demonstrated compliance. | 1 | |
| The registrar responded to the abuse report. | 29 | |
| CEO Certification | The registrar submitted its annual compliance certificate. | 4 |
| Data Escrow | The registrar completed its data escrow deposit. | 3 |
| The registrar's data escrow file content issue is resolved. | 1 | |
| Domain Deletion | The domain is no longer suspended. | 8 |
| The domain was not suspended at the time the complaint was processed. | 5 | |
| Domain Name System Security Extensions (DNSSEC), Internationalized Domain Names (IDN), Internet Protocol Version 6 (IPv6) | The registrar already supports Domain Name System Security Extensions (DNSSEC). | 1 |
| Domain Renewal | The domain has been renewed with the same registrant. | 1 |
| The registrar corrected its Expired Registration Recovery Policy (ERRP) noncompliance. | 3 | |
| The registrar corrected its noncompliance. | 1 | |
| The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements. | 3 | |
| Fees | The registrar paid its ICANN fees. | 3 |
| Registrar Other | The registrar corrected its noncompliance. | 15 |
| Transfer | The change of registrant is not authorized. | 1 |
| The registrar corrected its noncompliance. | 2 | |
| The registrar demonstrated compliance with its contractual requirements. | 5 | |
| The registrar demonstrated compliance with the change of registrant requirements. | 1 | |
| 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. | 4 | |
| The transfer cannot be completed due to a transfer or registration within the past 60 days, or a change of registrant lock. | 1 | |
| The transfer cannot be completed due to the change of registrant lock. | 1 | |
| The transfer cannot be completed without proof of the transfer contact's identity. | 1 | |
| The transfer has been completed. | 17 | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | The registrar corrected its noncompliance. | 2 |
| The registrar verified the domain with the Uniform Domain Name Dispute Resolution Policy (UDRP) provider. | 1 | |
| WHOIS Inaccuracy | The domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint. | 69 |
| The registrar corrected its noncompliance. | 6 | |
| The registrar demonstrated compliance. | 1 | |
| The WHOIS data has been updated. | 24 | |
| WHOIS Unavailable | The registrar corrected its noncompliance. | 1 |
| The registrar demonstrated compliance. | 4 | |
| The registrar's WHOIS service was compliant at the time the complaint was received. | 1 | |
| The registrar's WHOIS service was restored. | 1 | |
| Resolved Category Total | 231 |
Out of Scope
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Abuse | The complaint is out of scope because ICANN does not process complaints regarding website content. | 1 |
| 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. | 12 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 53 | |
| CEO Certification | The complaint is out of scope because ICANN terminated the registrar's accreditation. | 1 |
| Customer Service | 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. | 3 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 10 | |
| Data Escrow | The complaint is out of scope because the registrar voluntarily terminated its ICANN accreditation. | 1 |
| Domain Deletion | 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. | 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. | 14 | |
| 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. | 3 | |
| 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 spam is outside of ICANN's contractual authority. | 1 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 6 | |
| Domain Renewal | The complaint is out of scope because it is a duplicate of an open complaint. | 20 |
| The complaint is out of scope because the complainant did not provide the requested information. | 66 | |
| Failure To Notify | The complaint is out of scope because ICANN does not process complaints regarding website content. | 2 |
| 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 an illegal activity that is outside of ICANN's contractual authority. | 2 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 6 | |
| Privacy/Proxy | The complaint is out of scope because the complainant did not provide the requested information. | 1 |
| Registrar Contact | 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. | 2 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 3 | |
| Registrar Information Specification (RIS) | 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. | 2 | |
| 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 | |
| Registrar Other | The complaint is out of scope because ICANN terminated the registrar's accreditation. | 1 |
| Transfer | 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. | 1 | |
| The complaint is out of scope because it is a duplicate of an open complaint. | 35 | |
| 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 regarding a country-code top-level domain. | 21 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 110 | |
| The complaint is out of scope because the complainant is not the transfer contact for the domain. | 2 | |
| The complaint is out of scope because the unauthorized transfer was due to hijacking. | 9 | |
| 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 about a private dispute that does not implicate ICANN's contractual authority. | 5 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 5 | |
| WHOIS Format | The complaint is out of scope because ICANN does not process complaints regarding website content. | 1 |
| The complaint is out of scope because it is a duplicate of a closed complaint. | 1 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 2 | |
| 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 WHOIS accuracy complaints regarding third-level domains. | 4 | |
| The complaint is out of scope because it is a duplicate of a closed complaint. | 3 | |
| 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 domain with known compliant WHOIS. | 1 | |
| The complaint is out of scope because it is incomplete or broad. | 4 | |
| 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. | 73 | |
| The complaint is out of scope because it is regarding the complainant's own domain. | 1 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 411 | |
| The complaint is out of scope because the domain is not registered. | 16 | |
| WHOIS Unavailable | The complaint is out of scope because it is regarding a country-code top-level domain. | 6 |
| The complaint is out of scope because the complainant did not provide the requested information. | 2 | |
| Out of Scope Category Total | 986 |
ICANN Issue
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| CEO Certification | The matter has been withdrawn due to an ICANN issue. | 1 |
| ICANN Issue Category Total | 1 |
Registries
Registry Complaint Volume & Distribution
| Complaint Type | February 2020 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Abuse Contact Data | 4 | 3 |
| Bulk Zone File Access (ZFA) | - | - |
| Code Of Conduct | 3 | - |
| Monthly Report | 8 | - |
| Registration Restrictions Dispute Resolution Procedure | 1 | 1 |
| Registry Data Escrow | 17 | - |
| Registry Fees | - | - |
| Registry Other | 3 | - |
| Reserved Names/Controlled Interruption | 3 | 14 |
| Service Level Agreement Alerts | 1 | - |
| Uniform Rapid Suspension (URS) | 1 | - |
| Zone File Access | 68 | 27 |
| Grand Total | 109 | 45 |
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
| February 2020 | Quantity Sent | Process Turnaround Time |
|---|---|---|
| Volume 1st Notice Sent | 84 | 6.0 |
| Volume 2nd Notice Sent | 52 | 5.0 |
| Volume 3rd Notice Sent | 14 | 6.0 |
| Volume Breach | - | - |
| Volume Suspension | - | - |
| Volume Termination | - | - |
| Volume Contract Non-Renewal | - | - |
| Volume Closed All - as of Current Month = 144 | ||
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 | February 2020 |
|---|---|---|
| Financial | Zone File Access | 2 |
| Health and Fitness | Uniform Rapid Suspension (URS) | 1 |
| Zone File Access | 1 | |
| Intellectual Property | Reserved Names/Controlled Interruption | 3 |
| Zone File Access | 1 | |
| Total | 8 |
February 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.
February 2020 Registry Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 106 |
| Out of Scope | 38 |
| Registry Closed Complaints Total | 144 |
February 2020 Registry Closed Complaints Detail by Category and by Complaint Type
Resolved
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Bulk Zone File Access (ZFA) | The registry corrected its noncompliance. | 1 |
| Monthly Report | The registry demonstrated compliance. | 1 |
| Registry Data Escrow | ICANN received the required registry data escrow notification. | 18 |
| Registry Fees | The registry paid its ICANN fees. | 1 |
| Registry Other | The registry demonstrated compliance. | 1 |
| Service Level Agreement Alerts | The registry corrected its noncompliance. | 2 |
| Zone File Access | The registry demonstrated compliance. | 78 |
| The request for zone file access was already approved by the registry operator at the time of processing the complaint. | 4 | |
| Resolved Category Total | 106 |
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. | 1 |
| Reserved Names/Controlled Interruption | The complaint is out of scope because the complainant did not provide the requested information. | 14 |
| 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. | 18 | |
| The complaint is out of scope because it is about a requirement that is not applicable to the selected registry. | 1 | |
| Out of Scope Category Total | 38 |
Complaint Volume & Closure Rate
Volume Trend
| Feb-19 | Mar-19 | Apr-19 | May-19 | Jun-19 | Jul-19 | Aug-19 | Sep-19 | Oct-19 | Nov-19 | Dec-19 | Jan-20 | Feb-20 |
| 1934 | 2244 | 2130 | 1948 | 2705 | 2155 | 1589 | 1616 | 1702 | 1580 | 2579 | 1547 | 1360 |
Total Volume
| Counts | January 2020 | February 2020 |
|---|---|---|
| Total New | 1,547 | 1,360 |
| Total Closed | 1,754 | 1,362 |
Closure Rates
| Stage | January 2020 | February 2020 |
|---|---|---|
| Received All Target ≥ 55% | 58% | 52% |
| Current Month | 30% | 25% |
| Before 1st Inquiry / Notice | 48% | 42% |
| Before 2nd Inquiry / Notice | 8% | 7% |
| Before 3rd Inquiry / Notice | 1% | 2% |
ICANN Staff Average Turnaround Time
| Measures | January 2020 | February 2020 |
|---|---|---|
| Open to 1st Inquiry / Notice | 2.0 | 2.8 |
| 2nd WIP | 9.2 | 6.4 |
| 3rd WIP | 6.7 | 12.8 |
| Formal Notices | - | 1.0 |
Contractual Compliance Overall Process Turnaround Time
| Measures | January 2020 | February 2020 |
|---|---|---|
| Received to Closed | 23.0 | 30.5 |
Note: Average Turnaround Time is shown in business days.