ICANN Contractual Compliance Dashboard for May 2023

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 2023 Closed before 1st
Inquiry / Notice
Abuse439383
Consent To Display Registration Data24
Disclosure of gTLD Registration Data129
Domain Renewal/Redemption6754
Domain Suspension2232
Generic Registrar4752
Privacy/Proxy33
Registrar Data Escrow598629
Registrar Fees1-
Registration Data (service down)34
Registration Data Inaccuracy8723
Transfer11693
Uniform Domain-Name Dispute-Resolution (UDRP)83
REGISTRAR Total1,4051,289
  • 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 2023 Quantity Sent
Volume 1st Inquiry/Notice Sent229
Volume 2nd Inquiry/Notice Sent28
Volume 3rd Inquiry/Notice Sent11
Escalated Notice2
Volume Breach1
Volume Suspension-
Volume Termination-
Volume Contract Non-Renewal-
 
Volume Closed All - as of Current Month = 1528

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, phishing226
Malware, botnet65
Spam94
Counterfeiting70
Fraudulent, deceptive practices277
Pharmaceutical46
Trademark or copyright infringement173
Abuse contact / procedures information87
Other66

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 2023
Highly Regulated (Safeguards 1-8)::GamblingDomain Renewal/Redemption1
Regulated (Safeguards 1-3)::FinancialAbuse1
Regulated (Safeguards 1-3)::Intellectual PropertyAbuse1
Regulated (Safeguards 1-3)::Intellectual PropertyDomain Renewal/Redemption1
Total4

Registrar Complaints Processed in May 2023 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 Data
IP Lawyer/Brand Protection97The complaint is out of scope because the complainant did not provide the requested information (7)2-27The registrar demonstrated compliance; Access to non-public Registration Data denied (1)
The registrar corrected its noncompliance; Registration Data disclosed; (1)
Registrant - Former1---1-The registrar corrected its noncompliance; Access to non-public Registration Data denied (1)
LEA, Consumer Protection, Government or Data Protection Agency1-2121The registrar demonstrated compliance; Request for access to non-public Registration Data incomplete (1)
The registrar corrected its noncompliance; Registration Data disclosed (1)
UDRP/URS - Complainant--1-1-Access to non-public Registration Data denied; The registrar demonstrated compliance (1)
Information Security Researcher-1The complaint is out of scope because the complainant did not provide the requested information (1)----
Other11The complaint is out of scope because the complainant did not provide the requested information (1)----
Other Complaint Types also including disclosure requests for gTLD Registration Data:
AbuseLEA, Consumer Protection, Government or Data Protection Agency-----1
Other--1-1-The registrar demonstrated compliance; The registrar responded to abuse report (1)
Uniform Domain-Name Dispute-Resolution (UDRP)UDRP/URS - Provider----1-The registrar corrected its noncompliance (1)
Consent To Display Registration DataRegistrant - Current24The complaint is out of scope because the complainant did not provide the requested information (4)1-1-The registrar corrected its noncompliance (1)
gTLD Registration Data - RDDS
AbuseNon-Governmental Organization--1--1
Generic RegistrarIP Lawyer/Brand Protection1-1--1
ICANN Compliance-----1
Total151391912

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

*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 May 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 2023 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 2023 Registrar Closed Complaints Summary

Closure Code Category # of Complaints
Resolved902
Out of Scope626
ICANN Issue-
Registrar Closed Complaints Total1528

May 2023 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.67
The registrar demonstrated compliance.1
The registrar responded to the abuse report.36
AuditThe contracted party provided a timeline and action plan for addressing deficiencies.10
The contracted party provided clarification to clear initial finding(s).2
The contracted party remediated all deficiencies.3
Consent To Display Registration DataThe registrar corrected its noncompliance.1
Disclosure of gTLD Registration DataThe contracted party granted access to non-public registration data.2
The contracted party provided rationale for denying access to non-public registration data.2
The registrar demonstrated compliance.1
Domain Renewal/RedemptionThe domain has been renewed with the same registrant.2
The registrar corrected its Expired Registration Recovery Policy (ERRP) noncompliance.1
The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements.2
Domain SuspensionThe domain is no longer suspended.11
The registrar's deletion of the domain was compliant.1
Generic RegistrarThe registrar corrected its noncompliance.1
The registrar demonstrated compliance.1
The registrar submitted its annual compliance certificate.3
Registrar Data EscrowThe registrar completed its data escrow deposit.651
The registrar completed its initial data escrow deposit.1
The registrar's data escrow file content issue is resolved.3
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.30
The registrar corrected its noncompliance.1
The registrar verified the domain's WHOIS information is correct.2
The WHOIS data has been updated.32
TransferThe change of registrant is not authorized.1
The registrar corrected its noncompliance.1
The registrar demonstrated compliance with its contractual requirements.3
The registrar demonstrated compliance.6
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 cannot be completed due to evidence of fraud.2
The transfer has been completed.7
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.5
Resolved Category Total902

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.10
The complaint is out of scope because it contains offensive language.1
The complaint is out of scope because it is a duplicate of a closed complaint.4
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.4
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.2
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.65
The complaint is out of scope because spam is outside of ICANN's contractual authority.3
The complaint is out of scope because the complainant did not provide the requested information.98
The complaint is out of scope because the domain is not registered.14
The complaint is out of scope because there is no evidence of an abuse report with the registrar.150
Consent To Display Registration DataThe complaint is out of scope because the complainant did not provide the requested information.4
Disclosure of gTLD Registration DataThe complaint is out of scope because the complainant did not provide the requested information.9
Domain Renewal/RedemptionThe 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.2
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.3
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.38
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 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.3
The complaint is out of scope because the complainant did not provide the requested information.16
Generic RegistrarThe 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.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.29
The complaint is out of scope because there is no evidence of an abuse report with the registrar.11
Registration Data (service down)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 the complainant did not provide the requested information.3
Registration Data InaccuracyThe complaint is out of scope because it is regarding a country-code top-level domain.6
The complaint is out of scope because the complainant did not provide the requested information.14
TransferThe 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 terminated the registrar's accreditation.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 about a private dispute that does not implicate ICANN's contractual authority.2
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.8
The complaint is out of scope because the complainant did not provide the requested information.78
Uniform Domain-Name Dispute-Resolution (UDRP)The complaint is out of scope because the complainant did not provide the requested information.1
The complaint is out of scope because there is no Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding.1
Privacy/ProxyThe complaint is out of scope because ICANN does not process complaints regarding website content.1
The complaint is out of scope because the complainant did not provide the requested information.1
The complaint is out of scope because there is no evidence of an abuse report with the registrar.1
Out of Scope Category Total626

Registries

Registry Complaint Volume & Distribution

Complaint Type May 2023 Closed before 1st
Inquiry / Notice
Abuse Contact Data99
Code of Conduct1-
Generic Registry8-
Registry Data Escrow11159
Registry Fees1-
Reserved Names-2
Uniform Rapid Suspension (URS)1-
Zone File Access1815
REGISTRY Total14985

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 2023 Quantity Sent
Volume 1st Inquiry/Notice Sent82
Volume 2nd Inquiry/Notice Sent18
Volume 3rd Inquiry/Notice Sent5
Escalated Notice-
Volume Breach-
Volume Termination-
Volume Contract Non-Renewal-
 
Volume Closed All - as of Current Month = 103

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 2023
Regulated (Safeguards 1-3)::Children;Regulated (Safeguards 1-3)::Intellectual PropertyGeneric Registry2
Regulated (Safeguards 1-3)::Intellectual PropertyAbuse Contact Data1
Special: Potential for Cyber Bullying/Harassment (Safeguards 1-9)::Bullying/HarassmentGeneric Registry1
Total4

May 2023 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 2023 Registry Closed Complaints Summary

Closure Code Category # of Complaints
Resolved71
Out of Scope32
ICANN Issue-
Registry Closed Complaints Total103

May 2023 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.61
Zone File AccessThe request for zone file access was already approved by the registry operator at the time of processing the complaint.10
Resolved Category Total71

Out of Scope

Complaint Types Closure Code Description # of Complaints
Abuse Contact DataThe 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.1
The complaint is out of scope because there is no evidence of an abuse report with the registrar.6
Reserved NamesThe complaint is out of scope because the complainant did not provide the requested information.2
Zone File AccessThe complaint is out of scope because it is a duplicate of an open complaint.13
The complaint is out of scope because the complainant did not provide the requested information.8
Out of Scope Category Total32

Complaint Volume & Closure Rate

Volume Trend

May-22Jun-22Jul-22Aug-22Sep-22Oct-22Nov-22Dec-22Jan-23Feb-23Mar-23Apr-23May-23
856145994734909041198850929981964129516531554

Total Volume

Counts April 2023 May 2023
Total New16531554
Total Closed11891631