ICANN Contractual Compliance Dashboard for September 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 | September 2020 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Abuse | 267 | 139 |
| Consent To Display Registration Data | 3 | 1 |
| Disclosure Of gTLD Registration Data | 10 | 3 |
| Domain Name System Security Extensions (DNSSEC), Internationalized Domain Names (IDN), Internet Protocol Version 6 (IPv6) | - | 6 |
| Domain Renewal/Redemption | 155 | 86 |
| Domain Suspension | 18 | 17 |
| Generic Registrar | 79 | 36 |
| Privacy/Proxy | 4 | 1 |
| Registrar Data Escrow | 4 | 1 |
| Registrar Fees | 4 | 1 |
| Registration Data (service down) | 6 | 7 |
| Registration Data Inaccuracy* | 113 | 212 |
| Transfer | 448 | 212 |
| Uniform Domain-Name Dispute-Resolution (UDRP) | 9 | 6 |
| WHOIS Service Level Agreements | - | 46 |
| Total | 1,120 | 774 |
* The complaint type “WHOIS Inaccuracy” has been renamed “Registration Data Inaccuracy”. All complaints processed by Compliance in this complaint type are now reported under Registration Data Inaccuracy.
* Some Complaint Types are from the legacy system.
* “Closed before 1st Inquiry/Notice” represents complaints closed during the reporting period and can include complaints received in a prior period.
Compliance Process Volume
| September 2020 | Quantity Sent |
|---|---|
| Volume 1st Inquiry/Notice Sent | 245 |
| Volume 2nd Inquiry/Notice Sent | 59 |
| Volume 3rd Inquiry/Notice Sent | 7 |
| Escalated Notice | - |
| Volume Breach | - |
| Volume Suspension | - |
| Volume Termination | - |
| Volume Contract Non-Renewal | - |
| Volume Closed All - as of Current Month = 978 | |
Note: “Quantity Sent” represents activity which occurred during the reporting period and can include complaints received in a prior period.
Registrar Abuse Complaint Type Detail
| Abusive Activity Alleged in Connection with the Domain Name(s) in the Complaints Received: | Number of Instances the Activity has been Reported |
|---|---|
| Pharming, phishing | 99 |
| Malware, botnet | 25 |
| Spam | 51 |
| Counterfeiting | 31 |
| Fraudulent, deceptive practices | 128 |
| Pharmaceutical | 13 |
| Trademark or copyright infringement | 73 |
| Abuse contact / procedures information | 41 |
| Other | 38 |
Note: Activities are selected by the complainant with the submission and are not determined by ICANN Contractual Compliance. One single complaint can include more than one activity; therefore, the sum of the activities above will not necessarily equal the total of Abuse complaints received within the month.
Registrar Additional Information on Complaints Related to GAC Category 1 Safeguards
| Details on GAC Category 1 Type | Complaint Type | September 2020 |
|---|---|---|
| Regulated (Safeguards 1-3)::Intellectual Property | Abuse | 1 |
| Transfer | 1 | |
| Regulated (Safeguards 1-3)::Professional Services | Abuse | 1 |
| Total | 3 |
Registrar Complaints Processed in September 2020 Related to Requirements Under the Temporary Specification for gTLD Registration Data
| Complaint Type | Reporter Type | Reporter Complaints received | Reporter Complaints closed before Notice/ Inquiry (out of scope) | Closure reason(s) for out of scope Reporter Complaints | 1st Inquiry/ Notice | 2nd Inquiry/ Notice | Total Inquiries/ Notices in process |
|---|---|---|---|---|---|---|---|
| Disclosure of gTLD Registration Data | IP Lawyer/Brand Protection | 4 | 1 | Requested evidence not provided (1) | 1 | 1 | 1 |
| LEA, Consumer Protection, Government or Data Protection Agency | 1 | - | - | - | - | ||
| Other | 3 | 3 | Requested evidence not provided (3) | - | - | - | |
| UDRP/URS Provider | 2 | - | 1 | - | 1 | ||
| Other Complaint Types also including disclosure requests for gTLD Registration Data: | |||||||
| Abuse | IP Lawyer/Brand Protection | 1 | - | - | - | - | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | UDRP/URS Provider | 1 | - | - | - | - | |
| Consent To Display Registration Data | Registrant - Current | 3 | 1 | ccTLD (1) | - | - | |
| gTLD Registration Data - RDDS | - | - | - | - | - | ||
| Legacy Ticketing System: | |||||||
| Third Party Access | - | - | - | - | 7 | ||
| Consent to Display | - | - | - | - | 1 | ||
| RDDS | - | - | - | - | 9 | ||
| Total | 15 | 5 | 2 | 1 | 19 |
*The following columns have been removed from the above table because they had no complaint counts for the reported month:
- 3rd Inquiry/Notice
- Escalated Notice
- Breach Notice
- Suspension Notice
- Termination Notice
- Closed Inquiry/Notice
- Closure reasons(s) for Inquiries/Notices
*In the table above, the number of Reporter Complaints received may not equal the total number of closed Reporter Complaints plus the number of Notices/Inquiries sent, for any of the following reasons:
- Compliance actions took place in different months. The table reflects activity per month. Compliance may send Inquiries, Notices or Closures in different months from which it received the related complaint. For example, Compliance may receive a Reporter Complaint in one month, which is closed or results in an Inquiry/Notice sent to a contracted party the following month. Further, new Reporter Complaints may be pending review and processing by Compliance and therefore, only reported as received in the reported month.
- The reporter misfiled the complaint. A reporter may submit a complaint using the form for Disclosure of gTLD Registration Data or Consent to Display, which after review, Compliance determines is within the scope of ICANN's contractual authority, but should be processed under a different complaint type.
- Compliance bundled multiple complaints into a single Inquiry/Notice. A single compliance Inquiry or Notice may be based on one or multiple Reporter Complaints received by compliance, or on Compliance’s own observations of areas of non-compliance.
*Reporter type refers to the capacity in which the reporter submitted the complaint, which is selected by the reporter at the time of submission and is not determined by Compliance.
*Out of scope complaints involving disclosure for gTLD Registration Data may include for example, requests for personal data of privacy or proxy registrant customers, requests for Registration Data that is available in the public Registration Data Directory Services (not redacted), or failure to provide evidence of request made to the contracted party.
*The 'total Inquiries/Notices in process' reflects the number pending during the month, which account for those in 1st, 2nd, or 3rd Inquiry/Notice status, including those for which Compliance may not have sent additional Inquiries or Notices due to ongoing remediation for example.
*For additional details of complaints processed in the legacy ticketing system, please refer to the Monthly Dashboard for May 2020 through August 2020 available here: https://features.icann.org/compliance/dashboard/report-list
September 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.
September 2020 Registrar Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 224 |
| Out of Scope | 753 |
| ICANN Issue | 1 |
| Registrar Closed Complaints Total | 978 |
September 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. | 21 |
| The registrar demonstrated compliance. | 3 | |
| The registrar documented a valid response to the abuse report. | 1 | |
| The registrar responded to the abuse report. | 20 | |
| Domain Renewal/Redemption | The domain has been renewed with the same registrant. | 4 |
| The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements. | 10 | |
| Domain Suspension | The domain is no longer suspended. | 5 |
| The registrar restored the domain. | 2 | |
| Generic Registrar | The registrar corrected its Expired Registration Recovery Policy (ERRP) noncompliance. | 1 |
| The registrar corrected its noncompliance. | 7 | |
| The registrar demonstrated compliance with the WHOIS accuracy requirements. | 1 | |
| The registrar's Registrar Information Specification form was completed. | 1 | |
| The WHOIS data has been updated. | 1 | |
| Registrar Data Escrow | The registrar completed its data escrow deposit. | 5 |
| Registrar Fees | The registrar paid its ICANN fees. | 1 |
| Registration Data (service down) | The registrar demonstrated compliance. | 1 |
| The registrar's WHOIS service was restored. | 2 | |
| Registration Data Inaccuracy | The domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint. | 58 |
| The registrar verified the domain's WHOIS information is correct. | 2 | |
| The WHOIS data has been updated. | 17 | |
| Transfer | The registrar corrected its noncompliance. | 2 |
| The registrar demonstrated compliance with its contractual requirements. | 14 | |
| The registrar demonstrated compliance with the change of registrant requirements. | 3 | |
| 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. | 1 | |
| The transfer cannot be completed due to evidence of fraud. | 3 | |
| The transfer cannot be completed due to lack of payment for the prior or current registration period. | 3 | |
| 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. | 2 | |
| The transfer has been completed. | 25 | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | 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. | 1 | |
| Resolved Category Total | 224 |
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. | 3 |
| 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. | 2 | |
| 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. | 4 | |
| 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. | 102 | |
| 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. | 3 | |
| Consent To Display Registration Data | The complaint is out of scope because it is regarding a country-code top-level domain. | 1 |
| Disclosure of gTLD Registration Data | The complaint is out of scope because the complainant did not provide the requested information. | 4 |
| Domain Renewal/Redemption | The complaint is out of scope because it is a duplicate of an open complaint. | 13 |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 1 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 20 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 50 | |
| Domain Suspension | 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 the complainant did not provide the requested information. | 9 | |
| Generic Registrar | 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 is not a registrar. | 1 | |
| 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 incomplete or broad. | 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 complainant did not provide the requested information. | 30 | |
| The complaint is out of scope because the registrar voluntarily terminated its ICANN accreditation. | 0 | |
| Privacy/Proxy | The complaint is out of scope because it is a duplicate of an open complaint. | 1 |
| Registration Data (service down) | 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 the complainant did not provide the requested information. | 5 | |
| Registration Data Inaccuracy | 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. | 4 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 9 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 193 | |
| The complaint is out of scope because the domain is not registered. | 2 | |
| 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. | 1 | |
| 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 about a private dispute that does not implicate ICANN's contractual authority. | 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. | 150 | |
| The complaint is out of scope because the complainant is not the transfer contact for the domain. | 6 | |
| 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. | 5 | |
| 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. | 2 |
| The complaint is out of scope because the complainant did not provide the requested information. | 4 | |
| WHOIS Service Level Agreements | 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 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. | 2 | |
| 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. | 2 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 30 | |
| 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 | |
| Out of Scope Category Total | 753 |
ICANN Issue
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Registrar Data Escrow | The matter has been withdrawn due to an ICANN issue. | 1 |
| ICANN Issue Category Total | 1 |
Registries
Registry Complaint Volume & Distribution
| Complaint Type | September 2020 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Abuse Contact Data | 7 | - |
| Bulk Zone File Access (ZFA) | 1 | - |
| Code of Conduct | 4 | 3 |
| Generic Registry | 4 | - |
| Monthly Reports | 1 | - |
| Public Interest Commitments (PIC) | 1 | - |
| Registry Data Escrow | 4 | - |
| Service Level Agreement Alerts | 28 | - |
| Service Level Agreement | - | 12 |
| Zone File Access | 35 | 44 |
| Total | 85 | 59 |
Note: Some Complaint Types are from the legacy system. ”Closed before 1st Inquiry/Notice” represents complaints closed during the reporting period and can include complaints received in a prior period.
Compliance Process Volume
| September 2020 | Quantity Sent |
|---|---|
| Volume 1st Inquiry/Notice Sent | 39 |
| Volume 2nd Inquiry/Notice Sent | 8 |
| Volume 3rd Inquiry/Notice Sent | 4 |
| Escalated Notice | - |
| Volume Breach | - |
| 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 | September 2020 |
|---|---|---|
| - | - | |
| Total | - |
September 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.
September 2020 Registry Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 54 |
| Out of Scope | 33 |
| ICANN Issue | 0 |
| Registry Closed Complaints Total | 87 |
September 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 Reports | The registry corrected its noncompliance. | 1 |
| The registry demonstrated compliance. | 1 | |
| Registry Data Escrow | ICANN received the required registry data escrow notification. | 1 |
| Registry Fees | The registry paid its ICANN fees. | 1 |
| Zone File Access | The registry demonstrated compliance. | 26 |
| The request for zone file access was already approved by the registry operator at the time of processing the complaint. | 23 | |
| Resolved Category Total | 54 |
Out of Scope
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Code of Conduct | 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. | 1 | |
| Service Level Agreement | 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 incomplete or broad. | 3 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 6 | |
| Zone File Access | The complaint is out of scope because it is a duplicate of an open complaint. | 16 |
| The complaint is out of scope because the complainant did not provide the requested information. | 2 | |
| Out of Scope Category Total | 33 |
Complaint Volume & Closure Rate
Volume Trend
| Sep-19 | Oct-19 | Nov-19 | Dec-19 | Jan-20 | Feb-20 | Mar-20 | Apr-20 | May-20 | Jun-20 | Jul-20 | Aug-20 | Sep-20 |
| 1616 | 1702 | 1580 | 2579 | 1547 | 1360 | 1747 | 1639 | 1584 | 1362 | 1613 | 1486 | 1205 |
Total Volume
| Counts | August 2020 | September 2020 |
|---|---|---|
| Total New | 1,486 | 1,205 |
| Total Closed | 1,435 | 1,065 |