ICANN Contractual Compliance Dashboard for October 2024
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 | October 2024 | Closed before 1st Inquiry / Notice |
---|---|---|
Consent To Display Registration Data | 4 | 4 |
Disclosure of gTLD Registration Data | 10 | 9 |
DNS Abuse and Other Types of Abuse | 457 | 384 |
Domain Renewal/Redemption | 85 | 80 |
Domain Suspension | 22 | 25 |
Generic Registrar | 65 | 48 |
Privacy/Proxy | 5 | 3 |
Registrar Data Escrow | 231 | 181 |
Registration Data (service down) | 10 | 4 |
Registration Data Inaccuracy | 37 | 28 |
Transfer | 145 | 149 |
Uniform Domain-Name Dispute-Resolution (UDRP) | 10 | 3 |
REGISTRAR Total | 1,081 | 918 |
Compliance Process Volume
October 2024 | Quantity Sent |
---|---|
Volume 1st Inquiry/Notice Sent | 143 |
Volume 2nd Inquiry/Notice Sent | 37 |
Volume 3rd Inquiry/Notice Sent | 6 |
Escalated Notice | 31 |
Volume Breach | - |
Volume Suspension | - |
Volume Termination | - |
Volume Contract Non-Renewal | - |
Volume Closed All - as of Current Month = 1062 |
Registrar Additional Information on Complaints Related to GAC Category 1 Safeguards
Details on GAC Category 1 Type | Complaint Type | October 2024 |
---|---|---|
Highly Regulated (Safeguards 1-8)::Corporate Identifiers | DNS Abuse and Other Types of Abuse | 2 |
Regulated (Safeguards 1-3)::Corporate Identifiers | DNS Abuse and Other Types of Abuse | 1 |
Regulated (Safeguards 1-3)::Environmental | Generic Registrar | 1 |
Regulated (Safeguards 1-3)::Financial | Generic Registrar | 1 |
Regulated (Safeguards 1-3)::Intellectual Property | DNS Abuse and Other Types of Abuse | 11 |
Regulated (Safeguards 1-3)::Intellectual Property | Domain Renewal/Redemption | 3 |
Regulated (Safeguards 1-3)::Intellectual Property | Domain Suspension | 3 |
Regulated (Safeguards 1-3)::Intellectual Property | Generic Registrar | 2 |
Regulated (Safeguards 1-3)::Intellectual Property | Registration Data Inaccuracy | 1 |
Regulated (Safeguards 1-3)::Intellectual Property | Transfer | 1 |
Regulated (Safeguards 1-3)::Intellectual Property;Highly Regulated (Safeguards 1-8)::Gambling | DNS Abuse and Other Types of Abuse | 1 |
Total | 27 |
Registrar complaints processed in October 2024 related to requirements under the Interim Registration Data Policy for gTLDs:
Complaint Type | Reporter Type | Reporter Complaints received | Reporter Complaints closed before Notice/ Inquiry (out of scope) | Closure reason(s) for out of scope Reporter Complaints | 1st Inquiry/Notice | 2nd Inquiry/Notice | 3rd Inquiry/Notice | Closed Inquiry/ Notice | Total Inquires/ Notices in process | Closure reason(s) for Inquiries/Notices |
---|---|---|---|---|---|---|---|---|---|---|
Disclosure of gTLD Registration Data | ||||||||||
IP Lawyer/Brand Protection | 2 | 1 | The complaint is out of scope (1) | 1 | - | 1 | 1 | 2 | The registrar demonstrated compliance.; Registration Data disclosed (1) | |
Authorized Representative of Registrant | 1 | 1 | The complaint is out of scope (1) | - | - | - | - | - | - | |
Other | 5 | 6 | The complaint is out of scope (6) | 1 | 1 | - | - | 1 | - | |
UDRP/URS - Complainant | 1 | - | - | - | - | - | - | - | - | |
Information Security Researcher | 1 | - | - | - | - | - | - | - | - | |
Registrar | - | 1 | The complaint is out of scope (1) | - | - | - | - | - | - | |
Other Complaint Types also including disclosure requests for gTLD Registration Data: | ||||||||||
- | - | - | - | - | - | - | - | |||
Consent To Display Registration Data | ||||||||||
Consent To Display Registration Data | Registrant - Current | 1 | 2 | The complaint is out of scope (2) | - | - | - | - | - | - |
UDRP/URS - Respondent | 1 | 1 | The complaint is out of scope (1) | - | - | - | - | - | - | |
Registry Operator | 1 | 1 | The complaint is out of scope (1) | - | - | - | - | - | - | |
Reseller | 1 | - | - | - | - | - | - | - | ||
Domain Renewal/Redemption | Registrant - Current | 1 | 1 | The complaint is out of scope (1) | - | - | - | - | - | - |
Registration Data (service down) | Registrant - Current | - | - | - | - | - | - | 1 | - | |
gTLD Registration Data - RDDS | ||||||||||
- | - | - | - | - | - | - | - | |||
Total | 15 | 14 | 2 | 1 | 1 | 1 | 4 | - |
October 2024 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.
October 2024 Registrar Closed Complaints Summary
Closure Code Category | # of Complaints |
---|---|
Resolved | 333 |
Out of Scope | 729 |
ICANN Issue | - |
Registrar Closed Complaints Total | 1,062 |
October 2024 Registrar Closed Complaints Detail by Category and by Complaint Type
Resolved
Complaint Types | Closure Code Description | # of Complaints |
---|---|---|
Audit | The contracted party provided clarification to clear initial finding(s). | 1 |
The contracted party provided the requested data and documents. | 14 | |
Disclosure of gTLD Registration Data | The registrar demonstrated compliance. | 1 |
DNS Abuse and Other Types of Abuse | The registrar demonstrated having reasonably and promptly investigated and appropriately responded to an abuse report. | 9 |
The registrar does not have actionable evidence to determine the domain name is being used for DNS Abuse. | 4 | |
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. | 10 | |
The registrar suspended/deactivated the domain name. This is an appropriate mitigation action to stop the use of the domain name for DNS Abuse. | 19 | |
The registrar took appropriate mitigation action, other than suspension, to stop the use of the domain name for DNS Abuse. | 5 | |
Domain Renewal/Redemption | The registrar corrected its Expired Registration Recovery Policy (ERRP) noncompliance. | 1 |
Domain Suspension | The domain is no longer suspended. | 6 |
The registrar demonstrated compliance. | 1 | |
The registrar's deletion of the domain was compliant. | 3 | |
Generic Registrar | The registrar submitted its annual compliance certificate. | 1 |
The registrar's Registrar Information Specification form was completed. | 2 | |
Registrar Data Escrow | The registrar completed its data escrow deposit. | 202 |
The registrar demonstrated compliance. | 7 | |
Registration Data (service down) | The registrar corrected its noncompliance. | 6 |
The registrar's WHOIS service is now compliant. | 2 | |
Registration Data Inaccuracy | The domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint. | 5 |
The WHOIS data has been updated. | 2 | |
Transfer | The registrar corrected its noncompliance. | 1 |
The registrar demonstrated compliance with its contractual requirements. | 2 | |
The registrar demonstrated compliance. | 2 | |
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 evidence of fraud. | 1 | |
The transfer has been completed. | 17 | |
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. | 1 | |
Resolved Category Total | 333 |
Out of Scope
Complaint Types | Closure Code Description | # of Complaints |
---|---|---|
Consent To Display Registration Data | 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. | 3 | |
Disclosure of gTLD Registration Data | 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 the complainant did not provide the requested information. | 7 | |
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. | 124 |
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 does not process complaints regarding website content. | 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. | 10 | |
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 incomplete or broad. | 3 | |
The complaint is out of scope because it is regarding a country-code top-level domain. | 43 | |
The complaint is out of scope because the complainant did not provide the requested information. | 104 | |
The complaint is out of scope because the domain is not registered. | 3 | |
The complaint is out of scope because there is no evidence of an abuse report with the registrar. | 3 | |
The domain is suspended and suspension is a reasonable response to the abuse report. | 21 | |
The domain name is suspended or disabled and suspension is a mitigation action to stop DNS Abuse. | 63 | |
Domain Renewal/Redemption | 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 incomplete or broad. | 3 | |
The complaint is out of scope because it is regarding a country-code top-level domain. | 12 | |
The complaint is out of scope because reporter is a repeat offender. | 2 | |
The complaint is out of scope because the complainant did not provide the requested information. | 57 | |
Domain Suspension | 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. | 2 | |
The complaint is out of scope because reporter is a repeat offender. | 2 | |
The complaint is out of scope because the complainant did not provide the requested information. | 13 | |
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 does not process complaints regarding website content. | 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. | 1 | |
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. | 6 | |
The complaint is out of scope because the complainant did not provide the requested information. | 28 | |
Privacy/Proxy | 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 | |
The complaint is out of scope because there is no evidence of an abuse report with the registrar. | 1 | |
Registrar Data Escrow | The complaint is out of scope because it is a duplicate of an open complaint. | 5 |
Registration Data (service down) | 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. | 2 | |
Registration Data Inaccuracy | 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 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. | 21 | |
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 a closed complaint. | 2 | |
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. | 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. | 10 | |
The complaint is out of scope because the complainant did not provide the requested information. | 114 | |
The complaint is out of scope because the complainant is not the transfer contact for the domain. | 2 | |
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 | 729 |
Registries
Registry Complaint Volume & Distribution
Complaint Type | October 2024 | Closed before 1st Inquiry / Notice |
---|---|---|
Audit | 21 | 0 |
Code of Conduct | 2 | 4 |
DNS Abuse | 34 | 39 |
Generic Registry | 5 | 0 |
Public Interest Commitments (PIC) | 1 | 1 |
Registry Data Escrow | 42 | 37 |
Registry Fees | 1 | 0 |
Zone File Access | 6 | 2 |
REGISTRY Total | 112 | 83 |
Compliance Process Volume
October 2024 | Quantity Sent |
---|---|
Volume 1st Inquiry/Notice Sent | 28 |
Volume 2nd Inquiry/Notice Sent | 4 |
Volume 3rd Inquiry/Notice Sent | 4 |
Escalated Notice | - |
Volume Breach | - |
Volume Termination | - |
Volume Contract Non-Renewal | - |
Volume Closed All - as of Current Month = 86 |
Registry Additional Information on Complaints Related to GAC Category 1 Safeguards
Details on GAC Category 1 Type | Complaint Type | October 2024 |
---|---|---|
Regulated (Safeguards 1-3)::Children | Registry Data Escrow | 1 |
Regulated (Safeguards 1-3)::Environmental | Registry Data Escrow | 1 |
Regulated (Safeguards 1-3)::Intellectual Property | Registry Data Escrow | 1 |
Total | 3 |
October 2024 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.
October 2024 Registry Closed Complaints Summary
Closure Code Category | # of Complaints |
---|---|
Resolved | 43 |
Out of Scope | 43 |
ICANN Issue | - |
Registry Closed Complaints Total | 86 |
October 2024 Registry Closed Complaints Detail by Category and by Complaint Type
Resolved
Complaint Types | Closure Code Description | # of Complaints |
---|---|---|
Code of Conduct | The registrar demonstrated compliance. | 1 |
DNS Abuse | The registry suspended/deactivated the domain name. This is an appropriate mitigation action to contribute to stopping the use of the domain name for DNS Abuse. | 1 |
Generic Registry | The registry demonstrated compliance. | 1 |
Registry Data Escrow | ICANN received the required registry data escrow notification. | 39 |
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 | 43 |
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. | 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 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. | 24 |
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. | 1 | |
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. | 1 | |
The domain name is suspended or disabled and suspension is a mitigation action to stop DNS Abuse. | 3 | |
Public Interest Commitments (PIC) | The complaint is out of scope because it is about a private dispute that does not implicate ICANN's contractual authority. | 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 | 43 |
Complaint Volume & Closure Rate
Volume Trend
Total Volume
Counts | September 2024 | October 2024 |
---|---|---|
Total New | 2,267 | 1,193 |
Total Closed | 2,383 | 1,148 |