ICANN Contractual Compliance Dashboard for March 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 March 2023 Closed before 1st
Inquiry / Notice
Abuse676587
Consent To Display Registration Data33
Disclosure of gTLD Registration Data88
Domain Renewal/Redemption8474
Domain Suspension1721
Generic Registrar7374
Privacy/Proxy95
Registrar Data Escrow112112
Registration Data (service down)715
Registration Data Inaccuracy9857
Transfer138120
Uniform Domain-Name Dispute-Resolution (UDRP)95
REGISTRAR Total1,2341,081
  • 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

March 2023 Quantity Sent
Volume 1st Inquiry/Notice Sent219
Volume 2nd Inquiry/Notice Sent51
Volume 3rd Inquiry/Notice Sent18
Escalated Notice-
Volume Breach-
Volume Suspension-
Volume Termination-
Volume Contract Non-Renewal-
 
Volume Closed All - as of Current Month = 1265

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, phishing444
Malware, botnet100
Spam340
Counterfeiting112
Fraudulent, deceptive practices328
Pharmaceutical79
Trademark or copyright infringement204
Abuse contact / procedures information121
Other91

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 March 2023
Regulated (Safeguards 1-3)::Children;Regulated (Safeguards 1-3)::Intellectual PropertyRegistration Data Inaccuracy1
Regulated (Safeguards 1-3)::FinancialAbuse1
Regulated (Safeguards 1-3)::Generic Geographic TermsTransfer1
Regulated (Safeguards 1-3)::Intellectual PropertyAbuse1
Regulated (Safeguards 1-3)::Intellectual PropertyDomain Renewal/Redemption1
Regulated (Safeguards 1-3)::Intellectual PropertyTransfer3
Regulated (Safeguards 1-3)::Professional ServicesAbuse1
Total9

Registrar Complaints Processed in March 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 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 Protection74Requested evidence not provided (3)
Duplicate complaint (open) (1)
51-28The registrar demonstrated compliance; Access to non-public Registration Data denied (2)
Authorized Representative of Registrant-1Requested evidence not provided (1)-----
Registrant - Former----1-1
LEA, Consumer Protection, Government or Data Protection Agency-1Requested evidence not provided (1)11--1
UDRP/URS - Complainant-1Private dispute (1)-----
Other11ccTLD (1)1--21The registrar demonstrated compliance. (2)
Other Complaint Types also including disclosure requests for gTLD Registration Data:
AbuseLEA, Consumer Protection, Government or Data Protection Agency------1
Uniform Domain-Name Dispute-Resolution (UDRP)UDRP/URS - Provider11Requested evidence not provided (1)---1-The registrar corrected its noncompliance. (1)
Consent To Display Registration DataRegistrant - Current22Requested evidence not provided (1)
ccTLD (1)
-----
Other1------
Authorized Representative of Registrant-1Requested evidence not provided (1)-----
gTLD Registration Data - RDDS
Generic RegistrarICANN Compliance------2
Total1212721514

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

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

March 2023 Registrar Closed Complaints Summary

Closure Code Category # of Complaints
Resolved314
Out of Scope951
ICANN Issue-
Registrar Closed Complaints Total1265

March 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.49
The registrar demonstrated compliance.3
The registrar documented a valid non-action in response to the abuse report.4
The registrar responded to the abuse report.39
The registrar's abuse contact information was already published.1
Disclosure of gTLD Registration DataThe registrar demonstrated compliance.4
Domain Renewal/RedemptionThe registrar corrected its Expired Registration Recovery Policy (ERRP) noncompliance.1
The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements.5
Domain SuspensionThe domain is no longer suspended.5
Generic RegistrarThe registrar demonstrated compliance.2
The registrar submitted its annual compliance certificate.5
The registrar's annual compliance certificate has been corrected.2
Registrar Data EscrowThe registrar completed its data escrow deposit.120
The registrar's data escrow file content issue is resolved.1
Registration Data (service down)The registrar demonstrated compliance.1
Registration Data InaccuracyThe domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint.26
The registrar verified the domain's WHOIS information is correct.1
The WHOIS data has been updated.17
TransferThe registrar corrected its noncompliance.2
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 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.1
The transfer cannot be completed due to lack of payment for the prior or current registration period.1
The transfer cannot be completed due to the change of registrant lock.1
The transfer has been completed.13
Uniform Domain-Name Dispute-Resolution (UDRP)The registrar corrected its noncompliance.2
The registrar demonstrated compliance.2
Resolved Category Total314

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.3
The complaint is out of scope because ICANN does not process complaints regarding website content.10
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.9
The complaint is out of scope because it is about a private dispute that does not implicate ICANN's contractual authority.5
The complaint is out of scope because it is about a registrar that is not within 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.3
The complaint is out of scope because it is incomplete or broad.9
The complaint is out of scope because it is regarding a country-code top-level domain.58
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.120
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.338
Consent To Display Registration DataThe 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
Disclosure of gTLD Registration DataThe 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.5
Domain Renewal/RedemptionThe 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.8
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.57
The complaint is out of scope because the domain is not registered.1
Domain SuspensionThe 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.13
Generic RegistrarThe 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.4
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.61
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.4
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 ICANN is not a registrar.2
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 regarding a country-code top-level domain.4
The complaint is out of scope because the complainant did not provide the requested information.7
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 a duplicate of an open complaint.4
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.8
The complaint is out of scope because the complainant did not provide the requested information.38
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.10
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.8
The complaint is out of scope because the complainant did not provide the requested information.92
The complaint is out of scope because the complainant is not the domain registrant or the registrant's designated agent for purposes of a change of registrant.1
The complaint is out of scope because the unauthorized transfer was due to hijacking.3
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.3
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.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.2
Out of Scope Category Total951

Registries

Registry Complaint Volume & Distribution

Complaint Type March 2023 Closed before 1st
Inquiry / Notice
Abuse Contact Data66
Code of Conduct31
Generic Registry45
Registry Data Escrow1223
Reserved Names24
Service Level Agreement Alerts21-
Zone File Access136
REGISTRY Total6145

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

March 2023 Quantity Sent
Volume 1st Inquiry/Notice Sent7
Volume 2nd Inquiry/Notice Sent10
Volume 3rd Inquiry/Notice Sent-
Escalated Notice5
Volume Breach-
Volume Termination-
Volume Contract Non-Renewal-
 
Volume Closed All - as of Current Month = 52

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 March 2023
---
Total-

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

March 2023 Registry Closed Complaints Summary

Closure Code Category # of Complaints
Resolved30
Out of Scope22
ICANN Issue-
Registry Closed Complaints Total52

March 2023 Registry Closed Complaints Detail by Category and by Complaint Type

Resolved

Complaint Types Closure Code Description # of Complaints
Generic RegistryThe registry corrected its noncompliance.2
Registry Data EscrowICANN received the required registry data escrow notification.24
Zone File AccessThe request for zone file access was already approved by the registry operator at the time of processing the complaint.4
Resolved Category Total30

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.6
Generic RegistryThe 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.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.1
Reserved NamesThe complaint is out of scope because the complainant did not provide the requested information.4
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 it is incomplete or broad.1
Code of ConductThe complaint is out of scope because it is not about an ICANN contracted party.1
Out of Scope Category Total22

Complaint Volume & Closure Rate

Volume Trend

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

Total Volume

Counts February 2023 March 2023
Total New9641295
Total Closed8971317