ICANN Contractual Compliance Dashboard for June 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 | June 2020 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Abuse | 177 | 204 |
| Customer Service | 41 | 48 |
| Data Escrow | 38 | - |
| Domain Deletion | 53 | 48 |
| Domain Name System Security Extensions (DNSSEC), Internationalized Domain Names (IDN), Internet Protocol Version 6 (IPv6) | 11 | 3 |
| Domain Renewal | 92 | 126 |
| Failure To Notify | 16 | 8 |
| Fees | 1 | - |
| Privacy/Proxy | 4 | 1 |
| Registrar Contact | 4 | 8 |
| Registrar Information Specification (RIS) | 9 | 10 |
| Registrar Other | 3 | 2 |
| Transfer | 352 | 379 |
| Uniform Domain-Name Dispute-Resolution (UDRP) | 19 | 45 |
| WHOIS Format | 6 | 7 |
| WHOIS Inaccuracy breakdown in italics | 314 | 547 |
| Quality Review | - | - |
| Bulk Submission | - | - |
| Individual Submission | 314 | 547 |
| Accuracy Reporting System | - | - |
| WHOIS Service Level Agreements | 2 | 1 |
| WHOIS Unavailable | 13 | 11 |
| Total | 1155 | 1448 |
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
| June 2020 | Quantity Sent | Process Turnaround Time |
|---|---|---|
| Volume 1st Notice Sent | 135 | 17.8 |
| Volume 2nd Notice Sent | 27 | 12.1 |
| Volume 3rd Notice Sent | 10 | 6.0 |
| Volume Breach | - | - |
| Volume Suspension | - | - |
| Volume Termination | - | - |
| Volume Contract Non-Renewal | - | - |
| Volume Closed All - as of Current Month = 1,623 | ||
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 | June 2020 |
|---|---|
| New gTLD | |
| N/A1 | 15 |
| Trademark or Copyright Infringement | 5 |
| New gTLD Total | 20 |
| Legacy gTLD | |
| N/A1 | 118 |
| Fraudulent, deceptive practices | 5 |
| Pharmaceuticals | 1 |
| Pharming, Phishing | 1 |
| Trademark or Copyright Infringement | 20 |
| Legacy gTLD Total | 145 |
| Not Specified2 | |
| N/A1 | 12 |
| Not Specified Total | 12 |
| Details on Abuse Complaints Total | 177 |
| Details on Transfer Complaints | June 2020 |
|---|---|
| New gTLD | |
| N/A1 | 7 |
| Transfer | 3 |
| New gTLD Total | 10 |
| Legacy gTLD | |
| N/A1 | 153 |
| COR | 5 |
| Transfer | 116 |
| Transfer | COR | 3 |
| Transfer | Unauthorized COR | 1 |
| Unauthorized COR | 10 |
| Unauthorized Transfer | 17 |
| Unauthorized Transfer | Unauthorized COR | 1 |
| Legacy gTLD Total | 306 |
| Not Specified2 | |
| N/A1 | 36 |
| Not Specified Total | 36 |
| Details on Transfer Complaints Total | 352 |
| Details on WHOIS Inaccuracy Complaints | June 2020 |
|---|---|
| New gTLD | |
| N/A1 | 24 |
| Operability - WHOIS data inaccuracy | 1 |
| New gTLD Total | 25 |
| Legacy gTLD | |
| NA 1 | 234 |
| Identity | 3 |
| Operability - WHOIS data inaccuracy | 8 |
| Legacy gTLD Total | 245 |
| Not Specified2 | |
| N/A1 | 44 |
| Not Specified Total | 44 |
| Details on WHOIS Inaccuracy Complaints Total | 314 |
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 | June 2020 |
|---|---|---|
| Financial | Abuse | 1 |
| Health and Fitness | Charity | Transfer | 1 |
| Intellectual Property | Abuse | 2 |
| Domain Deletion | 1 | |
| Transfer | 2 | |
| WHOIS Inaccuracy | 8 | |
| Professional Services | Domain Renewal | 1 |
| Total | 16 |
Registrar Complaints with Evidence of Alleged Violation of the Temporary Specification - 1 February 2020 to Date
| Complaint Type | Temp Spec-related Requirements | Received |
|---|---|---|
| Abuse | Third Party Access | 11 |
| Customer Service | Third Party Access | 1 |
| WHOIS Inaccuracy | RDDS | 20 |
"Complaint type" refers to the specific webform used by the complainant at submission.
Compliance extended the timeline in this chart in order to capture all complaints identified as relating to the Temporary Specification, notwithstanding the date we received or reviewed the complaint. February reflects the first time that Compliance published this data.
- Third Party Access complaints relate to allegations that a registrar failed to provide or respond to a request for reasonable access to non-public Registration Data per Section 4.1 of Appendix A.
- RDDS complaints relate to non-compliance with the display of Registration Data in a registrar’s Registration Data Directory Service(s) (RDDS) per Sections 2-3 of Appendix A (e.g., registrar is not providing an anonymized email address or a web form to facilitate email communication with the relevant contact in the email field(s)).
Registrar Inquiries/Notices Related to Temporary Specification Sent and Closed in June 2020
| Temp Spec-related Requirements | 1st Inquiry/Notice | 2nd Inquiry/Notice | 3rd Inquiry/Notice | Closed | Resolved Code |
|---|---|---|---|---|---|
| Third Party Access | - | 1 | - | 1 | The registrar corrected its noncompliance. |
| RDDS | 4 | 2 | 1 | 3 | The registrar corrected its noncompliance. |
Numbers above reflect the notifications sent and the notifications closed within the month. They do not include communications in between notifications sent to request clarification or additional evidence following a contracted party’s response.
A single notification can encompass multiple complaints. Further, Compliance may have included complaints received in notifications processed and closed in prior months or may be under process. For example, concerning the charts above:
- Compliance addressed the eleven complaints received in the abuse complaint type through one single notification processed in prior months.
- One third party access notification that Compliance sent in a prior month was closed in June.
- Three RDDS notifications that Compliance sent in prior months were also closed in June.
Examples of “the registrar corrected its noncompliance” scenarios:
- Registrar implemented changes to ensure it was providing reasonable access to non-public Registration Data per Section 4.1 of Appendix A.
- Registrar implemented changes to the display of Registration Data in its RDDS to address the concerns raised in the compliance inquiry/notice (e.g., registrar is now providing an anonymized email address or a web form to facilitate email communication with the relevant contact).
June 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.
June 2020 Registrar Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 272 |
| Out of Scope | 1351 |
| ICANN Issue | - |
| Registrar Closed Complaints Total | 1623 |
June 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. | 45 |
| The registrar published the required abuse contact information. | 1 | |
| The registrar responded to the abuse report. | 14 | |
| CEO Certification | The registrar submitted its annual compliance certificate. | 1 |
| The registrar's annual compliance certificate has been corrected. | 1 | |
| Data Escrow | The registrar completed its data escrow deposit. | 2 |
| 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. | 3 | |
| The registrar restored the domain. | 1 | |
| 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 registrar corrected its Expired Registration Recovery Policy (ERRP) noncompliance. | 2 |
| The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements. | 5 | |
| Fees | The registrar paid its ICANN fees. | 1 |
| Registrar Other | The registrar corrected its noncompliance. | 9 |
| Transfer | The registrar demonstrated compliance with its contractual requirements. | 2 |
| 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. | 6 | |
| 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. | 2 | |
| The transfer cannot be completed due to evidence of fraud. | 1 | |
| The transfer cannot be completed due to the change of registrant lock. | 2 | |
| The transfer cannot be completed without proof of the transfer contact's identity. | 6 | |
| The transfer has been completed. | 33 | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | The registrar corrected its noncompliance. | 4 |
| The registrar demonstrated compliance with the Uniform Domain Name Dispute Resolution Policy (UDRP) requirements. | 1 | |
| The registrar locked a domain subject to a Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding. | 11 | |
| WHOIS Inaccuracy | The domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint. | 85 |
| The registrar corrected its noncompliance. | 2 | |
| The registrar demonstrated compliance. | 6 | |
| The registrar verified the domain's WHOIS information is correct. | 1 | |
| The WHOIS data has been updated. | 10 | |
| WHOIS Unavailable | The registrar's WHOIS service is now compliant. | 1 |
| The registrar's WHOIS service was restored. | 1 | |
| Resolved Category Total | 272 |
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. | 4 |
| 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. | 24 | |
| 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 incomplete or broad. | 1 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 10 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 123 | |
| The complaint is out of scope because the domain is not registered. | 1 | |
| Customer Service | 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. | 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. | 13 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 30 | |
| Domain Deletion | 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. | 6 | |
| 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. | 2 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 27 | |
| 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. | 3 |
| Domain Renewal | 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 incomplete or broad. | 1 | |
| 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. | 104 | |
| The complaint is out of scope because the domain is not registered. | 1 | |
| Failure To Notify | The complaint is out of scope because it is a duplicate of an open complaint. | 7 |
| The complaint is out of scope because the complainant did not provide the requested information. | 1 | |
| 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 incomplete or broad. | 1 |
| The complaint is out of scope because the complainant did not provide the requested information. | 7 | |
| Registrar Information Specification (RIS) | 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. | 8 | |
| Registrar Other | The complaint is out of scope because ICANN terminated the registrar's accreditation. | 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 is a duplicate of a closed complaint. | 3 | |
| The complaint is out of scope because it is a duplicate of an open complaint. | 58 | |
| 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. | 35 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 260 | |
| The complaint is out of scope because the complainant is not the transfer contact for the domain. | 3 | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | The complaint is out of scope because ICANN does not process complaints regarding website content. | 5 |
| 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 private dispute that does not implicate ICANN's contractual authority. | 12 | |
| 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 regarding a country-code top-level domain. | 1 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 20 | |
| WHOIS Format | 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. | 5 | |
| WHOIS Inaccuracy | 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. | 38 | |
| The complaint is out of scope because it is about the WHOIS of a known privacy or proxy service. | 1 | |
| The complaint is out of scope because it is incomplete or broad. | 2 | |
| 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. | 43 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 420 | |
| The complaint is out of scope because the domain is not registered. | 10 | |
| WHOIS Service Level Agreements | The complaint is out of scope because the complainant did not provide the requested information. | 1 |
| 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. | 5 | |
| Out of Scope Category Total | 1351 |
Registries
Registry Complaint Volume & Distribution
| Complaint Type | June 2020 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Abuse Contact Data | 6 | 5 |
| Bulk Registration Data Access | 99 | - |
| Bulk Zone File Access (ZFA) | 1 | - |
| Code Of Conduct | 1 | - |
| Continued Operations Instrument (COI) | - | - |
| Monthly Report | 4 | - |
| Public Interest Commitments (PIC) | 4 | 4 |
| Registration Restrictions Dispute Resolution Procedure | 2 | 2 |
| Registry Data Escrow | 2 | - |
| Registry Other | 4 | 1 |
| Reserved Names/Controlled Interruption | 1 | - |
| Service Level Agreement | - | 1 |
| Service Level Agreement Alerts | 2 | - |
| Zone File Access | 81 | 34 |
| Grand Total | 207 | 47 |
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
| June 2020 | Quantity Sent | Process Turnaround Time |
|---|---|---|
| Volume 1st Notice Sent | 132 | 5.6 |
| Volume 2nd Notice Sent | 18 | 6.0 |
| Volume 3rd Notice Sent | 1 | 6.0 |
| Volume Breach | - | - |
| Volume Suspension | - | - |
| Volume Termination | - | - |
| Volume Contract Non-Renewal | - | - |
| Volume Closed All - as of Current Month = 87 | ||
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 | June 2020 |
|---|---|---|
| Corporate Identifiers | Zone File Access | 2 |
| Financial | Zone File Access | 1 |
| Intellectual Property | Reserved Names/Controlled Interruption | 1 |
| Total | 4 |
Registry Complaints with Evidence of Alleged Violation of the Temporary Specification - 1 February 2020 to Date
| Complaint Type | Temp Spec-related Requirements | Received |
|---|---|---|
| - | - | - |
“Complaint type” refers to the specific webform used by the complainant at submission.
Registry Inquiries/Notices Related to Temporary Specification Sent and Closed in June 2020
| Temp Spec-related Requirements | 1st Inquiry/Notice | 2nd Inquiry/Notice | 3rd Inquiry/Notice | Closed | Resolved Code |
|---|---|---|---|---|---|
| Third Pary Access | - | - | - | - | - |
| RDDS | - | - | - | - | - |
June 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.
June 2020 Registry Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 62 |
| Out of Scope | 25 |
| ICANN Issue | - |
| Registry Closed Complaints Total | 87 |
June 2020 Registry Closed Complaints Detail by Category and by Complaint Type
Resolved
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Continued Operations Instrument (COI) | The registry demonstrated compliance. | 1 |
| Monthly Report | The registry corrected its noncompliance. | 2 |
| Zone File Access | The registry demonstrated compliance. | 39 |
| The request for zone file access was already approved by the registry operator at the time of processing the complaint. | 20 | |
| Resolved Category Total | 62 |
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. | 5 |
| Public Interest Commitments (PIC) | The complaint is out of scope because it is about a requirement that is not applicable to the selected registry. | 4 |
| 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. | 2 |
| Registry Other | The complaint is out of scope because it is a duplicate of an open complaint. | 1 |
| Service Level Agreement | The complaint is out of scope because it is incomplete or broad. | 1 |
| Zone File Access | 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. | 6 | |
| 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 | 25 |
Complaint Volume & Closure Rate
Volume Trend
| Jun-19 | Jul-19 | Aug-19 | Sep-19 | Oct-19 | Nov-19 | Dec-19 | Jan-20 | Feb-20 | Mar-20 | Apr-20 | May-20 | Jun-20 |
| 2705 | 2155 | 1589 | 1616 | 1702 | 1580 | 2579 | 1547 | 1360 | 1747 | 1639 | 1584 | 1362 |
Total Volume
| Counts | May 2020 | June 2020 |
|---|---|---|
| Total New | 1,584 | 1,362 |
| Total Closed | 1,672 | 1,710 |
Closure Rates
| Stage | May 2020 | June 2020 |
|---|---|---|
| Received All Target ≥ 55% | 55% | 61% |
| Current Month | 28% | 31% |
| Before 1st Inquiry / Notice | 50% | 54% |
| Before 2nd Inquiry / Notice | 5% | 6% |
| Before 3rd Inquiry / Notice | 1% | 1% |
ICANN Staff Average Turnaround Time
| Measures | May 2020 | June 2020 |
|---|---|---|
| Open to 1st Inquiry / Notice | 2.2 | 1.7 |
| 2nd WIP | 5.9 | 5.6 |
| 3rd WIP | 19.5 | 12.2 |
| Formal Notices | - | - |
Contractual Compliance Overall Process Turnaround Time
| Measures | May 2020 | June 2020 |
|---|---|---|
| Received to Closed | 25.4 | 30.8 |
Note: Average Turnaround Time is shown in business days.