ICANN Contractual Compliance Dashboard for August 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 August 2025 Closed before 1st
Inquiry / Notice
Consent To Display Registration Data32
Disclosure of gTLD Registration Data77
DNS Abuse and Other Types of Abuse728576
Domain Renewal/Redemption7571
Domain Suspension2627
Generic Registrar8071
Privacy/Proxy70
Registrar Data Escrow24158
Registrar Fees30
Registration Data (service down)3610
Registration Data Inaccuracy23942
Transfer198157
Uniform Domain-Name Dispute-Resolution (UDRP)100
REGISTRAR Total1,6531,021
  • 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

August 2025 Quantity Sent
Volume 1st Inquiry/Notice Sent325
Volume 2nd Inquiry/Notice Sent17
Volume 3rd Inquiry/Notice Sent7
Escalated Notice7
Volume Breach-
Volume Suspension-
Volume Termination-
Volume Contract Non-Renewal-
Volume Closed All - as of Current Month = 1147

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 August 2025
Highly Regulated (Safeguards 1-8)::FinancialDomain Suspension1
Highly Regulated (Safeguards 1-8)::GamblingDNS Abuse and Other Types of Abuse3
Regulated (Safeguards 1-3)::Children;Regulated (Safeguards 1-3)::Intellectual PropertyRegistration Data Inaccuracy1
Regulated (Safeguards 1-3)::EnvironmentalDNS Abuse and Other Types of Abuse1
Regulated (Safeguards 1-3)::FinancialDNS Abuse and Other Types of Abuse1
Regulated (Safeguards 1-3)::Intellectual PropertyDNS Abuse and Other Types of Abuse8
Regulated (Safeguards 1-3)::Intellectual PropertyDomain Suspension1
Regulated (Safeguards 1-3)::Intellectual PropertyTransfer1
Regulated (Safeguards 1-3)::Intellectual PropertyPrivacy/Proxy1
Regulated (Safeguards 1-3)::Intellectual Property;Highly Regulated (Safeguards 1-8)::GamblingGeneric Registrar1
Special: Potential for Cyber Bullying/Harassment (Safeguards 1-9)::Bullying/HarassmentTransfer1
Total20

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

August 2025 Registrar Closed Complaints Summary

Closure Code Category # of Complaints
Resolved201
Out of Scope945
ICANN Issue1
Registrar Closed Complaints Total1147

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

Resolved

Complaint Types Closure Code Description # of Complaints
DNS Abuse and Other Types of AbuseThe registrar demonstrated compliance.1
The registrar demonstrated having reasonably and promptly investigated and appropriately responded to an abuse report.25
The registrar does not have actionable evidence to determine the domain name is being used for DNS Abuse.4
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.7
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
Domain Renewal/RedemptionThe domain has been renewed with the same registrant.2
The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements.1
The registrar demonstrated compliance.1
Domain SuspensionThe domain is no longer suspended.11
The registrar restored the domain.1
Generic RegistrarThe registrar corrected its noncompliance.2
Registrar Data EscrowThe registrar completed its data escrow deposit.78
Registration Data (service down)The registrar corrected its noncompliance.2
The registrar's Registration Data Directory Service is now compliant.2
Registration Data InaccuracyThe domain is suspended and the registrar is not required to address the registration data inaccuracy complaint.11
The registration data has been updated.15
TransferThe registrar corrected its noncompliance.2
The registrar demonstrated compliance with its contractual requirements.5
The registrar demonstrated compliance.5
The transfer cannot be completed due to a transfer or registration within the past 60 days, or a change of registrant lock.2
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.7
Uniform Domain-Name Dispute-Resolution (UDRP)The registrar demonstrated compliance.2
The registrar locked a domain subject to a Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding.2
Resolved Category Total201

Out of Scope

Complaint Types Closure Code Description # of Complaints
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 the complainant did not provide the requested information.7
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.236
The complaint is out of scope because ICANN does not process complaints regarding website content.3
The complaint is out of scope because it is a duplicate of a closed complaint.17
The complaint is out of scope because it is a duplicate of an open complaint.25
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 incomplete or broad.1
The complaint is out of scope because it is regarding a country-code top-level domain.64
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.3
The domain is suspended and suspension is a reasonable response to the abuse report.25
The domain name is suspended or disabled and suspension is a mitigation action to stop DNS Abuse.105
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.2
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.7
The complaint is out of scope because the complainant did not provide the requested information.55
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 regarding a country-code top-level domain.4
The complaint is out of scope because the complainant did not provide the requested information.10
The complaint is out of scope because the domain is not registered.1
Generic RegistrarThe complaint is out of scope because customer service issues are outside of ICANN's contractual authority.7
The complaint is out of scope because ICANN does not process complaints regarding website content.3
The complaint is out of scope because it is a duplicate of a closed complaint.2
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 about a private dispute that does not implicate ICANN's contractual authority.3
The complaint is out of scope because it is about an illegal activity that is outside of ICANN's contractual authority.1
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.7
The complaint is out of scope because the complainant did not provide the requested information.40
Registration Data (service down)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 regarding a country-code top-level domain.1
The complaint is out of scope because the complainant did not provide the requested information.8
Registration Data InaccuracyThe complaint is out of scope because it is a duplicate of an open complaint.3
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.29
The complaint is out of scope because the domain is not registered.1
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.18
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 regarding a country-code top-level domain.21
The complaint is out of scope because the complainant did not provide the requested information.104
The complaint is out of scope because the complainant is not the transfer contact for the domain.1
The complaint is out of scope because the domain is not registered.1
The complaint is out of scope because the unauthorized transfer was due to hijacking.2
Out of Scope Category Total945

ICANN Issue

Complaint Types Closure Code Description # of Complaints
Registration Data InaccuracyThe matter has been withdrawn due to an ICANN issue.1
ICANN Issue Category Total1

Registries

Registry Complaint Volume & Distribution

Complaint Type August 2025 Closed before 1st
Inquiry / Notice
Code of Conduct55
DNS Abuse3220
Generic Registry81
Registry Data Escrow4731
Registry Fees10
Reserved Names10
Uniform Rapid Suspension (URS)70
Zone File Access21
REGISTRY Total10358

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

August 2025 Quantity Sent
Volume 1st Inquiry/Notice Sent16
Volume 2nd Inquiry/Notice Sent-
Volume 3rd Inquiry/Notice Sent2
Escalated Notice-
Volume Breach-
Volume Termination-
Volume Contract Non-Renewal-
Volume Closed All - as of Current Month = 77

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 August 2025
Regulated (Safeguards 1-3)::Intellectual PropertyDNS Abuse1
Regulated (Safeguards 1-3)::Intellectual PropertyGeneric Registry2
Regulated (Safeguards 1-3)::Intellectual PropertyReserved Names1
Total4

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

August 2025 Registry Closed Complaints Summary

Closure Code Category # of Complaints
Resolved50
Out of Scope27
ICANN Issue-
Registry Closed Complaints Total77

August 2025 Registry Closed Complaints Detail by Category and by Complaint Type

Resolved

Complaint Types Closure Code Description # of Complaints
AuditThe contracted party provided a timeline and action plan for addressing deficiencies.2
The contracted party provided the requested data and documents.1
The contracted party remediated all deficiencies.6
DNS AbuseThe registry published the required abuse contact. This contact provides a confirmation receipt to any party submitting an abuse report.2
The registry referred the domain and evidence to the sponsoring registrar. The registrar then took action that resulted in the abusive activity being stopped. The registry took appropriate mitigation action to contribute to disrupting the use of the domain name for DNS Abuse.1
The registry suspended/deactivated the domain name. This is an appropriate mitigation action to contribute to stopping the use of the domain name for DNS Abuse.1
Registry Data EscrowICANN received the required registry data escrow notification.31
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.5
Resolved Category Total50

Out of Scope

Complaint Types Closure Code Description # of Complaints
Code of ConductThe 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 a duplicate of a closed complaint.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 evidence of an abuse report with the registrar.1
DNS AbuseThe complaint is invalid or not actionable because there is no evidence of an abuse report filed with a registrar or registry.11
The complaint is out of scope because ICANN does not process complaints regarding website content.1
The complaint is out of scope because it is regarding a country-code top-level domain.7
The domain name is suspended or disabled and suspension is a mitigation action to stop DNS Abuse.1
Generic RegistryThe complaint is out of scope because it is regarding a country-code top-level domain.1
Zone File AccessThe complaint is out of scope because it is regarding a country-code top-level domain.1
Out of Scope Category Total27

Complaint Volume & Closure Rate

Volume Trend


Total Volume

Counts July 2025August 2025
Total New1,5501,756
Total Closed1,4141,224