ICANN Contractual Compliance Dashboard for September 2022
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 2022 | Closed before 1st Inquiry / Notice |
---|---|---|
Abuse | 344 | 282 |
Consent To Display Registration Data | 3 | 3 |
Disclosure of gTLD Registration Data | 5 | 3 |
Domain Renewal/Redemption | 48 | 40 |
Domain Suspension | 17 | 23 |
Generic Registrar | 38 | 45 |
Privacy/Proxy | 5 | 9 |
Registrar Data Escrow | 131 | 20 |
Registrar Fees | 2 | - |
Registration Data (service down) | 3 | 2 |
Registration Data Inaccuracy | 75 | 34 |
Transfer | 151 | 113 |
Uniform Domain-Name Dispute-Resolution (UDRP) | 4 | 2 |
Total | 826 | 576 |
Compliance Process Volume
September 2022 | Quantity Sent |
---|---|
Volume 1st Inquiry/Notice Sent | 159 |
Volume 2nd Inquiry/Notice Sent | 55 |
Volume 3rd Inquiry/Notice Sent | 3 |
Escalated Notice | - |
Volume Breach | - |
Volume Suspension | - |
Volume Termination | - |
Volume Contract Non-Renewal | - |
Volume Closed All - as of Current Month = 814 |
Registrar Abuse Complaint Type Detail
Abusive Activity Alleged in Connection with the Domain Name(s) in the Complaints Received: | Number of Instances the Activity has been Reported |
---|---|
Pharming, phishing | 154 |
Malware, botnet | 34 |
Spam | 83 |
Counterfeiting | 43 |
Fraudulent, deceptive practices | 188 |
Pharmaceutical | 5 |
Trademark or copyright infringement | 114 |
Abuse contact / procedures information | 53 |
Other | 44 |
Registrar Additional Information on Complaints Related to GAC Category 1 Safeguards
Details on GAC Category 1 Type | Complaint Type | September 2022 |
---|---|---|
Regulated (Safeguards 1-3)::Intellectual Property | Abuse | 1 |
Regulated (Safeguards 1-3)::Intellectual Property | Domain Renewal/Redemption | 1 |
Regulated (Safeguards 1-3)::Intellectual Property | Uniform Domain-Name Dispute-Resolution (UDRP) | 1 |
Special: Potential for Cyber Bullying/Harassment (Safeguards 1-9)::Bullying/Harassment | Generic Registrar | 1 |
Total | 4 |
Registrar Complaints Processed in September 2022 Related to Requirements Under the Temporary Specification for gTLD Registration Data
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 Inquiries/ Notices in process | Closure reason(s) for Inquiries/Notices |
---|---|---|---|---|---|---|---|---|---|---|
Disclosure of gTLD Registration Data | ||||||||||
IP Lawyer/Brand Protection | - | - | - | 1 | - | 1 | 5 | The registrar demonstrated compliance; Request for access to non-public Registration Data incomplete (1) | ||
UDRP/URS - Complainant | 1 | - | - | - | - | - | ||||
LEA, Consumer Protection, Government or Data Protection Agency | - | - | 2 | 2 | - | - | 4 | |||
Registrant - Current | - | 1 | ccTLD (1) | - | - | - | - | - | ||
Other | 4 | 2 | Requested evidence not provided (2) | - | - | - | - | 1 | ||
Other Complaint Types also including disclosure requests for gTLD Registration Data: | ||||||||||
Abuse | IP Lawyer/Brand Protection | - | - | - | - | 1 | - | 1 | ||
LEA, Consumer Protection, Government or Data Protection Agency | - | - | - | - | - | - | 1 | |||
Consent To Display Registration Data | Registrant - Current | 2 | 2 | Requested evidence not provided (1) ccTLD (1) | - | - | - | - | 2 | |
Registrant - Former | 1 | 1 | Requested evidence not provided (1) | - | - | - | - | - | ||
gTLD Registration Data - RDDS | ||||||||||
Generic Registrar | IP Lawyer/Brand Protection | - | - | - | - | - | 1 | - | The registrar corrected its noncompliance. (1) | |
ICANN Compliance | 1 | - | 1 | - | - | - | 4 | |||
Total | 9 | 6 | 3 | 3 | 1 | 2 | 18 |
September 2022 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 2022 Registrar Closed Complaints Summary
Closure Code Category | # of Complaints |
---|---|
Resolved | 289 |
Out of Scope | 525 |
ICANN Issue | - |
Registrar Closed Complaints Total | 814 |
September 2022 Registrar Closed Complaints Detail by Category and by Complaint Type
Resolved
Complaint Types | Closure Code Description | # of Complaints |
---|---|---|
Abuse | The domain is suspended and suspension is a reasonable response to the abuse report. | 39 |
The registrar corrected its noncompliance. | 1 | |
The registrar responded to the abuse report. | 35 | |
The registrar's abuse contact information appears in the public WHOIS. | 1 | |
Disclosure of gTLD Registration Data | The registrar corrected its noncompliance. | 1 |
Domain Renewal/Redemption | The registrar corrected its Expired Registration Recovery Policy (ERRP) noncompliance. | 2 |
The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements. | 2 | |
The registrar demonstrated compliance. | 1 | |
Domain Suspension | The domain is no longer suspended. | 8 |
The registrar demonstrated compliance. | 1 | |
The registrar's deletion of the domain was compliant. | 1 | |
Generic Registrar | The registrar demonstrated compliance. | 2 |
Registrar Data Escrow | The registrar completed its data escrow deposit. | 24 |
Registration Data (service down) | The registrar's WHOIS service was restored. | 2 |
Registration Data Inaccuracy | The domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint. | 84 |
The registrar demonstrated compliance. | 1 | |
The WHOIS data has been updated. | 49 | |
Transfer | The registrar corrected its noncompliance. | 1 |
The registrar demonstrated compliance with its contractual requirements. | 3 | |
The registrar demonstrated compliance. | 3 | |
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. | 4 | |
The transfer cannot be completed due to lack of payment for the prior or current registration period. | 1 | |
The transfer has been completed. | 11 | |
The transfer was denied because of a court order received by the registrar. | 1 | |
Uniform Domain-Name Dispute-Resolution (UDRP) | The registrar corrected its noncompliance. | 5 |
The registrar demonstrated compliance with the Uniform Domain Name Dispute Resolution Policy (UDRP) requirements. | 1 | |
The registrar demonstrated compliance. | 4 | |
Resolved Category Total | 289 |
Out of Scope
Complaint Types | Closure Code Description | # of Complaints |
---|---|---|
Abuse | 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. | 10 | |
The complaint is out of scope because it is a duplicate of an open complaint. | 29 | |
The complaint is out of scope because it is about a private dispute that does not implicate ICANN's contractual authority. | 3 | |
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 incomplete or broad. | 4 | |
The complaint is out of scope because it is regarding a country-code top-level domain. | 28 | |
The complaint is out of scope because the complainant did not provide the requested information. | 58 | |
The complaint is out of scope because the domain is not registered. | 1 | |
The complaint is out of scope because there is no evidence of an abuse report with the registrar. | 122 | |
Consent To Display Registration Data | 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 | |
Disclosure of gTLD Registration Data | 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 | |
Domain Renewal/Redemption | 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 regarding a country-code top-level domain. | 3 | |
The complaint is out of scope because the complainant did not provide the requested information. | 34 | |
Domain Suspension | 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 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 it is a duplicate of a closed complaint. | 1 | |
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 about a private dispute that does not implicate ICANN's contractual authority. | 3 | |
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. | 22 | |
The complaint is out of scope because there is no evidence of an abuse report with the registrar. | 4 | |
Registration Data (service down) | 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 the complainant did not provide the requested information. | 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. | 4 | |
The complaint is out of scope because the complainant did not provide the requested information. | 27 | |
Transfer | 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. | 19 | |
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. | 74 | |
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 domain is not registered. | 1 | |
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. | 1 | |
Privacy/Proxy | The complaint is out of scope because it is a duplicate of an open complaint. | 4 |
The complaint is out of scope because the complainant did not provide the requested information. | 4 | |
The complaint is out of scope because there is no evidence of an abuse report with the registrar. | 1 | |
Out of Scope Category Total | 525 |
Registries
Registry Complaint Volume & Distribution
Complaint Type | September 2022 | Closed before 1st Inquiry / Notice |
---|---|---|
Abuse Contact Data | 3 | 3 |
Code of Conduct | 2 | 3 |
Generic Registry | - | 1 |
Registry Data Escrow | 19 | 1 |
Registry Fees | 7 | - |
Reserved Names | 6 | 1 |
Zone File Access | 41 | 7 |
Total | 78 | 16 |
Compliance Process Volume
September 2022 | Quantity Sent |
---|---|
Volume 1st Inquiry/Notice Sent | 39 |
Volume 2nd Inquiry/Notice Sent | 8 |
Volume 3rd Inquiry/Notice Sent | 5 |
Escalated Notice | - |
Volume Breach | - |
Volume Termination | - |
Volume Contract Non-Renewal | - |
Volume Closed All - as of Current Month = 36 |
Registry Additional Information on Complaints Related to GAC Category 1 Safeguards
Details on GAC Category 1 Type | Complaint Type | September 2022 |
---|---|---|
Highly Regulated (Safeguards 1-8)::Financial | Reserved Names | 1 |
Highly Regulated (Safeguards 1-8)::Health and Fitness | Reserved Names | 1 |
Highly Regulated (Safeguards 1-8)::Professional Services | Reserved Names | 1 |
Total | 3 |
September 2022 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 2022 Registry Closed Complaints Summary
Closure Code Category | # of Complaints |
---|---|
Resolved | 23 |
Out of Scope | 13 |
ICANN Issue | - |
Registry Closed Complaints Total | 36 |
September 2022 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. | 2 |
Zone File Access | The registry demonstrated compliance. | 8 |
The request for zone file access was already approved by the registry operator at the time of processing the complaint. | 13 | |
Resolved Category Total | 23 |
Out of Scope
Complaint Types | Closure Code Description | # of Complaints |
---|---|---|
Abuse Contact Data | 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 regarding a country-code top-level domain. | 1 | |
The complaint is out of scope because there is no evidence of an abuse report with the registrar. | 1 | |
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 regarding a country-code top-level domain. | 1 | |
The complaint is out of scope because the complainant did not provide the requested information. | 1 | |
Generic Registry | The complaint is out of scope because the complainant did not provide the requested information. | 1 |
Zone File Access | The complaint is out of scope because it is a duplicate of an open complaint. | 4 |
The complaint is out of scope because the complainant did not provide the requested information. | 1 | |
Reserved Names | The complaint is out of scope because the complainant did not provide the requested information. | 1 |
Out of Scope Category Total | 13 |
Complaint Volume & Closure Rate
Volume Trend
Sep-21 | Oct-21 | Nov-21 | Dec-21 | Jan-22 | Feb-22 | Mar-22 | Apr-22 | May-22 | Jun-22 | Jul-22 | Aug-22 | Sep-22 |
1016 | 1285 | 915 | 891 | 816 | 2058 | 1240 | 1124 | 856 | 1459 | 947 | 3490 | 904 |
Total Volume
Counts | August 2022 | September 2022 |
---|---|---|
Total New | 3490 | 904 |
Total Closed | 1580 | 850 |