ICANN Contractual Compliance Dashboard for August 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 | August 2020 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Abuse | 198 | 133 |
| Customer Service | 37 | 35 |
| Data Escrow | 21 | - |
| Domain Deletion | 21 | 18 |
| Domain Name System Security Extensions (DNSSEC), Internationalized Domain Names (IDN), Internet Protocol Version 6 (IPv6) | 13 | 38 |
| Domain Renewal | 91 | 80 |
| Failure To Notify | 9 | - |
| Fees | 2 | - |
| Privacy/Proxy | 4 | 2 |
| Registrar Contact | 3 | 5 |
| Registrar Information Specification (RIS) | 35 | 33 |
| Registrar Other | 5 | - |
| Transfer | 337 | 366 |
| Uniform Domain-Name Dispute-Resolution (UDRP) | 5 | 17 |
| WHOIS Format | 4 | 2 |
| WHOIS Inaccuracy breakdown in italics | 522 | 451 |
| Quality Review | - | - |
| Bulk Submission | - | - |
| Individual Submission | 522 | 451 |
| Accuracy Reporting System | - | - |
| WHOIS Service Level Agreements | 6 | 3 |
| WHOIS Unavailable | 8 | 7 |
| Total | 1321 | 1190 |
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
| August 2020 | Quantity Sent | Process Turnaround Time |
|---|---|---|
| Volume 1st Notice Sent | 189 | 15.3 |
| Volume 2nd Notice Sent | 28 | 6.6 |
| Volume 3rd Notice Sent | 5 | 6.0 |
| Volume Breach | - | - |
| Volume Suspension | - | - |
| Volume Termination | - | - |
| Volume Contract Non-Renewal | - | - |
| Volume Closed All - as of Current Month = 1,319 | ||
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 | August 2020 |
|---|---|
| New gTLD | |
| Fraudulent, deceptive practices | 5 |
| Other | 1 |
| Pharming, Phishing | 1 |
| Trademark or Copyright Infringement | 1 |
| New gTLD Total | 8 |
| Legacy gTLD | |
| N/A1 | 78 |
| Counterfeiting | 3 |
| Counterfeiting | Fraudulent, deceptive practices | 1 |
| Fraudulent, deceptive practices | 39 |
| Fraudulent, deceptive practices | Registrar Abuse contact | 1 |
| Malware, Botnet | Pharming, Phishing | 1 |
| Other | 17 |
| Pharmaceuticals | 4 |
| Pharming, Phishing | 12 |
| Registrar Abuse contact | 9 |
| Spam | 7 |
| Spam | Registrar Abuse contact | 1 |
| Trademark or Copyright Infringement | 4 |
| Trademark or Copyright Infringement | Pharmaceuticals | 1 |
| Legacy gTLD Total | 178 |
| Not Specified2 | |
| N/A1 | 12 |
| Not Specified Total | 12 |
| Details on Abuse Complaints Total | 198 |
| Details on Transfer Complaints | August 2020 |
|---|---|
| New gTLD | |
| N/A1 | 3 |
| Transfer | 7 |
| New gTLD Total | 10 |
| Legacy gTLD | |
| N/A1 | 110 |
| COR | 5 |
| Transfer | 142 |
| Transfer | COR | 1 |
| Transfer | Unauthorized Transfer | 1 |
| Unauthorized COR | 7 |
| Unauthorized Transfer | 21 |
| Unauthorized Transfer | Unauthorized COR | 2 |
| Legacy gTLD Total | 289 |
| Not Specified2 | |
| N/A1 | 38 |
| Not Specified Total | 38 |
| Details on Transfer Complaints Total | 337 |
| Details on WHOIS Inaccuracy Complaints | August 2020 |
|---|---|
| New gTLD | |
| N/A1 | 26 |
| New gTLD Total | 26 |
| Legacy gTLD | |
| NA 1 | 393 |
| Identity | 2 |
| Operability - WHOIS data inaccuracy | 35 |
| Syntax | Operability - Whois data inaccuracy | 1 |
| Legacy gTLD Total | 431 |
| Not Specified2 | |
| N/A1 | 65 |
| Not Specified Total | 65 |
| Details on WHOIS Inaccuracy Complaints Total | 522 |
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 | August 2020 |
|---|---|---|
| Health and Fitness | Domain Deletion | 1 |
| Transfer | 1 | |
| Intellectual Property | Customer Service | 3 |
| Domain Renewal | 1 | |
| Transfer | 1 | |
| WHOIS Inaccuracy | 9 | |
| Professional Services | WHOIS Inaccuracy | 1 |
| Total | 17 |
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 | 23 |
"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 August 2020
| Temp Spec-related Requirements | 1st Inquiry/Notice | 2nd Inquiry/Notice | 3rd Inquiry/Notice | Total in Process | Closed | Resolved Code |
|---|---|---|---|---|---|---|
| Third Party Access | 0 | 1 | 0 | 7 | 0 | |
| Consent to Display | 1 | 1 | 0 | 1 | 0 | |
| RDDS | 3 | 2 | 0 | 14 | 6 | The registrar corrected its noncompliance. |
Numbers above reflect the notifications sent and closed within the month. In addition, the 'total in process' reflects the number of notifications pending during the month, which account for those in 1st, 2nd, or 3rd Inquiry/Notice status, including those for which Compliance sent communications in between notifications 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.
- RDDS notifications that Compliance sent in a prior month were closed in August.
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).
August 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.
August 2020 Registrar Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 195 |
| Out of Scope | 1123 |
| ICANN Issue | 1 |
| Registrar Closed Complaints Total | 1319 |
August 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. | 20 |
| The registrar demonstrated compliance. | 1 | |
| The registrar responded to the abuse report. | 11 | |
| Data Escrow | The registrar completed its data escrow deposit. | 11 |
| The registrar's data escrow file content issue is resolved. | 1 | |
| Domain Deletion | The domain is no longer suspended. | 3 |
| The registrar restored the domain. | 1 | |
| 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). | 12 |
| Domain Renewal | The domain has been renewed with the same registrant. | 2 |
| The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements. | 6 | |
| The registrar demonstrated compliance. | 1 | |
| Fees | The registrar paid its ICANN fees. | 2 |
| Registrar Other | The registrar corrected its noncompliance. | 7 |
| Transfer | The registrar corrected its noncompliance. | 2 |
| The registrar demonstrated compliance with its contractual requirements. | 4 | |
| 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. | 5 | |
| 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 has been completed. | 25 | |
| The transfer was denied because of a court order received by the registrar. | 1 | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | The registrar corrected its noncompliance. | 7 |
| The registrar locked a domain subject to a Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding. | 4 | |
| WHOIS Accuracy Reporting System (WHOIS ARS) | The domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint. | 1 |
| WHOIS Inaccuracy | The domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint. | 46 |
| The registrar corrected its noncompliance. | 5 | |
| The registrar demonstrated compliance. | 1 | |
| The registrar verified the domain's WHOIS information is correct. | 3 | |
| The WHOIS data has been updated. | 6 | |
| WHOIS Unavailable | The registrar's WHOIS service was restored. | 3 |
| Resolved Category Total | 195 |
Out of Scope
| 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 ICANN does not process complaints regarding website content. | 3 | |
| 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. | 3 | |
| 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 about a private dispute that does not implicate ICANN's contractual authority. | 2 | |
| 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. | 11 | |
| 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. | 68 | |
| The complaint is out of scope because the domain is not registered. | 1 | |
| The complaint is out of scope because there is no evidence of an abuse report with the registrar. | 1 | |
| 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. | 8 | |
| 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. | 22 | |
| 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 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. | 2 | |
| 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. | 6 | |
| Domain Name System Security Extensions (DNSSEC), Internationalized Domain Names (IDN), Internet Protocol Version 6 (IPv6) | 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. | 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 it is incomplete or broad. | 1 | |
| 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. | 5 | |
| 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. | 12 | |
| The complaint is out of scope because the domain is not registered. | 1 | |
| The complaint is out of scope because there is no evidence of an abuse report with the registrar. | 1 | |
| Domain Renewal | 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. | 67 | |
| Privacy/Proxy | The complaint is out of scope because it is regarding a country-code top-level domain. | 2 |
| 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. | 1 | |
| 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 regarding a country-code top-level domain. | 2 |
| The complaint is out of scope because the complainant did not provide the requested information. | 32 | |
| Registrar Other | The complaint is out of scope because the registrar voluntarily terminated its ICANN accreditation. | 1 |
| Transfer | The complaint is out of scope because it is a duplicate of an open complaint. | 49 |
| 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. | 37 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 261 | |
| 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 domain is not registered. | 3 | |
| The complaint is out of scope because the unauthorized transfer was due to hijacking. | 3 | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | 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 regarding a country-code top-level domain. | 1 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 7 | |
| The complaint is out of scope because the domain is not registered. | 1 | |
| 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 the complainant did not provide the requested information. | 1 | |
| WHOIS Inaccuracy | 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. | 54 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 62 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 289 | |
| The complaint is out of scope because the domain is not registered. | 14 | |
| WHOIS Service Level Agreements | 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. | 1 | |
| WHOIS Unavailable | 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. | 1 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 4 | |
| The complaint is out of scope because the domain is not registered. | 1 | |
| Out of Scope Category Total | 1123 |
ICANN Issue
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Domain Renewal | The matter has been withdrawn due to an ICANN issue. | 1 |
| ICANN Issue Category Total | 1 |
Registries
Registry Complaint Volume & Distribution
| Complaint Type | August 2020 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Abuse Contact Data | 6 | 5 |
| Bulk Registration Data Access | - | - |
| Bulk Zone File Access (ZFA) | 1 | - |
| Code Of Conduct | 2 | 2 |
| Monthly Report | 14 | - |
| Registration Restrictions Dispute Resolution Procedure | 2 | 2 |
| Registry Data Escrow | 56 | - |
| Registry Fees | 1 | - |
| Registry Other | 8 | 3 |
| Reserved Names/Controlled Interruption | - | 2 |
| Service Level Agreement | 4 | 2 |
| Uniform Rapid Suspension (URS) | 1 | - |
| Zone File Access | 70 | 46 |
| Grand Total | 165 | 62 |
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
| August 2020 | Quantity Sent | Process Turnaround Time |
|---|---|---|
| Volume 1st Notice Sent | 54 | 5.5 |
| Volume 2nd Notice Sent | 43 | 6.0 |
| Volume 3rd Notice Sent | 1 | - |
| Volume Breach | - | 606 |
| Volume Suspension | - | - |
| Volume Termination | - | - |
| Volume Contract Non-Renewal | - | - |
| Volume Closed All - as of Current Month = 116 | ||
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 | August 2020 |
|---|---|---|
| Financial | Registry Data Escrow | 2 |
| Zone File Access | 2 | |
| Intellectual Property | Code Of Conduct | 1 |
| Monthly Report | 1 | |
| Registry Data Escrow | 2 | |
| Professional Services | Zone File Access | 3 |
| Total | 11 |
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 August 2020
| Temp Spec-related Requirements | 1st Inquiry/Notice | 2nd Inquiry/Notice | 3rd Inquiry/Notice | Closed | Resolved Code |
|---|---|---|---|---|---|
| Third Pary Access | - | - | - | - | - |
| RDDS | - | - | - | - | - |
August 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.
August 2020 Registry Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 75 |
| Out of Scope | 41 |
| ICANN Issue | - |
| Registry Closed Complaints Total | 116 |
August 2020 Registry Closed Complaints Detail by Category and by Complaint Type
Resolved
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Bulk Registration Data Access | The registry corrected its noncompliance. | 7 |
| Bulk Zone File Access (ZFA) | The registry corrected its noncompliance. | 2 |
| Registry Fees | The registry operator's Registry Agreement (RA) was terminated. | 1 |
| Registry Other | The registry corrected its noncompliance. | 2 |
| Zone File Access | The registry demonstrated compliance. | 45 |
| The request for zone file access was already approved by the registry operator at the time of processing the complaint. | 18 | |
| Resolved Category Total | 75 |
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. | 4 |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 1 | |
| Code Of Conduct | 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 registry voluntarily terminated. | 1 | |
| 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 a closed complaint. | 2 |
| The complaint is out of scope because the complainant did not provide the requested information. | 1 | |
| Reserved Names/Controlled Interruption | The complaint is out of scope because the complainant did not provide the requested information. | 2 |
| Service Level Agreement | The complaint is out of scope because it is a duplicate of an open complaint. | 1 |
| The complaint is out of scope because the complainant did not provide the requested information. | 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. | 18 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 1 | |
| Out of Scope Category Total | 116 |
Complaint Volume & Closure Rate
Volume Trend
| Aug-19 | Sep-19 | Oct-19 | Nov-19 | Dec-19 | Jan-20 | Feb-20 | Mar-20 | Apr-20 | May-20 | Jun-20 | Jul-20 | Aug-20 |
| 1589 | 1616 | 1702 | 1580 | 2579 | 1547 | 1360 | 1747 | 1639 | 1584 | 1362 | 1613 | 1486 |
Total Volume
| Counts | July 2020 | August 2020 |
|---|---|---|
| Total New | 1,613 | 1,486 |
| Total Closed | 1,420 | 1,435 |
Closure Rates
| Stage | July 2020 | August 2020 |
|---|---|---|
| Received All Target ≥ 55% | 53% | 60% |
| Current Month | 36% | 47% |
| Before 1st Inquiry / Notice | 46% | 52% |
| Before 2nd Inquiry / Notice | 6% | 6% |
| Before 3rd Inquiry / Notice | 1% | 1% |
ICANN Staff Average Turnaround Time
| Measures | July 2020 | August 2020 |
|---|---|---|
| Open to 1st Inquiry / Notice | 1.7 | 3.0 |
| 2nd WIP | 7.3 | 10 |
| 3rd WIP | 34.1 | 8.0 |
| Formal Notices | - | 1.0 |
Contractual Compliance Overall Process Turnaround Time
| Measures | July 2020 | August 2020 |
|---|---|---|
| Received to Closed | 28.0 | 28.2 |
Note: Average Turnaround Time is shown in business days.