ICANN Contractual Compliance Dashboard for May 2025

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 2025 Closed before 1st
Inquiry / Notice
Consent To Display Registration Data20
Disclosure of gTLD Registration Data311
DNS Abuse and Other Types of Abuse600545
Domain Renewal/Redemption69105
Domain Suspension2524
Generic Registrar7036
Privacy/Proxy72
Registrar Data Escrow4833
Registrar Fees40
Registration Data (service down)92
Registration Data Inaccuracy4836
Transfer137116
Uniform Domain-Name Dispute-Resolution (UDRP)87
REGISTRAR Total1,030917
  • 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 2025 Quantity Sent
Volume 1st Inquiry/Notice Sent94
Volume 2nd Inquiry/Notice Sent17
Volume 3rd Inquiry/Notice Sent2
Escalated Notice9
Volume Breach1
Volume Suspension-
Volume Termination2
Volume Contract Non-Renewal-
Volume Closed All - as of Current Month = 1017

Note: “Quantity Sent” represents activity which occurred during the reporting period and can include complaints received in a prior period.

Registrar Additional Information on Complaints Related to GAC Category 1 Safeguards

Details on GAC Category 1 Type Complaint Type May 2025
Highly Regulated (Safeguards 1-8)::GamblingDNS Abuse and Other Types of Abuse1
Regulated (Safeguards 1-3)::Children;Regulated (Safeguards 1-3)::Intellectual PropertyRegistration Data Inaccuracy1
Regulated (Safeguards 1-3)::Generic Geographic TermsDNS Abuse and Other Types of Abuse1
Regulated (Safeguards 1-3)::Intellectual PropertyDNS Abuse and Other Types of Abuse17
Regulated (Safeguards 1-3)::Intellectual PropertyDomain Renewal/Redemption3
Regulated (Safeguards 1-3)::Intellectual PropertyTransfer1
Regulated (Safeguards 1-3)::Professional ServicesDomain Renewal/Redemption1
Special: Potential for Cyber Bullying/Harassment (Safeguards 1-9)::Bullying/HarassmentDomain Renewal/Redemption1
Special: Potential for Cyber Bullying/Harassment (Safeguards 1-9)::Bullying/HarassmentTransfer1
Total27

Registrar complaints processed in May 2025 related to requirements under the Interim Registration Data Policy for gTLDs:

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 Inquires/ Notices in process Closure reason(s) for Inquiries/Notices
Disclosure of gTLD Registration Data
IP Lawyer/Brand Protection-2The complaint is out of scope (2)--1-The registrar corrected its noncompliance.; Access to non-public Registration Data denied (1)
Information Security Researcher-1The complaint is out of scope (1)---
Registrant - Current---1-1
Other35The complaint is out of scope (5)----
Authorized Representative of Registrant-1The complaint is out of scope (1)----
LEA, Consumer Protection, Government or Data Protection Agency-1The complaint is out of scope (1)----
Registrant - Former-1The complaint is out of scope (1)----
Other Complaint Types also including disclosure requests for gTLD Registration Data:
------
Consent To Display Registration Data
Consent To Display Registration DataRegistrant - Current2-1-1-The registrar corrected its noncompliance.; The contracted party has displayed the contact information for which consent was provided (1)
gTLD Registration Data - RDDS
Registration Data (service down)ICANN Compliance--1111The registrar is now compliant. (1)
Other----2-The registrar is now compliant. (2)
Generic RegistrarICANN Compliance-----1
Non-Governmental Organization-----1
Total5112254

*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 disclosure requirements under the Interim Registration Data Policy for gTLDs. 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 August 2020 available here: https://features.icann.org/compliance/dashboard/report-list

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

  • Registrar implemented changes to its disclosure process(es) to ensure compliance with disclosure requirements under the Interim Registration Data Policy for gTLDs.
  • 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.
  • 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/disclosure of non-public registration data per the Interim Registration Data Policy for gTLDs.
  • Registrar demonstrated that it displays registration data in its RDDS pursuant to the requirements of the RAA and Interim Registration Data Policy for gTLDs (e.g. registrar demonstrated that it obtained Consent from the registrant to display personal registration data in the RDDS, otherwise subject to redaction requirements).

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

Closure Code Category # of Complaints
Resolved124
Out of Scope893
ICANN Issue-
Registrar Closed Complaints Total1017

May 2025 Registrar Closed Complaints Detail by Category and by Complaint Type

Resolved

Complaint Types Closure Code Description # of Complaints
Consent To Display Registration DataThe registrar corrected its noncompliance.1
Disclosure of gTLD Registration DataThe registrar corrected its noncompliance.2
DNS Abuse and Other Types of AbuseThe registrar demonstrated having reasonably and promptly investigated and appropriately responded to an abuse report.13
The registrar does not have actionable evidence to determine the domain name is being used for DNS Abuse.2
The registrar published the required abuse contact. This contact provides a confirmation receipt to any party submitting an abuse report.1
The registrar suspended or deactivated the domain name. This is a reasonable response to an abuse report.9
The registrar suspended/deactivated the domain name. This is an appropriate mitigation action to stop the use of the domain name for DNS Abuse.10
The registrar took appropriate mitigation action to disrupt the use of the domain name for DNS Abuse.1
Domain Renewal/RedemptionThe domain has been renewed with the same registrant.3
Domain SuspensionThe domain is no longer suspended.1
The domain was not suspended at the time the complaint was processed.1
The registrar demonstrated compliance.1
The registrar restored the domain.1
The registrar's deletion of the domain was compliant.2
Generic RegistrarThe registrar demonstrated compliance.1
Registrar Data EscrowThe registrar completed its data escrow deposit.44
Registration Data (service down)The registrar's Registration Data Directory Service is now compliant.6
Registration Data InaccuracyThe domain is suspended and the registrar is not required to address the registration data inaccuracy complaint.5
The registrar demonstrated compliance.2
The registration data has been updated.2
TransferThe change of registrant has been completed.1
The registrar corrected its noncompliance.1
The 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.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 or registration within the past 60 days, or a change of registrant lock.3
The transfer cannot be completed without proof of the transfer contact's identity.1
The transfer has been completed.4
Uniform Domain-Name Dispute-Resolution (UDRP)The registrar demonstrated compliance.1
Resolved Category Total124

Out of Scope

Complaint Types Closure Code Description # of Complaints
Disclosure of gTLD Registration DataThe complaint is out of scope because customer service issues are outside of ICANN's contractual authority.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.8
DNS Abuse and Other Types of AbuseThe complaint is invalid or not actionable because there is no evidence of an abuse report filed with a registrar or registry.219
The complaint is out of scope because customer service issues are outside of ICANN's contractual authority.4
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.16
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.70
The complaint is out of scope because the complainant did not provide the requested information.122
The complaint is out of scope because the domain is not registered.3
The complaint will not be addressed because it contains offensive and/or abusive language.1
The domain is suspended and suspension is a reasonable response to the abuse report.16
The domain name is suspended or disabled and suspension is a mitigation action to stop DNS Abuse.92
Domain Renewal/RedemptionThe complaint is out of scope because customer service issues are outside of ICANN's contractual authority.4
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 about a registrar that is not within ICANN's contractual authority.1
The complaint is out of scope because it is incomplete or broad.4
The complaint is out of scope because it is regarding a country-code top-level domain.7
The complaint is out of scope because the complainant did not provide the requested information.84
Domain SuspensionThe 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.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 ICANN terminated the registrar's accreditation.5
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 regarding a country-code top-level domain.6
The complaint is out of scope because the complainant did not provide the requested information.21
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.1
Registrar Data EscrowThe complaint is out of scope because it is a duplicate of an open complaint.3
The complaint is out of scope because the registrar voluntarily terminated its ICANN accreditation.2
Registrar FeesThe complaint is out of scope because ICANN terminated the registrar's accreditation.4
The complaint is out of scope because the registrar voluntarily terminated its ICANN 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 ICANN terminated the registrar's accreditation.4
The complaint is out of scope because it is a duplicate of an open complaint.1
The complaint is out of scope because the registrar voluntarily terminated its ICANN accreditation.1
Registration Data InaccuracyThe 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.3
The complaint is out of scope because the complainant did not provide the requested information.29
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.6
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.12
The complaint is out of scope because the complainant did not provide the requested information.91
The complaint is out of scope because the unauthorized transfer was due to hijacking.2
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 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 there is no Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding.4
Out of Scope Category Total893

Registries

Registry Complaint Volume & Distribution

Complaint Type May 2025 Closed before 1st
Inquiry / Notice
Code of Conduct33
DNS Abuse4543
Generic Registry72
Registry Data Escrow64121
Registry Fees20
Reserved Names10
Zone File Access10
REGISTRY Total123169

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 2025 Quantity Sent
Volume 1st Inquiry/Notice Sent9
Volume 2nd Inquiry/Notice Sent5
Volume 3rd Inquiry/Notice Sent3
Escalated Notice5
Volume Breach-
Volume Termination-
Volume Contract Non-Renewal-
Volume Closed All - as of Current Month = 172

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 2025
Regulated (Safeguards 1-3)::FinancialDNS Abuse2
Regulated (Safeguards 1-3)::FinancialRegistry Data Escrow2
Regulated (Safeguards 1-3)::Health and FitnessRegistry Data Escrow1
Regulated (Safeguards 1-3)::Intellectual PropertyRegistry Data Escrow4
Regulated (Safeguards 1-3)::Professional ServicesRegistry Data Escrow1
Total10

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

Closure Code Category # of Complaints
Resolved122
Out of Scope50
ICANN Issue-
Registry Closed Complaints Total172

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

Out of Scope

Complaint Types Closure Code Description # of Complaints
Code of ConductThe 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 an illegal activity that is outside of ICANN's contractual authority.1
DNS AbuseThe complaint is invalid or not actionable because there is no evidence of an abuse report filed with a registrar or registry.18
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 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.4
The domain name is suspended or disabled and suspension is a mitigation action to stop DNS Abuse.15
The registry operator is not the best-equipped party to review and take appropriate, proportionate, mitigation action in the particular case.3
The reported activity is not DNS Abuse (phishing, pharming, botnets, malware or spam as a delivery mechanism for the other four types of DNS Abuse.) Therefore, DNS Abuse requirements are not applicable.1
Generic RegistryThe 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
Registry Data EscrowThe complaint is out of scope because the registry voluntarily terminated.2
Out of Scope Category Total50

Complaint Volume & Closure Rate

Volume Trend


Total Volume

CountsApril 2025May 2025
Total New1,7461,153
Total Closed1,7351,189