ICANN Contractual Compliance Dashboard for June 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 | June 2026 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Consent To Display Registration Data | 4 | 4 |
| Disclosure of gTLD Registration Data | 7 | 9 |
| DNS Abuse and Other Types of Abuse | 935 | 372 |
| Domain Renewal/Redemption | 70 | 84 |
| Domain Suspension | 24 | 42 |
| Generic Registrar | 94 | 115 |
| Privacy/Proxy | 2 | 2 |
| Registrar Data Escrow | 197 | 58 |
| Registrar Fees | 3 | 0 |
| Registration Data (service down) | 11 | 2 |
| Registration Data Inaccuracy | 69 | 66 |
| Transfer | 238 | 279 |
| Uniform Domain-Name Dispute-Resolution (UDRP) | 9 | 6 |
| REGISTRAR Total | 1,663 | 1,039 |
- 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
| June 2026 | Quantity Sent |
|---|---|
| Volume 1st Inquiry/Notice Sent | 136 |
| Volume 2nd Inquiry/Notice Sent | 28 |
| Volume 3rd Inquiry/Notice Sent | 1 |
| Escalated Notice | 14 |
| Volume Breach | 2 |
| Volume Suspension | - |
| Volume Termination | - |
| Volume Contract Non-Renewal | - |
| Volume Closed All - as of Current Month = 1165 | |
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 | June 2026 |
|---|---|---|
| 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)::Financial | DNS Abuse and Other Types of Abuse | 1 |
| Regulated (Safeguards 1-3)::Financial | Transfer | 2 |
| Regulated (Safeguards 1-3)::Financial | Generic Registrar | 1 |
| Regulated (Safeguards 1-3)::Health and Fitness | Domain Suspension | 1 |
| Regulated (Safeguards 1-3)::Health and Fitness | Transfer | 1 |
| Regulated (Safeguards 1-3)::Intellectual Property | DNS Abuse and Other Types of Abuse | 24 |
| Regulated (Safeguards 1-3)::Intellectual Property | Domain Suspension | 1 |
| Regulated (Safeguards 1-3)::Intellectual Property | Transfer | 6 |
| 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)::Professional Services | Transfer | 2 |
| Special: Potential for Cyber Bullying/Harassment (Safeguards 1-9)::Bullying/Harassment;Regulated (Safeguards 1-3)::Intellectual | Transfer | 1 |
| Total | 48 |
June 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.
June 2026 Registrar Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 202 |
| Out of Scope | 963 |
| ICANN Issue | - |
| Registrar Closed Complaints Total | 1165 |
June 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. | 1 |
| The registrar responded to the Disclosure Request in compliance with its obligations, which included the specific reason(s) for denying the request and an explanation of how it arrived at its decision. | 1 | |
| The registrar took appropriate action to correct noncompliance with its Disclosure Request response requirements. In addition, the registrar responded to the disclosure request in compliance with its obligations, which included the specific reason(s) for denying the request and an explanation of how it arrived at its decision. | 1 | |
| 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. | 1 | |
| 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. | 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. | 10 | |
| Domain Renewal/Redemption | The domain has been renewed with the same registrant. | 3 |
| The registrar corrected its Expired Registration Recovery Policy (ERRP) noncompliance. | 1 | |
| The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements. | 5 | |
| Domain Suspension | The registrar demonstrated compliance. | 1 |
| 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. | 90 |
| The registrar completed its initial data escrow deposit. | 2 | |
| Registrar Fees | The registrar paid its ICANN fees. | 1 |
| Registration Data (service down) | The registrar corrected its noncompliance. | 3 |
| Registration Data Inaccuracy | The domain is suspended and the registrar is not required to address the registration data inaccuracy complaint. | 11 |
| The registrar demonstrated compliance. | 1 | |
| The registration data has been updated. | 3 | |
| Transfer | The change of registrant is not authorized. | 1 |
| The registrar corrected its noncompliance. | 1 | |
| 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 transfer or registration within the past 60 days, or a change of registrant lock. | 2 | |
| The transfer cannot be completed due to the change of registrant lock. | 1 | |
| The transfer has been completed. | 36 | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | The registrar corrected its noncompliance. | 1 |
| The registrar locked a domain subject to a Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding. | 1 | |
| Resolved Category Total | 202 |
Out of Scope
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Consent To Display Registration Data | The complaint is out of scope because it is incomplete or broad. | 2 |
| 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 request was incomplete or failed to meet minimum published requirements. | 2 |
| 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 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. | 100 |
| 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. | 1 | |
| 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. | 6 | |
| 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. | 92 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 73 | |
| The domain is suspended and suspension is a reasonable response to the abuse report. | 36 | |
| The domain name is suspended or disabled and suspension is a mitigation action to stop DNS Abuse. | 52 | |
| The required abuse contact is displayed on the contracted party’s website and/or other designated place. | 1 | |
| 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 it is a duplicate of an open complaint. | 6 | |
| 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. | 3 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 66 | |
| The complaint will not be addressed because it contains offensive and/or abusive language. | 1 | |
| Domain Suspension | The complaint is not actionable as the domain is no longer suspended. | 11 |
| 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 a closed complaint. | 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 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. | 4 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 19 | |
| Generic Registrar | The complaint is out of scope because customer service issues are outside of ICANN's contractual authority. | 17 |
| The complaint is out of scope because ICANN is not a registrar. | 3 | |
| 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. | 9 | |
| 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 incomplete or broad. | 3 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 15 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 59 | |
| The complaint is out of scope because the domain is not registered. | 1 | |
| Privacy/Proxy | The complaint is out of scope because the complainant did not provide the requested information. | 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. | 2 | |
| The complaint is out of scope because it is a duplicate of an open complaint. | 1 | |
| Registrar Fees | The complaint is out of scope because ICANN terminated the registrar's accreditation. | 4 |
| Registration Data (service down) | The complaint is out of scope because the complainant did not provide the requested information. | 2 |
| Registration Data Inaccuracy | 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. | 3 | |
| 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. | 48 | |
| Transfer | 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. | 26 | |
| 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 about an illegal activity that is outside of ICANN's contractual authority. | 1 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 17 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 192 | |
| The complaint is out of scope because the complainant is not the transfer contact for the domain. | 5 | |
| The complaint is out of scope because the unauthorized transfer was due to hijacking. | 11 | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | The complaint is out of scope because it is regarding a country-code top-level domain. | 4 |
| The complaint is out of scope because there is no Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding. | 2 | |
| Out of Scope Category Total | 963 |
Registries
Registry Complaint Volume & Distribution
| Complaint Type | June 2026 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Code of Conduct | 1 | 1 |
| DNS Abuse | 35 | 33 |
| Generic Registry | 2 | 1 |
| Public Interest Commitments (PIC) | 0 | 1 |
| Registry Data Escrow | 204 | 203 |
| Registry Fees | 2 | 0 |
| Uniform Rapid Suspension (URS) | 1 | 0 |
| Zone File Access | 3 | 1 |
| REGISTRY Total | 248 | 240 |
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
| June 2026 | Quantity Sent |
|---|---|
| Volume 1st Inquiry/Notice Sent | 17 |
| Volume 2nd Inquiry/Notice Sent | 3 |
| Volume 3rd Inquiry/Notice Sent | 2 |
| Escalated Notice | 1 |
| Volume Breach | - |
| Volume Termination | - |
| Volume Contract Non-Renewal | - |
| Volume Closed All - as of Current Month = 247 | |
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 | June 2026 |
|---|---|---|
| Highly Regulated (Safeguards 1-8)::Financial | Registry Data Escrow | 1 |
| Highly Regulated (Safeguards 1-8)::Professional Services | Registry Data Escrow | 1 |
| Regulated (Safeguards 1-3)::Children | Registry Data Escrow | 1 |
| Regulated (Safeguards 1-3)::Financial | Registry Data Escrow | 2 |
| Regulated (Safeguards 1-3)::Generic Geographic Terms | Registry Data Escrow | 1 |
| Regulated (Safeguards 1-3)::Health and Fitness | Registry Data Escrow | 2 |
| Regulated (Safeguards 1-3)::Intellectual Property | Registry Data Escrow | 3 |
| Regulated (Safeguards 1-3)::Intellectual Property | DNS Abuse | 1 |
| Regulated (Safeguards 1-3)::Professional Services | Registry Data Escrow | 1 |
| Special: Potential for Cyber Bullying/Harassment (Safeguards 1-9)::Bullying/Harassment | Registry Data Escrow | 1 |
| Total | 14 |
June 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.
June 2026 Registry Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 209 |
| Out of Scope | 38 |
| ICANN Issue | - |
| Registry Closed Complaints Total | 247 |
June 2026 Registry Closed Complaints Detail by Category and by Complaint Type
Resolved
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| DNS Abuse | The registry published the required abuse contact. This contact provides a confirmation receipt to any party submitting an abuse report. | 1 |
| 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 | |
| Registry Data Escrow | ICANN received the required registry data escrow notification. | 204 |
| 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. | 1 |
| Resolved Category Total | 209 |
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. | 18 |
| 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. | 8 | |
| The domain name is suspended or disabled and suspension is a mitigation action to stop DNS Abuse. | 3 | |
| The registry operator is not the best-equipped party to review and take appropriate, proportionate, mitigation action in the particular case. | 3 | |
| Generic Registry | The complaint is out of scope because it is regarding a country-code top-level domain. | 1 |
| Public Interest Commitments (PIC) | The complaint is out of scope because there is no evidence of an abuse report with the registrar. | 1 |
| Registry Data Escrow | The complaint is out of scope because the registry voluntarily terminated. | 1 |
| Zone File Access | The complaint is out of scope because the complainant did not provide the requested information. | 1 |
| Out of Scope Category Total | 38 |
Complaint Volume & Closure Rate
Volume Trend
Total Volume
| Counts | May 2026 | June 2026 |
|---|---|---|
| Total New | 1,648 | 1,911 |
| Total Closed | 6,695 | 1,412 |