ICANN Contractual Compliance Dashboard for April 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 | April 2026 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Consent To Display Registration Data | 1 | 1 |
| Disclosure of gTLD Registration Data | 5 | 6 |
| DNS Abuse and Other Types of Abuse | 4,376 | 537 |
| Domain Renewal/Redemption | 77 | 68 |
| Domain Suspension | 33 | 32 |
| Generic Registrar | 84 | 48 |
| Privacy/Proxy | 3 | 8 |
| Registrar Data Escrow | 47 | 30 |
| Registrar Fees | 1 | 0 |
| Registration Data (service down) | 16 | 9 |
| Registration Data Inaccuracy | 50 | 46 |
| Transfer | 236 | 178 |
| Uniform Domain-Name Dispute-Resolution (UDRP) | 13 | 8 |
| REGISTRAR Total | 4,942 | 971 |
- 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
| April 2026 | Quantity Sent |
|---|---|
| Volume 1st Inquiry/Notice Sent | 142 |
| Volume 2nd Inquiry/Notice Sent | 15 |
| Volume 3rd Inquiry/Notice Sent | - |
| Escalated Notice | 13 |
| Volume Breach | - |
| Volume Suspension | - |
| Volume Termination | 11 |
| Volume Contract Non-Renewal | - |
| Volume Closed All - as of Current Month = 1115 | |
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 | April 2026 |
|---|---|---|
| Highly Regulated (Safeguards 1-8)::Corporate Identifiers | Generic Registrar | 1 |
| Highly Regulated (Safeguards 1-8)::Gambling | DNS Abuse and Other Types of Abuse | 1 |
| Highly Regulated (Safeguards 1-8)::Gambling | Transfer | 2 |
| Regulated (Safeguards 1-3)::Children | DNS Abuse and Other Types of Abuse | 1 |
| Regulated (Safeguards 1-3)::Intellectual Property | DNS Abuse and Other Types of Abuse | 70 |
| Regulated (Safeguards 1-3)::Intellectual Property | Domain Suspension | 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;Regulated (Safeguards 1-3)::Children;Highly Regulated (Safeguards 1-8)::Gambli | Transfer | 1 |
| Total | 80 |
April 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.
April 2026 Registrar Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 180 |
| Out of Scope | 935 |
| ICANN Issue | - |
| Registrar Closed Complaints Total | 1115 |
April 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 took appropriate action to correct noncompliance with its Disclosure Request response requirements. In addition, the registrar responded to the request and provided the requested registration data. | 1 |
| DNS Abuse and Other Types of Abuse | The registrar demonstrated having reasonably and promptly investigated and appropriately responded to an abuse report. | 5 |
| 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. | 1 | |
| The registrar requested the registrant and/or reseller to act on an abusive activity. This is an appropriate mitigation action to disrupt the use of the domain name for DNS Abuse. | 1 | |
| The registrar suspended or deactivated the domain name. This is a reasonable response to an abuse report. | 3 | |
| The registrar suspended/deactivated the domain name. This is an appropriate mitigation action to stop the use of the domain name for DNS Abuse. | 15 | |
| The registrar took appropriate mitigation action, other than suspension, to stop the use of the domain name for DNS Abuse. | 2 | |
| Domain Renewal/Redemption | The registrant indicated the registrar provided the requested assistance for domain renewal. | 3 |
| The registrar corrected its Expired Registration Recovery Policy (ERRP) noncompliance. | 1 | |
| The registrar corrected its noncompliance. | 1 | |
| The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements. | 4 | |
| Domain Suspension | The registrar demonstrated compliance. | 1 |
| The registrar suspended the domain name in compliance with its obligations. | 4 | |
| The registry suspended the domain name in compliance with its obligations. | 1 | |
| Generic Registrar | The domain is suspended and the registrar is not required to address the registration data inaccuracy complaint. | 1 |
| The registrar demonstrated compliance. | 2 | |
| Privacy/Proxy | The registrar corrected its noncompliance. | 1 |
| The required information was displayed on the website(s) at the time the complaint was submitted. | 3 | |
| Registrar Data Escrow | The registrar completed its data escrow deposit. | 41 |
| Registrar Fees | The registrar paid its ICANN fees. | 2 |
| Registration Data (service down) | The registrar's Registration Data Directory Service is now compliant. | 9 |
| The registrar's Registration Data Directory Service was compliant at the time the complaint was received. | 1 | |
| Registration Data Inaccuracy | The domain is suspended and the registrar is not required to address the registration data inaccuracy complaint. | 18 |
| The registration data has been updated. | 11 | |
| Transfer | The registrar corrected its noncompliance. | 3 |
| The registrar demonstrated compliance with its contractual requirements. | 2 | |
| The registrar demonstrated compliance. | 8 | |
| 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 transfer or registration within the past 60 days, or a change of registrant lock. | 2 | |
| The transfer has been completed. | 23 | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | The registrar corrected its noncompliance. | 1 |
| Resolved Category Total | 180 |
Out of Scope
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Consent To Display Registration Data | 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 because the full registration data of the Proxy Service registrant is published in the RDDS. | 1 |
| The complaint is invalid or not actionable because the registrar is compliant with its publication requirements regarding Disclosure Requests. | 1 | |
| The complaint is invalid or not actionable because there is no evidence of a Disclosure Request submitted to a registrar or registry. | 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. | 266 |
| The complaint is out of scope because ICANN does not process complaints regarding website content. | 2 | |
| The complaint is out of scope because it is a duplicate of a closed complaint. | 10 | |
| The complaint is out of scope because it is a duplicate of an open complaint. | 13 | |
| 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. | 68 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 71 | |
| The complaint is out of scope because the domain is not registered. | 2 | |
| The domain is suspended and suspension is a reasonable response to the abuse report. | 17 | |
| The domain name is suspended or disabled and suspension is a mitigation action to stop DNS Abuse. | 89 | |
| Domain Renewal/Redemption | 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 is not a registrar. | 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. | 3 | |
| 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. | 9 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 48 | |
| Domain Suspension | The complaint is not actionable as the domain is no longer suspended. | 4 |
| 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. | 10 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 17 | |
| Generic Registrar | 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 ICANN does not process complaints regarding website content. | 1 | |
| The complaint is out of scope because ICANN is not a registrar. | 1 | |
| 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. | 1 | |
| 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. | 5 | |
| 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. | 18 | |
| Privacy/Proxy | 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. | 2 | |
| 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 | |
| The complaint is out of scope because the registrar voluntarily terminated its ICANN accreditation. | 1 | |
| Registrar Fees | The complaint is out of scope because ICANN terminated the registrar's accreditation. | 11 |
| The complaint is out of scope because the registrar voluntarily terminated its ICANN accreditation. | 2 | |
| 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 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. | 5 | |
| The complaint is out of scope because the domain is not registered. | 1 | |
| The complaint is out of scope because the registrar voluntarily terminated its ICANN accreditation. | 1 | |
| Registration Data Inaccuracy | 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 incomplete or broad. | 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. | 33 | |
| The complaint is out of scope because the domain is not registered. | 1 | |
| Transfer | 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 it is a duplicate of a closed complaint. | 1 | |
| 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. | 4 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 19 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 117 | |
| The complaint is out of scope because the complainant is not the domain registrant or the registrant's designated agent for purposes of a change of registrant. | 1 | |
| The complaint is out of scope because the unauthorized transfer was due to hijacking. | 5 | |
| 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 regarding a country-code top-level domain. | 1 | |
| 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. | 4 | |
| Out of Scope Category Total | 935 |
Registries
Registry Complaint Volume & Distribution
| Complaint Type | April 2026 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Code of Conduct | 1 | 1 |
| DNS Abuse | 44 | 50 |
| Generic Registry | 1 | 0 |
| Registry Data Escrow | 1,342 | 1306 |
| Registry Fees | 0 | 1 |
| Reserved Names | 0 | 1 |
| Zone File Access | 3 | 1 |
| REGISTRY Total | 1,391 | 1,360 |
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
| April 2026 | Quantity Sent |
|---|---|
| Volume 1st Inquiry/Notice Sent | 14 |
| Volume 2nd Inquiry/Notice Sent | 3 |
| Volume 3rd Inquiry/Notice Sent | - |
| Escalated Notice | 1 |
| Volume Breach | - |
| Volume Termination | - |
| Volume Contract Non-Renewal | - |
| Volume Closed All - as of Current Month = 1370 | |
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 | April 2026 |
|---|---|---|
| Highly Regulated (Safeguards 1-8)::Charity | Registry Data Escrow | 3 |
| Highly Regulated (Safeguards 1-8)::Financial | Registry Data Escrow | 3 |
| Highly Regulated (Safeguards 1-8)::Professional Services | Registry Data Escrow | 6 |
| Regulated (Safeguards 1-3)::Children | Registry Data Escrow | 9 |
| Regulated (Safeguards 1-3)::Financial | Registry Data Escrow | 11 |
| Regulated (Safeguards 1-3)::Generic Geographic Terms | Registry Data Escrow | 6 |
| Regulated (Safeguards 1-3)::Health and Fitness | Registry Data Escrow | 13 |
| Regulated (Safeguards 1-3)::Intellectual Property | Registry Data Escrow | 25 |
| Regulated (Safeguards 1-3)::Professional Services | Registry Data Escrow | 7 |
| Special: Potential for Cyber Bullying/Harassment (Safeguards 1-9)::Bullying/Harassment | Registry Data Escrow | 6 |
| Total | 89 |
April 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.
April 2026 Registry Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 1318 |
| Out of Scope | 52 |
| ICANN Issue | - |
| Registry Closed Complaints Total | 1370 |
April 2026 Registry Closed Complaints Detail by Category and by Complaint Type
Resolved
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Generic Registry | The registry corrected its noncompliance. | 1 |
| Registry Data Escrow | ICANN received the required registry data escrow notification. | 1,311 |
| Registry Fees | The registry paid its ICANN fees. | 2 |
| Zone File Access | The request for zone file access was already approved by the registry operator at the time of processing the complaint. | 4 |
| Resolved Category Total | 1,318 |
Out of Scope
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Code of Conduct | 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. | 27 |
| 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 regarding a country-code top-level domain. | 9 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 3 | |
| 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. | 5 | |
| The required abuse contact is displayed on the contracted party’s website and/or other designated place. | 2 | |
| Reserved Names | The complaint is out of scope because the complainant did not provide the requested information. | 1 |
| Out of Scope Category Total | 52 |
Complaint Volume & Closure Rate
Volume Trend
Total Volume
| Counts | March 2026 | April 2026 |
|---|---|---|
| Total New | 2,947 | 6,333 |
| Total Closed | 2,409 | 2,485 |