ICANN Contractual Compliance Dashboard for January 2021
ICANN provides a monthly dashboard summarizing contractual compliance complaints activity for the month. These monthly metrics show the complaint volume as they advance through the overall contractual compliance Informal & Formal process. Learn more about this dashboard report »
Registrars
Registrar Complaint Volume & Distribution
| Complaint Type | January 2021 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Abuse | 245 | 237 |
| Consent To Display Registration Data | 2 | - |
| Disclosure of gTLD Registration Data | 18 | 8 |
| Domain Renewal/Redemption | 152 | 127 |
| Domain Suspension | 20 | 22 |
| Generic Registrar | 81 | 38 |
| Privacy/Proxy | 4 | - |
| Registrar Data Escrow | 29 | - |
| Registrar Fees | 3 | - |
| Registration Data (service down) | 10 | 10 |
| Registration Data Inaccuracy | 80 | 67 |
| Transfer | 1,358 | 474 |
| Uniform Domain-Name Dispute-Resolution (UDRP) | 2 | 10 |
| Total | 2,004 | 993 |
- 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
| January 2021 | Quantity Sent |
|---|---|
| Volume 1st Inquiry/Notice Sent | 214 |
| Volume 2nd Inquiry/Notice Sent | 129 |
| Volume 3rd Inquiry/Notice Sent | 89 |
| Escalated Notice | - |
| Volume Breach | 1 |
| Volume Suspension | - |
| Volume Termination | - |
| Volume Contract Non-Renewal | - |
| Volume Closed All - as of Current Month = 1074 | |
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 | 113 |
| Malware, botnet | 31 |
| Spam | 58 |
| Counterfeiting | 40 |
| Fraudulent, deceptive practices | 147 |
| Pharmaceutical | 18 |
| Trademark or copyright infringement | 72 |
| Abuse contact / procedures information | 52 |
| Other | 47 |
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 | January 2021 |
|---|---|---|
| Regulated (Safeguards 1-3)::Children | Transfer | 1 |
| Regulated (Safeguards 1-3)::Intellectual Property | Abuse | 1 |
| Regulated (Safeguards 1-3)::Intellectual Property | Consent To Display Registration Data | 1 |
| Regulated (Safeguards 1-3)::Intellectual Property | Domain Suspension | 1 |
| Total | 4 |
Registrar Complaints Processed in January 2021 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 | 11 | 4 | Requested evidence not provided (4) | - | - | 3 |
| LEA, Consumer Protection, Government or Data Protection Agency | 1 | - | - | - | - | ||
| Non-Governmental Org | - | 1 | Requested evidence not provided (1) | - | - | - | |
| Information Security Researcher | - | 1 | Requested evidence not provided (1) | - | - | - | |
| Registrant - Current | 3 | 3 | Requested evidence not provided (2) ccTLD (1) | - | - | - | |
| Registrant - Former | 1 | 1 | Duplicate complaint (closed) (1) | - | - | - | |
| Registrar | - | 1 | Requested evidence not provided (1) | - | - | - | |
| Other | 1 | - | - | - | - | ||
| Reseller | 2 | - | - | - | - | ||
| Consent To Display Registration Data | |||||||
| Other | 1 | - | - | - | - | ||
| Registrant - Current | 1 | - | 1 | - | 1 | ||
| gTLD Registration Data - RDDS | |||||||
| Generic Registrar | Other | - | - | - | 1 | 1 | |
| Generic Registrar | ICANN Compliance | 3 | - | 3 | - | 6 | |
| Registration Data (service down) | Information Security Researcher | - | 1 | Requested evidence not provided (1) | - | - | - |
| Registration Data Inaccuracy | Other | - | 1 | Requested evidence not provided (1) | - | - | - |
| Legacy Ticketing System: | |||||||
| Third Party Access | - | - | - | - | 7 | ||
| RDDS | - | - | - | - | 6 | ||
| Total | 24 | 13 | 4 | 1 | 24 | ||
*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
*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
*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 ensure it was providing full Registration Data to UDRP providers upon notification of a complaint per Section 1.1 of Appendix E.
- 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).
January 2021 Registrar Closed Complaints by Closure Code
This report presents the number of closed complaints for registrars by closure code. When a complaint is closed, a description is selected which best describes the resolution of the complaint. The codes are categorized into three groups - Resolved, Out of Scope and ICANN Issue.
- Resolved = the reporter's complaint has been resolved or the contracted party has reviewed the complaint, responded to ICANN and/or demonstrated compliance.
- Out of Scope = the complaint cannot be addressed by ICANN because it is invalid or out of scope of ICANN's agreements/policies; or does not meet the minimum threshold for processing.
- ICANN Issue = the complaint should not have been sent to contracted party due to ICANN error; or internal ICANN process needs to be completed before the Compliance process can continue.
January 2021 Registrar Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 152 |
| Out of Scope | 922 |
| ICANN Issue | - |
| Registrar Closed Complaints Total | 1074 |
January 2021 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. | 31 |
| The registrar responded to the abuse report. | 2 | |
| Domain Renewal/Redemption | The domain has been renewed with the same registrant. | 3 |
| The registrar corrected its Expired Registration Recovery Policy (ERRP) noncompliance. | 2 | |
| The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements. | 1 | |
| The registrar demonstrated compliance. | 1 | |
| Domain Suspension | The domain is no longer suspended. | 12 |
| Generic Registrar | The domain is suspended and suspension is a reasonable response to the abuse report. | 1 |
| The registrar corrected its noncompliance. | 2 | |
| 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. | 5 | |
| Registration Data Inaccuracy | The domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint. | 7 |
| The registrar corrected its noncompliance. | 3 | |
| The registrar verified the domain's WHOIS information is correct. | 1 | |
| The registry demonstrated compliance. | 1 | |
| The WHOIS data has been updated. | 4 | |
| Transfer | The registrar corrected its noncompliance. | 1 |
| The registrar demonstrated compliance with its contractual 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. | 11 | |
| The transfer has been completed. | 52 | |
| The transfer was denied because of a court order received by the registrar. | 1 | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | The registrar demonstrated compliance with the Uniform Domain Name Dispute Resolution Policy (UDRP) requirements. | 1 |
| Resolved Category Total | 152 |
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. | 14 |
| 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 about a private dispute that does not implicate ICANN's contractual authority. | 6 | |
| The complaint is out of scope because it is incomplete or broad. | 2 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 21 | |
| 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. | 86 | |
| 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. | 73 | |
| Disclosure of gTLD Registration Data | The complaint is out of scope because the complainant did not provide the requested information. | 8 |
| Domain Renewal/Redemption | The complaint is out of scope because it is a duplicate of a closed complaint. | 2 |
| The complaint is out of scope because it is a duplicate of an open complaint. | 28 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 36 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 59 | |
| Domain Suspension | 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. | 7 | |
| Generic Registrar | 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. | 6 | |
| 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. | 22 | |
| Registrar Fees | The complaint is out of scope because ICANN terminated the registrar's accreditation. | 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. | 9 | |
| Registration Data Inaccuracy | The complaint is out of scope because the complainant did not provide the requested information. | 65 |
| Transfer | 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 a closed complaint. | 6 | |
| The complaint is out of scope because it is a duplicate of an open complaint. | 90 | |
| 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. | 167 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 180 | |
| The complaint is out of scope because the complainant is not the transfer contact for the domain. | 1 | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | 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 regarding a country-code top-level domain. | 1 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 2 | |
| The complaint is out of scope because there is no Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding. | 4 | |
| Out of Scope Category Total | 922 |
Registries
Registry Complaint Volume & Distribution
| Complaint Type | January 2021 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Abuse Contact Data | 8 | - |
| Code of Conduct | 2 | - |
| Generic Registry | 4 | - |
| Registry Data Escrow | 16 | - |
| Registry Fees | 1 | - |
| Service Level Agreement Alerts | 1 | - |
| Zone File Access | 59 | 70 |
| Total | 91 | 70 |
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
| January 2021 | Quantity Sent |
|---|---|
| Volume 1st Inquiry/Notice Sent | 55 |
| Volume 2nd Inquiry/Notice Sent | - |
| Volume 3rd Inquiry/Notice Sent | - |
| Escalated Notice | - |
| Volume Breach | - |
| Volume Termination | - |
| Volume Contract Non-Renewal | - |
| Volume Closed All - as of Current Month = 78 | |
Note: “Quantity Sent” represents activity which occurred during the reporting period and can include complaints received in a prior period.
Registry Additional Information on Complaints Related to GAC Category 1 Safeguards
| Details on GAC Category 1 Type | Complaint Type | January 2021 |
|---|---|---|
| Highly Regulated (Safeguards 1-8)::Charity | Zone File Access | 1 |
| Regulated (Safeguards 1-3)::Intellectual Property | Zone File Access | 1 |
| Total | 2 |
January 2021 Registry Closed Complaints by Closure Code
This report presents the number of closed complaints for registries by closure code. When a complaint is closed, a description is selected which best describes the resolution of the complaint. The codes are categorized into three groups - Resolved, Out of Scope and ICANN Issue.
- Resolved = the reporter's complaint has been resolved or the contracted party has reviewed the complaint, responded to ICANN and/or demonstrated compliance.
- Out of Scope = the complaint cannot be addressed by ICANN because it is invalid or out of scope of ICANN's agreements/policies; or does not meet the minimum threshold for processing.
- ICANN Issue = the complaint should not have been sent to contracted party due to ICANN error; or internal ICANN process needs to be completed before the Compliance process can continue.
January 2021 Registry Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 44 |
| Out of Scope | 34 |
| ICANN Issue | - |
| Registry Closed Complaints Total | 78 |
January 2021 Registry Closed Complaints Detail by Category and by Complaint Type
Resolved
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Registry Data Escrow | ICANN received the required registry data escrow notification. | 1 |
| Service Level Agreement Alerts | The registry corrected its noncompliance. | 6 |
| Zone File Access | The registry corrected its noncompliance. | 2 |
| The registry operator's Registry Agreement (RA) was terminated. | 1 | |
| The request for zone file access was already approved by the registry operator at the time of processing the complaint. | 34 | |
| Resolved Category Total | 44 |
Out of Scope
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Registry Data Escrow | The complaint is out of scope because the registry voluntarily terminated. | 1 |
| Zone File Access | 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. | 24 | |
| The complaint is out of scope because it is incomplete or broad. | 6 | |
| Out of Scope Category Total | 34 |
Complaint Volume & Closure Rate
Volume Trend
| Jan-20 | Feb-20 | Mar-20 | Apr-20 | May-20 | Jun-20 | Jul-20 | Aug-20 | Sep-20 | Oct-20 | Nov-20 | Dec-20 | Jan-21 |
| 1547 | 1360 | 1747 | 1639 | 1584 | 1362 | 1613 | 1486 | 1205 | 1111 | 1217 | 2016 | 2095 |
Total Volume
| Counts | December 2020 | January 2021 |
|---|---|---|
| Total New | 2,016 | 2,095 |
| Total Closed | 695 | 1,152 |