ICANN Contractual Compliance Dashboard for December 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 | December 2025 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Consent To Display Registration Data | 1 | 0 |
| Disclosure of gTLD Registration Data | 15 | 9 |
| DNS Abuse and Other Types of Abuse | 1,438 | 504 |
| Domain Renewal/Redemption | 74 | 62 |
| Domain Suspension | 26 | 32 |
| Generic Registrar | 132 | 31 |
| Privacy/Proxy | 9 | 1 |
| Registrar Data Escrow | 57 | 35 |
| Registrar Fees | 0 | 1 |
| Registration Data (service down) | 6 | 1 |
| Registration Data Inaccuracy | 85 | 39 |
| Transfer | 202 | 154 |
| Uniform Domain-Name Dispute-Resolution (UDRP) | 4 | 2 |
| REGISTRAR Total | 2,049 | 871 |
- 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
| December 2025 | Quantity Sent |
|---|---|
| Volume 1st Inquiry/Notice Sent | 130 |
| Volume 2nd Inquiry/Notice Sent | 12 |
| Volume 3rd Inquiry/Notice Sent | 3 |
| Escalated Notice | 3 |
| Volume Breach | 1 |
| Volume Suspension | - |
| Volume Termination | - |
| Volume Contract Non-Renewal | - |
| Volume Closed All - as of Current Month = 946 | |
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 | December 2025 |
|---|---|---|
| Highly Regulated (Safeguards 1-8)::Gambling | DNS Abuse and Other Types of Abuse | 19 |
| Regulated (Safeguards 1-3)::Children;Regulated (Safeguards 1-3)::Intellectual Property | Generic Registrar | 1 |
| Regulated (Safeguards 1-3)::Financial | DNS Abuse and Other Types of Abuse | 2 |
| Regulated (Safeguards 1-3)::Health and Fitness | DNS Abuse and Other Types of Abuse | 2 |
| Regulated (Safeguards 1-3)::Intellectual Property | DNS Abuse and Other Types of Abuse | 34 |
| Regulated (Safeguards 1-3)::Intellectual Property | Domain Suspension | 1 |
| Regulated (Safeguards 1-3)::Intellectual Property | Transfer | 1 |
| Regulated (Safeguards 1-3)::Intellectual Property | Generic Registrar | 2 |
| Regulated (Safeguards 1-3)::Intellectual Property | Domain Renewal/Redemption | 1 |
| Regulated (Safeguards 1-3)::Intellectual Property | Disclosure of gTLD Registration Data | 2 |
| Regulated (Safeguards 1-3)::Intellectual Property | Registration Data Inaccuracy | 1 |
| Total | 66 |
December 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.
December 2025 Registrar Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 121 |
| Out of Scope | 825 |
| ICANN Issue | - |
| Registrar Closed Complaints Total | 946 |
December 2025 Registrar Closed Complaints Detail by Category and by Complaint Type
Resolved
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Disclosure of gTLD Registration Data | The registrar demonstrated that it is now compliant with its publication requirements regarding Disclosure Requests. | 2 |
| DNS Abuse and Other Types of Abuse | The registrar demonstrated having reasonably and promptly investigated and appropriately responded to an abuse report. | 7 |
| The registrar does not have actionable evidence to determine the domain name is being used for DNS Abuse. | 3 | |
| The registrar suspended or deactivated the domain name. This is a reasonable response to an abuse report. | 5 | |
| The registrar suspended/deactivated the domain name. This is an appropriate mitigation action to stop the use of the domain name for DNS Abuse. | 9 | |
| The registrar took appropriate mitigation action, other than suspension, to stop the use of the domain name for DNS Abuse. | 1 | |
| Domain Renewal/Redemption | The registrar corrected its noncompliance. | 1 |
| The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements. | 3 | |
| Domain Suspension | The domain is no longer suspended. | 3 |
| The registrar demonstrated compliance. | 2 | |
| The registrar suspended the domain name in compliance with its obligations. | 1 | |
| Generic Registrar | The registrar demonstrated compliance. | 3 |
| Registrar Data Escrow | The registrar completed its data escrow deposit. | 48 |
| Registrar Fees | The registrar paid its ICANN fees. | 1 |
| Registration Data (service down) | The registrar corrected its noncompliance. | 1 |
| The registrar's Registration Data Directory Service is now compliant. | 1 | |
| Registration Data Inaccuracy | The domain is suspended and the registrar is not required to address the registration data inaccuracy complaint. | 7 |
| Transfer | The registrar corrected its noncompliance. | 1 |
| The registrar demonstrated compliance with its contractual requirements. | 1 | |
| The registrar demonstrated compliance. | 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. | 11 | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | The registrar demonstrated compliance. | 3 |
| The registrar locked a domain subject to a Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding. | 1 | |
| Resolved Category Total | 121 |
Out of Scope
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Disclosure of gTLD Registration Data | The complaint is invalid or not actionable as the evidence provided demonstrates that the registrar responded to the Disclosure Request in compliance with its obligations. | 1 |
| The complaint is invalid or not actionable as the evidence provided demonstrates that the request was incomplete or failed to meet minimum published requirements. | 1 | |
| The complaint is invalid or not actionable because the full registration data of the Proxy Service registrant is published in the RDDS. | 3 | |
| The complaint is invalid or not actionable because the registrar was not provided sufficient opportunity to review and respond before the complaint submission. | 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. | 3 | |
| DNS Abuse and Other Types of Abuse | The complaint is invalid or not actionable because there is no evidence of an abuse report filed with a registrar or registry. | 148 |
| 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 is a duplicate of a closed complaint. | 13 | |
| 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 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. | 74 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 64 | |
| 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. | 183 | |
| Domain Renewal/Redemption | 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. | 6 | |
| 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. | 47 | |
| Domain Suspension | The complaint is not actionable as the domain is no longer suspended. | 3 |
| 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. | 3 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 22 | |
| Generic Registrar | 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 is regarding a country-code top-level domain. | 11 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 19 | |
| Privacy/Proxy | The complaint is out of scope because the complainant did not provide the requested information. | 1 |
| Registration Data (service down) | The complaint is out of scope because it is regarding a country-code top-level domain. | 1 |
| Registration Data Inaccuracy | 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 the complainant did not provide the requested information. | 33 | |
| Transfer | 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 is a duplicate of an open complaint. | 15 | |
| 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. | 22 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 103 | |
| 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 unauthorized transfer was due to hijacking. | 2 | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | The complaint is out of scope because the complainant did not provide the requested information. | 2 |
| The complaint is out of scope because there is no Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding. | 1 | |
| Out of Scope Category Total | 825 |
Registries
Registry Complaint Volume & Distribution
| Complaint Type | December 2025 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Code of Conduct | 6 | 2 |
| DNS Abuse | 41 | 32 |
| Generic Registry | 2 | 2 |
| Registry Data Escrow | 42 | 22 |
| REGISTRY Total | 91 | 58 |
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
| December 2025 | Quantity Sent |
|---|---|
| Volume 1st Inquiry/Notice Sent | 6 |
| Volume 2nd Inquiry/Notice Sent | 11 |
| Volume 3rd Inquiry/Notice Sent | 1 |
| Escalated Notice | 1 |
| Volume Breach | - |
| Volume Termination | - |
| Volume Contract Non-Renewal | - |
| Volume Closed All - as of Current Month = 63 | |
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 | December 2025 |
|---|---|---|
| Regulated (Safeguards 1-3)::Health and Fitness | Registry Data Escrow | 2 |
| Regulated (Safeguards 1-3)::Intellectual Property | Registry Data Escrow | 1 |
| Regulated (Safeguards 1-3)::Intellectual Property | DNS Abuse | 2 |
| Regulated (Safeguards 1-3)::Professional Services | Registry Data Escrow | 1 |
| Total | 6 |
December 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.
December 2025 Registry Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 27 |
| Out of Scope | 36 |
| ICANN Issue | - |
| Registry Closed Complaints Total | 63 |
December 2025 Registry Closed Complaints Detail by Category and by Complaint Type
Resolved
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Generic Registry | The registry operator demonstrated to ICANN that its Whois Service is now compliant with the registry agreement. | 1 |
| Registry Data Escrow | ICANN received the required registry data escrow notification. | 25 |
| Registry Fees | The registry paid its ICANN fees. | 1 |
| Resolved Category Total | 27 |
Out of Scope
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Code of Conduct | 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 Abuse | The complaint is invalid or not actionable because there is no evidence of an abuse report filed with a registrar or registry. | 20 |
| 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 is regarding a country-code top-level domain. | 9 | |
| The domain name is suspended or disabled and suspension is a mitigation action to stop DNS Abuse. | 2 | |
| Generic Registry | The 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 | |
| Out of Scope Category Total | 36 |
Complaint Volume & Closure Rate
Volume Trend
Total Volume
| Counts | November 2025 | December 2025 |
|---|---|---|
| Total New | 1,744 | 2,140 |
| Total Closed | 929 | 1,009 |