ICANN Contractual Compliance Dashboard for May 2022

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 May 2022 Closed before 1st
Inquiry / Notice
Abuse282224
Consent To Display Registration Data12
Disclosure of gTLD Registration Data64
Domain Renewal/Redemption5346
Domain Suspension1922
Generic Registrar4151
Privacy/Proxy33
Registrar Data Escrow124142
Registrar Fees7-
Registration Data (service down)67
Registration Data Inaccuracy9437
Transfer129102
Uniform Domain-Name Dispute-Resolution (UDRP)113
Total776643
  • 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

May 2022 Quantity Sent
Volume 1st Inquiry/Notice Sent168
Volume 2nd Inquiry/Notice Sent32
Volume 3rd Inquiry/Notice Sent9
Escalated Notice-
Volume Breach2
Volume Suspension-
Volume Termination-
Volume Contract Non-Renewal-
 
Volume Closed All - as of Current Month = 847

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, phishing126
Malware, botnet36
Spam57
Counterfeiting38
Fraudulent, deceptive practices157
Pharmaceutical12
Trademark or copyright infringement83
Abuse contact / procedures information40
Other52

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 May 2022
Regulated (Safeguards 1-3)::Intellectual PropertyAbuse2
Regulated (Safeguards 1-3)::Intellectual PropertyTransfer1
Total3

Registrar Complaints Processed in May 2022 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 3rd Inquiry/ Notice Closed Inquiry/Notice Total Inquiries/ Notices in process Closure reason(s) for Inquiries/Notices
Disclosure of gTLD Registration Data
IP Lawyer/Brand Protection11The complaint is out of scope (1)-11410The registrar demonstrated compliance; Access to non-public Registration denied (1)
The registrar corrected its noncompliance; Registration Data disclosed (1)
The registrar corrected its noncompliance; Request for access to non-public Registration Data incomplete (2)
Other33Requested evidence not provided (2)
The complaint is out of scope (1)
----1
Authorized Representative of Registrant1------
LEA, Consumer Protection, Government or Data Protection Agency1----1-The registrar corrected its noncompliance; Registration Data disclosed (1)
Other Complaint Types also including disclosure requests for gTLD Registration Data:
AbuseIP Lawyer/Brand Protection------1
Other11The complaint is out of scope (1)-----
Authorized Representative of Registrant------1
Uniform Domain-Name Dispute-Resolution (UDRP)UDRP/URS - Provider----23-Domain locked; Domain verified (3)
Consent To Display Registration DataRegistrant - Former12Requested evidence not provided (2)----1
gTLD Registration Data - RDDS
Generic RegistrarICANN Compliance1-1---6
Total97113820

*The following columns have been removed from the above table because they had no complaint counts for the reported month:

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

*Compliance processes Notices/Inquiries for disclosure of gTLD Registration Data to ensure compliance with Appendix A, Section 4.1 of the Temporary Specification for gTLD Registration Data. Notices/Inquiries may be closed upon a registrar correcting an area of non-compliance or demonstrating compliance, regardless of whether access to Registration Data is granted or denied.

*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 April 2020 available here: https://features.icann.org/compliance/dashboard/report-list

*Examples of how “the registrar corrected its noncompliance” include:

  • Registrar implemented changes to ensure it was providing reasonable access to non-public Registration Data per Section 4.1 of Appendix A.
  • Registrar responded to a request for access to non-public Registration Data and provided the requested Data or an explanation for denial.
  • 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 how “the registrar demonstrated compliance” include:

  • Registrar demonstrated that it previously reviewed and responded to request(s) for access to non-public Registration Data per the requirements in Section 4.1 of Appendix A.
  • Registrar demonstrated that it displays Registration Data in its RDDS pursuant to the requirements of the RAA and Sections 2 and 3 of Appendix A (e.g. registrar demonstrated that it obtained Consent from the registrant to display non-redacted Registration Data in the RDDS, otherwise subject to redaction requirements pursuant to Section 2.1).

May 2022 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.

May 2022 Registrar Closed Complaints Summary

Closure Code Category # of Complaints
Resolved356
Out of Scope491
ICANN Issue-
Registrar Closed Complaints Total847

May 2022 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.27
The registrar corrected its noncompliance.1
The registrar responded to the abuse report.21
Disclosure of gTLD Registration DataThe change of registrant is not authorized.1
The contracted party granted access to non-public registration data.1
The registrar corrected its noncompliance.3
The registrar demonstrated compliance.1
Domain Renewal/RedemptionThe domain has been renewed with the same registrant.2
The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements.6
Domain SuspensionThe domain was not suspended at the time the complaint was processed.2
The registrar's deletion of the domain was compliant.2
Generic RegistrarThe registrar corrected its noncompliance.3
The registrar demonstrated compliance.18
The registrar submitted its annual compliance certificate.7
Registrar Data EscrowThe registrar completed its data escrow deposit.155
Registrar FeesThe registrar paid its ICANN fees.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.43
The registrar demonstrated compliance.1
The WHOIS data has been updated.13
TransferThe change of registrant has been completed.1
The registrar corrected its noncompliance.2
The registrar demonstrated compliance with its contractual requirements.5
The registrar demonstrated compliance.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.2
The registrar's deletion of the domain was compliant.1
The transfer cannot be completed due to a dispute over the identity of the registrant or administrative contact.1
The transfer cannot be completed due to a transfer within the past 60 days.1
The transfer cannot be completed due to evidence of fraud.1
The transfer cannot be completed due to the change of registrant lock.1
The transfer has been completed.15
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.5
The registrar demonstrated compliance with the Uniform Domain Name Dispute Resolution Policy (UDRP) requirements.1
The registrar demonstrated compliance.6
The registrar locked a domain subject to a Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding.3
Resolved Category Total356

Out of Scope

Complaint Types Closure Code Description # of Complaints
AbuseThe 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
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.8
The complaint is out of scope because it is a duplicate of an open complaint.9
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 incomplete or broad.3
The complaint is out of scope because it is regarding a country-code top-level domain.26
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.48
The complaint is out of scope because there is no evidence of an abuse report with the registrar.114
Consent To Display Registration DataThe complaint is out of scope because the complainant did not provide the requested information.2
Disclosure of gTLD Registration DataThe 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.2
Domain Renewal/RedemptionThe 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 is not a registrar.1
The complaint is out of scope because ICANN terminated the registrar's accreditation.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.5
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.3
The complaint is out of scope because the complainant did not provide the requested information.31
Domain SuspensionThe complaint is out of scope because it is a duplicate of an open complaint.1
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.18
Generic RegistrarThe complaint is out of scope because customer service issues are outside of ICANN's contractual authority.3
The complaint is out of scope because ICANN terminated the registrar's accreditation.1
The complaint is out of scope because it is a duplicate of an open complaint.7
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.5
The complaint is out of scope because the complainant did not provide the requested information.28
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.6
Privacy/ProxyThe 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.2
Registrar Data EscrowThe 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 it contains offensive language.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.3
Registration Data InaccuracyThe 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.1
The complaint is out of scope because it is about information that does not exist in the domain's current WHOIS.1
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.29
TransferThe 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 about a private dispute that does not implicate ICANN's contractual authority.4
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.82
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 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 the complainant did not provide the requested information.2
Out of Scope Category Total491

Registries

Registry Complaint Volume & Distribution

Complaint Type May 2022 Closed before 1st
Inquiry / Notice
Abuse Contact Data43
Code of Conduct-2
Generic Registry61
Public Interest Commitments (PIC)2-
Registry Data Escrow3433
Registry Fees3-
Zone File Access3117
Total8056

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

May 2022 Quantity Sent
Volume 1st Inquiry/Notice Sent65
Volume 2nd Inquiry/Notice Sent28
Volume 3rd Inquiry/Notice Sent12
Escalated Notice-
Volume Breach-
Volume Termination-
Volume Contract Non-Renewal-
 
Volume Closed All - as of Current Month = 84

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 May 2022
Highly Regulated (Safeguards 1-8)::FinancialZone File Access1
Regulated (Safeguards 1-3)::Professional ServicesZone File Access2
Total3

May 2022 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.

May 2022 Registry Closed Complaints Summary

Closure Code Category # of Complaints
Resolved70
Out of Scope14
ICANN Issue-
Registry Closed Complaints Total84

May 2022 Registry Closed Complaints Detail by Category and by Complaint Type

Resolved

Complaint Types Closure Code Description # of Complaints
Registry Data EscrowICANN received the required registry data escrow notification.35
Zone File AccessThe registry demonstrated compliance.22
The request for zone file access was already approved by the registry operator at the time of processing the complaint.13
Resolved Category Total70

Out of Scope

Complaint Types Closure Code Description # of Complaints
Abuse Contact DataThe complaint is out of scope because there is no evidence of an abuse report with the registrar.3
Code of ConductThe 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.1
Generic RegistryThe complaint is out of scope because the complainant did not provide the requested information.1
Registry Data EscrowThe complaint is out of scope because it is a duplicate of an open complaint.1
Registry FeesThe complaint is out of scope because it is a duplicate of an open complaint.1
Zone File AccessThe complaint is out of scope because it is a duplicate of an open complaint.5
The complaint is out of scope because the complainant did not provide the requested information.1
Out of Scope Category Total14

Complaint Volume & Closure Rate

Volume Trend

May-21Jun-21Jul-21Aug-21Sep-21Oct-21Nov-21Dec-21Jan-22Feb-22Mar-22Apr-22May-22
348722071051149690010161285915891816205812401124

Total Volume

Counts April 2022 May 2022
Total New1,124856
Total Closed1,395931