ICANN Contractual Compliance Dashboard for February 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 February 2021 Closed before 1st
Inquiry / Notice
Abuse25157
Consent To Display Registration Data4-
Disclosure of gTLD Registration Data1814
Domain Renewal/Redemption16487
Domain Suspension2126
Generic Registrar6939
Privacy/Proxy7-
Registrar Data Escrow46-
Registration Data (service down)9-
Registration Data Inaccuracy9949
Transfer906442
Uniform Domain-Name Dispute-Resolution (UDRP)93
Total1,603717
  • 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

February 2021 Quantity Sent
Volume 1st Inquiry/Notice Sent332
Volume 2nd Inquiry/Notice Sent182
Volume 3rd Inquiry/Notice Sent144
Escalated Notice7
Volume Breach-
Volume Suspension-
Volume Termination1
Volume Contract Non-Renewal-
 
Volume Closed All - as of Current Month = 808

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, phishing109
Malware, botnet31
Spam55
Counterfeiting39
Fraudulent, deceptive practices147
Pharmaceutical11
Trademark or copyright infringement91
Abuse contact / procedures information45
Other34

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 February 2021
Regulated (Safeguards 1-3)::Intellectual PropertyAbuse1
Regulated (Safeguards 1-3)::Intellectual PropertyDomain Suspension1
Regulated (Safeguards 1-3)::Intellectual PropertyGeneric Registrar2
Regulated (Safeguards 1-3)::Intellectual PropertyPrivacy/Proxy1
Regulated (Safeguards 1-3)::Intellectual PropertyTransfer1
Total6

Registrar Complaints Processed in February 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 Closed Inquiry/Notice Total Inquiries/ Notices in process Closure reason(s) for Inquiries/Notices
Disclosure of gTLD Registration DataIP Lawyer/Brand Protection147Duplicate complaint (open) (1)
Requested evidence not provided (6)
82-9
Registrant - Current-2Requested evidence not provided (2)----
Registrant - Former-1Duplicate complaint (closed) (1)----
Other43Requested evidence not provided (3)----
Reseller-2Requested evidence not provided (1)
ccTLD (1)
----
ICANN Compliance-----2
Other Complaint Types also including disclosure requests for gTLD Registration Data:
AbuseIP Lawyer/Brand Protection--1--1
Consent To Display Registration Data
Authorized Representative1-----
Registrant - Current1----1
Registrant - Former2-----
gTLD Registration Data - RDDS
Registration Data InaccuracyOther-----1
Generic RegistrarICANN Compliance22Rr fixed issue (2)3127Registrar corrected its noncompliance (2)
Legacy Ticketing System:
Third Party Access-----7
RDDS----24Registrar corrected its noncompliance (1)
Registrar Terminated (1)
Total2417123432

*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

*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).

*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).

February 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.

February 2021 Registrar Closed Complaints Summary

Closure Code Category # of Complaints
Resolved101
Out of Scope707
ICANN Issue-
Registrar Closed Complaints Total808

February 2021 Registrar Closed Complaints Detail by Category and by Complaint Type

Resolved

Complaint Types Closure Code Description # of Complaints
AbuseThe domain is suspended and suspension is a reasonable response to the abuse report.9
The registrar responded to the abuse report.1
Domain Renewal/RedemptionThe domain has been renewed with the same registrant.2
The registrar corrected its noncompliance.1
The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements.1
Domain SuspensionThe domain is no longer suspended.9
The registrar's deletion of the domain was compliant.1
Generic RegistrarThe registrar corrected its noncompliance.4
Registrar Data EscrowThe registrar completed its data escrow deposit.1
The registrar's data escrow file content issue is resolved.1
Registration Data (service down)The registrar's WHOIS service was restored.1
Registration Data InaccuracyThe domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint.28
The registrar verified the domain's WHOIS information is correct.1
The WHOIS data has been updated.12
TransferThe registrar demonstrated compliance with its contractual requirements.1
The registrar demonstrated compliance.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.2
The transfer has been completed.23
Uniform Domain-Name Dispute-Resolution (UDRP)The registrar demonstrated compliance.1
Resolved Category Total101

Out of Scope

Complaint Types Closure Code Description # of Complaints
AbuseThe 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.5
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 it is regarding a country-code top-level domain.17
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.2
The complaint is out of scope because there is no evidence of an abuse report with the registrar.14
Disclosure of gTLD Registration DataThe 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.1
The complaint is out of scope because the complainant did not provide the requested information.12
Domain Renewal/RedemptionThe complaint is out of scope because it is a duplicate of an open complaint.23
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.23
The complaint is out of scope because the complainant did not provide the requested information.43
Domain SuspensionThe 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.1
The complaint is out of scope because the complainant did not provide the requested information.12
Generic RegistrarThe complaint is out of scope because ICANN terminated the registrar's accreditation.2
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.13
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.18
The complaint is out of scope because the registrar voluntarily terminated its ICANN accreditation.1
The complaint is out of scope because there is no evidence of an abuse report with the registrar.1
Registration Data InaccuracyThe complaint is out of scope because the complainant did not provide the requested information.46
TransferThe 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.81
The complaint is out of scope because it is regarding a country-code top-level domain.171
The complaint is out of scope because the complainant did not provide the requested information.184
The complaint is out of scope because the domain is not registered.1
The complaint is out of scope because the registrar voluntarily terminated its ICANN accreditation.1
Uniform Domain-Name Dispute-Resolution (UDRP)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
Out of Scope Category Total707

Registries

Registry Complaint Volume & Distribution

Complaint Type February 2021 Closed before 1st
Inquiry / Notice
Abuse Contact Data4-
Bulk Zone File Access (ZFA)1-
Code of Conduct3-
Generic Registry4-
Registry Data Escrow281-
Registry Fees2-
Reserved Names3-
Zone File Access2712
Total32512

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

February 2021 Quantity Sent
Volume 1st Inquiry/Notice Sent12
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 = 14

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 2021
Special: Potential for Cyber Bullying/Harassment (Safeguards 1-9)::Bullying/HarassmentZone File Access1
Total1

February 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.

February 2021 Registry Closed Complaints Summary

Closure Code Category # of Complaints
Resolved13
Out of Scope1
ICANN Issue-
Registry Closed Complaints Total14

February 2021 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
Registry FeesThe registry paid its ICANN fees.1
Zone File AccessThe request for zone file access was already approved by the registry operator at the time of processing the complaint.11
Resolved Category Total13

Out of Scope

Complaint Types Closure Code Description # of Complaints
Zone File AccessThe complaint is out of scope because it is a duplicate of an open complaint.1
Out of Scope Category Total1

Complaint Volume & Closure Rate

Volume Trend

Feb-20Mar-20Apr-20May-20Jun-20Jul-20Aug-20Sep-20Oct-20Nov-20Dec-20Jan-21Feb-21
1360174716391584136216131486120511111217201620951928

Total Volume

Counts January 2021 February 2021
Total New2,0951,928
Total Closed1,152822