ICANN Contractual Compliance Dashboard for January 2026
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 | January 2026 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Consent To Display Registration Data | 3 | 4 |
| Disclosure of gTLD Registration Data | 7 | 11 |
| DNS Abuse and Other Types of Abuse | 750 | 599 |
| Domain Renewal/Redemption | 106 | 87 |
| Domain Suspension | 20 | 37 |
| Generic Registrar | 170 | 51 |
| Privacy/Proxy | 1 | 3 |
| Registrar Data Escrow | 59 | 33 |
| Registration Data (service down) | 8 | 25 |
| Registration Data Inaccuracy | 109 | 37 |
| Transfer | 205 | 157 |
| Uniform Domain-Name Dispute-Resolution (UDRP) | 6 | 3 |
| Registrar Fees | 2 | 0 |
| REGISTRAR Total | 1,446 | 1,047 |
- 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
| January 2026 | Quantity Sent |
|---|---|
| Volume 1st Inquiry/Notice Sent | 214 |
| Volume 2nd Inquiry/Notice Sent | 18 |
| Volume 3rd Inquiry/Notice Sent | 5 |
| Escalated Notice | 7 |
| Volume Breach | 1 |
| Volume Suspension | - |
| Volume Termination | 2 |
| Volume Contract Non-Renewal | - |
| Volume Closed All - as of Current Month = 1241 | |
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 | January 2026 |
|---|---|---|
| Highly Regulated (Safeguards 1-8)::Education | DNS Abuse and Other Types of Abuse | 1 |
| Highly Regulated (Safeguards 1-8)::Gambling | DNS Abuse and Other Types of Abuse | 2 |
| Highly Regulated (Safeguards 1-8)::Gambling | Generic Registrar | 1 |
| Regulated (Safeguards 1-3)::Children;Regulated (Safeguards 1-3)::Intellectual Property | Generic Registrar | 2 |
| Regulated (Safeguards 1-3)::Environmental;Highly Regulated (Safeguards 1-8)::Gambling | Domain Renewal/Redemption | 1 |
| Regulated (Safeguards 1-3)::Financial | DNS Abuse and Other Types of Abuse | 2 |
| Regulated (Safeguards 1-3)::Financial | Domain Suspension | 1 |
| Regulated (Safeguards 1-3)::Health and Fitness | Registration Data (service down) | 1 |
| Regulated (Safeguards 1-3)::Intellectual Property | DNS Abuse and Other Types of Abuse | 13 |
| Regulated (Safeguards 1-3)::Intellectual Property | Transfer | 1 |
| Regulated (Safeguards 1-3)::Intellectual Property | Generic Registrar | 5 |
| Regulated (Safeguards 1-3)::Intellectual Property | Registration Data Inaccuracy | 1 |
| Total | 31 |
January 2026 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.
January 2026 Registrar Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 241 |
| Out of Scope | 999 |
| ICANN Issue | 1 |
| Registrar Closed Complaints Total | 1241 |
January 2026 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. | 14 |
| The registrar does not have actionable evidence to determine the domain name is being used for DNS Abuse. | 6 | |
| The registrar suspended or deactivated the domain name. This is a reasonable response to an abuse report. | 4 | |
| The registrar suspended/deactivated the domain name. This is an appropriate mitigation action to stop the use of the domain name for DNS Abuse. | 11 | |
| Domain Renewal/Redemption | The registrar corrected its noncompliance. | 1 |
| The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements. | 8 | |
| The registrar demonstrated compliance. | 1 | |
| Domain Suspension | The registrar demonstrated compliance. | 1 |
| The registrar lifted the domain suspension. | 1 | |
| The registrar suspended the domain name in compliance with its obligations. | 1 | |
| The registry suspended the domain name in compliance with its obligations. | 1 | |
| Registrar Data Escrow | The registrar completed its data escrow deposit. | 65 |
| Registration Data (service down) | The registrar's Registration Data Directory Service is now compliant. | 11 |
| The registrar's Registration Data Directory Service was compliant at the time the complaint was received. | 10 | |
| Registration Data Inaccuracy | The domain is suspended and the registrar is not required to address the registration data inaccuracy complaint. | 34 |
| The registrar demonstrated compliance. | 2 | |
| The registrar verified the domain's registration data is correct. | 1 | |
| The registration data has been updated. | 35 | |
| Transfer | The registrar corrected its noncompliance. | 3 |
| The registrar demonstrated compliance with its contractual requirements. | 2 | |
| The registrar demonstrated compliance. | 7 | |
| 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. | 2 | |
| The transfer has been completed. | 9 | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | The registrar demonstrated compliance. | 4 |
| The registrar locked a domain subject to a Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding. | 3 | |
| Resolved Category Total | 241 |
Out of Scope
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Consent To Display Registration Data | The complaint is out of scope because it is a duplicate of an open complaint. | 1 |
| The complaint is out of scope because the complainant did not provide the requested information. | 3 | |
| Disclosure of gTLD Registration Data | The complaint is invalid or not actionable because the full registration data of the Proxy Service registrant is published in the RDDS. | 1 |
| The complaint is out of scope because the complainant did not provide the requested information. | 10 | |
| 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. | 243 |
| 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 does not process complaints regarding website content. | 5 | |
| The complaint is out of scope because it is a duplicate of a closed complaint. | 12 | |
| The complaint is out of scope because it is a duplicate of an open complaint. | 11 | |
| The complaint is out of scope because it is not about an ICANN contracted party. | 3 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 26 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 66 | |
| The domain is suspended and suspension is a reasonable response to the abuse report. | 13 | |
| The domain name is suspended or disabled and suspension is a mitigation action to stop DNS Abuse. | 219 | |
| Domain Renewal/Redemption | 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. | 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. | 1 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 16 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 58 | |
| Domain Suspension | The complaint is not actionable as the domain is no longer suspended. | 11 |
| 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. | 1 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 21 | |
| Generic Registrar | The 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. | 2 | |
| 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 regarding a country-code top-level domain. | 9 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 25 | |
| The complaint is out of scope because the domain is not registered. | 1 | |
| Privacy/Proxy | 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 incomplete or broad. | 1 | |
| Registrar Data Escrow | 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. | 1 | |
| Registration Data (service down) | The complaint is out of scope because ICANN does not process complaints regarding website content. | 1 |
| 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 a closed complaint. | 4 | |
| The complaint is out of scope because it is a duplicate of an open complaint. | 3 | |
| 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. | 2 | |
| The complaint is out of scope because it is not about an ICANN contracted party. | 1 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 1 | |
| The complaint is out of scope because the domain is not registered. | 1 | |
| Registration Data Inaccuracy | 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 regarding a country-code top-level domain. | 6 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 27 | |
| Transfer | 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. | 4 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 14 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 110 | |
| 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. | 4 | |
| 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. | 2 | |
| Out of Scope Category Total | 999 |
ICANN Issue
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Registration Data (service down) | The matter has been withdrawn due to an ICANN issue. | 1 |
| ICANN Issue Category Total | 1 |
Registries
Registry Complaint Volume & Distribution
| Complaint Type | January 2026 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Code of Conduct | 5 | 9 |
| DNS Abuse | 32 | 40 |
| Generic Registry | 5 | 6 |
| Registry Data Escrow | 63 | 82 |
| Reserved Names | 1 | 0 |
| Zone File Access | 7 | 0 |
| Registry Fees | 1 | 0 |
| REGISTRY Total | 114 | 137 |
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
| January 2026 | Quantity Sent |
|---|---|
| Volume 1st Inquiry/Notice Sent | 2 |
| Volume 2nd Inquiry/Notice Sent | 1 |
| Volume 3rd Inquiry/Notice Sent | 6 |
| Escalated Notice | - |
| Volume Breach | - |
| Volume Termination | - |
| Volume Contract Non-Renewal | - |
| Volume Closed All - as of Current Month = 139 | |
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 | January 2026 |
|---|---|---|
| Regulated (Safeguards 1-3)::Financial | Registry Data Escrow | 1 |
| Regulated (Safeguards 1-3)::Intellectual Property | Registry Data Escrow | 1 |
| Regulated (Safeguards 1-3)::Intellectual Property | DNS Abuse | 1 |
| Total | 3 |
January 2026 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.
January 2026 Registry Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 88 |
| Out of Scope | 51 |
| ICANN Issue | - |
| Registry Closed Complaints Total | 139 |
January 2026 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 it was compliant with its Whois Service obligations at the time the complaint was received. | 5 |
| Registry Data Escrow | ICANN received the required registry data escrow notification. | 82 |
| Registry Fees | The registry paid its ICANN fees. | 1 |
| Resolved Category Total | 88 |
Out of Scope
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Code of Conduct | 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 about a private dispute that does not implicate ICANN's contractual authority. | 2 | |
| The complaint is out of scope because there is no evidence of an abuse report with the registrar. | 3 | |
| DNS Abuse | The complaint is invalid or not actionable because there is no evidence of an abuse report filed with a registrar or registry. | 26 |
| 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. | 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. | 4 | |
| The complaint is out of scope because the domain is not registered. | 1 | |
| The domain name is suspended or disabled and suspension is a mitigation action to stop DNS Abuse. | 4 | |
| The required abuse contact is displayed on the contracted party’s website and/or other designated place. | 2 | |
| Generic Registry | The complaint is out of scope because it is regarding a country-code top-level domain. | 1 |
| Out of Scope Category Total | 51 |
Complaint Volume & Closure Rate
Volume Trend
Total Volume
| Counts | December 2025 | January 2026 |
|---|---|---|
| Total New | 2,140 | 1,560 |
| Total Closed | 1,009 | 1,380 |