ICANN Contractual Compliance Dashboard for September 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 | September 2026 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Consent To Display Registration Data | 4 | 4 |
| Disclosure of gTLD Registration Data | 11 | 6 |
| DNS Abuse and Other Types of Abuse | 782 | 309 |
| Domain Renewal/Redemption | 100 | 61 |
| Domain Suspension | 36 | 12 |
| Generic Registrar | 93 | 47 |
| Privacy/Proxy | 3 | 3 |
| Registrar Data Escrow | 76 | 36 |
| Registrar Fees | 6 | 1 |
| Registration Data (service down) | 12 | 15 |
| Registration Data Inaccuracy | 130 | 86 |
| Transfer | 269 | 176 |
| Uniform Domain-Name Dispute-Resolution (UDRP) | 12 | 4 |
| REGISTRAR Total | 1,534 | 760 |
- 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
| September 2026 | Quantity Sent |
|---|---|
| Volume 1st Inquiry/Notice Sent | 198 |
| Volume 2nd Inquiry/Notice Sent | 33 |
| Volume 3rd Inquiry/Notice Sent | 5 |
| Escalated Notice | 10 |
| Volume Breach | 1 |
| Volume Suspension | - |
| Volume Termination | - |
| Volume Contract Non-Renewal | - |
| Volume Closed All - as of Current Month = 941 | |
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 | September 2026 |
|---|---|---|
| Highly Regulated (Safeguards 1-8)::Financial | Registration Data Inaccuracy | 1 |
| Highly Regulated (Safeguards 1-8)::Gambling | DNS Abuse and Other Types of Abuse | 3 |
| Highly Regulated (Safeguards 1-8)::Gambling | Transfer | 1 |
| Regulated (Safeguards 1-3)::Children;Regulated (Safeguards 1-3)::Intellectual Property | DNS Abuse and Other Types of Abuse | 3 |
| Regulated (Safeguards 1-3)::Environmental | DNS Abuse and Other Types of Abuse | 2 |
| Regulated (Safeguards 1-3)::Financial | DNS Abuse and Other Types of Abuse | 7 |
| Regulated (Safeguards 1-3)::Financial | Transfer | 1 |
| Regulated (Safeguards 1-3)::Intellectual Property | DNS Abuse and Other Types of Abuse | 26 |
| Regulated (Safeguards 1-3)::Intellectual Property | Transfer | 2 |
| 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 | Registration Data Inaccuracy | 1 |
| Regulated (Safeguards 1-3)::Intellectual Property | Registration Data (service down) | 1 |
| Regulated (Safeguards 1-3)::Intellectual Property | Uniform Domain-Name Dispute-Resolution (UDRP) | 1 |
| Regulated (Safeguards 1-3)::Professional Services | Transfer | 1 |
| Special: Potential for Cyber Bullying/Harassment (Safeguards 1-9)::Bullying/Harassment | DNS Abuse and Other Types of Abuse | 1 |
| Total | 54 |
September 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.
September 2026 Registrar Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 231 |
| Out of Scope | 710 |
| ICANN Issue | - |
| Registrar Closed Complaints Total | 941 |
September 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 confirmed the full registration data of the Proxy Service registrant is published in the RDDS. | 1 |
| 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. | 8 |
| The registrar does not have actionable evidence to determine the domain name is being used for DNS Abuse. | 7 | |
| The registrar requested the registrant and/or reseller to act on an abusive activity. The registrant and/or reseller then took action that resulted in the abusive activity being stopped. The registrar took appropriate mitigation action to disrupt the use of the domain name for DNS Abuse. | 2 | |
| 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. | 31 | |
| Domain Renewal/Redemption | The domain has been renewed with the same registrant. | 3 |
| The registrant indicated the registrar provided the requested assistance for domain renewal. | 3 | |
| The registrar corrected its Expired Registration Recovery Policy (ERRP) noncompliance. | 2 | |
| The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements. | 9 | |
| Domain Suspension | The registrar suspended the domain name in compliance with its obligations under the Registration Data Accuracy Program Specification. | 1 |
| The registrar suspended the domain name in compliance with its obligations. | 2 | |
| Generic Registrar | The registrar demonstrated compliance. | 2 |
| Registrar Data Escrow | The registrar completed its data escrow deposit. | 71 |
| Registration Data (service down) | The registrar’s Registration Data Directory Service is now compliant. | 1 |
| The registrar’s Registration Data Directory Service was compliant at the time the complaint was received. | 1 | |
| The registrar’s Registration Data Directory Service was restored. | 3 | |
| Registration Data Inaccuracy | The domain is suspended and the registrar is not required to address the registration data inaccuracy complaint. | 32 |
| The registrar verified the domain’s registration data is correct. | 1 | |
| The registration data has been updated. | 12 | |
| Transfer | The registrar corrected its noncompliance. | 1 |
| The registrar demonstrated compliance. | 3 | |
| 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 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 cannot be completed due to evidence of fraud. | 1 | |
| The transfer has been completed. | 14 | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | The registrar corrected its noncompliance. | 3 |
| The registrar demonstrated compliance. | 4 | |
| The registrar locked a domain subject to a Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding. | 1 | |
| Registrar Fees | The registrar paid its ICANN fees. | 1 |
| Resolved Category Total | 231 |
Out of Scope
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Consent To Display Registration Data | 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 incomplete or broad. | 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 | |
| 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. | 2 |
| 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 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. | 83 |
| The complaint is out of scope because ICANN terminated the registrar's accreditation. | 3 | |
| 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. | 12 | |
| 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. | 37 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 69 | |
| 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. | 12 | |
| The domain name is suspended or disabled and suspension is a mitigation action to stop DNS Abuse. | 80 | |
| Domain Renewal/Redemption | The complaint is out of scope because customer service issues are outside of ICANN's contractual authority. | 3 |
| 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 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. | 5 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 36 | |
| 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. | 5 | |
| 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. | 1 | |
| Generic Registrar | The complaint is out of scope because customer service issues are outside of ICANN's contractual authority. | 5 |
| 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. | 2 | |
| 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. | 8 | |
| 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. | 20 | |
| 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 a closed complaint. | 1 | |
| Registration Data (service down) | The 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. | 1 | |
| The complaint is out of scope because ICANN terminated the registrar's accreditation. | 1 | |
| The complaint is out of scope because it is incomplete or broad. | 6 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 2 | |
| Registration Data Inaccuracy | 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. | 6 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 68 | |
| Transfer | 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 an open complaint. | 28 | |
| 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. | 8 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 113 | |
| The complaint is out of scope because the complainant is not the transfer contact for the domain. | 3 | |
| 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. | 12 | |
| 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 there is no Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding. | 3 | |
| Privacy/Proxy | The complaint is out of scope because it is regarding a country-code top-level domain. | 2 |
| The complaint is out of scope because the complainant did not provide the requested information. | 1 | |
| Registrar Fees | The complaint is out of scope because ICANN terminated the registrar's accreditation. | 1 |
| Out of Scope Category Total | 710 |
Registries
Registry Complaint Volume & Distribution
| Complaint Type | September 2026 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Code of Conduct | 4 | 5 |
| DNS Abuse | 32 | 33 |
| Generic Registry | 6 | 5 |
| Registry Data Escrow | 92 | 68 |
| Registry Fees | 1 | 0 |
| Uniform Rapid Suspension (URS) | 1 | 1 |
| Zone File Access | 2 | 1 |
| REGISTRY Total | 138 | 113 |
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
| September 2026 | Quantity Sent |
|---|---|
| Volume 1st Inquiry/Notice Sent | 7 |
| Volume 2nd Inquiry/Notice Sent | 2 |
| Volume 3rd Inquiry/Notice Sent | - |
| Escalated Notice | - |
| Volume Breach | - |
| Volume Termination | - |
| Volume Contract Non-Renewal | - |
| Volume Closed All - as of Current Month = 122 | |
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 | September 2026 |
|---|---|---|
| Highly Regulated (Safeguards 1-8)::Financial | Registry Data Escrow | 1 |
| Regulated (Safeguards 1-3)::Health and Fitness | Registry Data Escrow | 1 |
| Regulated (Safeguards 1-3)::Intellectual Property | Registry Data Escrow | 11 |
| Regulated (Safeguards 1-3)::Intellectual Property | DNS Abuse | 1 |
| Total | 14 |
September 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.
September 2026 Registry Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 78 |
| Out of Scope | 44 |
| ICANN Issue | - |
| Registry Closed Complaints Total | 122 |
September 2026 Registry Closed Complaints Detail by Category and by Complaint Type
Resolved
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Registry Data Escrow | ICANN received the required registry data escrow notification. | 72 |
| Registry Fees | The registry paid its ICANN fees. | 1 |
| Zone File Access | The registry demonstrated compliance. | 2 |
| The request for zone file access was already approved by the registry operator at the time of processing the complaint. | 3 | |
| Resolved Category Total | 78 |
Out of Scope
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Code of Conduct | The complaint is out of scope because ICANN is not a registrar. | 1 |
| 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. | 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. | 18 |
| 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 not about an ICANN contracted party. | 1 | |
| 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. | 1 | |
| The domain name is suspended or disabled and suspension is a mitigation action to stop DNS Abuse. | 2 | |
| The registry operator is not the best-equipped party to review and take appropriate, proportionate, mitigation action in the particular case. | 4 | |
| Generic Registry | 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. | 1 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 3 | |
| Uniform Rapid Suspension (URS) | The complaint is out of scope because it is about a private dispute that does not implicate ICANN's contractual authority. | 1 |
| Out of Scope Category Total | 44 |
Complaint Volume & Closure Rate
Volume Trend
Total Volume
| Counts | August 2026 | September 2026 |
|---|---|---|
| Total New | 1,506 | 1,672 |
| Total Closed | 1,045 | 1,063 |