ICANN Contractual Compliance Dashboard for June 2023
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 2023 | Closed before 1st Inquiry / Notice |
---|---|---|
Abuse | 372 | 309 |
Consent To Display Registration Data | 3 | 3 |
Disclosure of gTLD Registration Data | 9 | 5 |
Domain Renewal/Redemption | 72 | 54 |
Domain Suspension | 30 | 22 |
Generic Registrar | 49 | 45 |
Privacy/Proxy | 1 | 3 |
Registrar Data Escrow | 582 | 93 |
Registrar Fees | 3 | 1 |
Registration Data (service down) | 8 | 8 |
Registration Data Inaccuracy | 46 | 35 |
Transfer | 139 | 103 |
Uniform Domain-Name Dispute-Resolution (UDRP) | 2 | 2 |
REGISTRAR Total | 1,316 | 683 |
Compliance Process Volume
June 2023 | Quantity Sent |
---|---|
Volume 1st Inquiry/Notice Sent | 153 |
Volume 2nd Inquiry/Notice Sent | 26 |
Volume 3rd Inquiry/Notice Sent | 4 |
Escalated Notice | 7 |
Volume Breach | 1 |
Volume Suspension | - |
Volume Termination | - |
Volume Contract Non-Renewal | - |
Volume Closed All - as of Current Month = 872 |
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 | 177 |
Malware, botnet | 44 |
Spam | 91 |
Counterfeiting | 59 |
Fraudulent, deceptive practices | 223 |
Pharmaceutical | 34 |
Trademark or copyright infringement | 154 |
Abuse contact / procedures information | 64 |
Other | 66 |
Registrar Additional Information on Complaints Related to GAC Category 1 Safeguards
Details on GAC Category 1 Type | Complaint Type | June 2023 |
---|---|---|
Regulated (Safeguards 1-3)::Intellectual Property | Abuse | 5 |
Regulated (Safeguards 1-3)::Intellectual Property | Domain Suspension | 1 |
Total | 6 |
Registrar Complaints Processed in June 2023 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 | 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 | The complaint is out of scope because it is regarding a country-code top-level domain (1) | 2 | - | 5 | 4 | The registrar corrected its noncompliance.;Access to non-public Registration Data denied (4) The registrar corrected its noncompliance;Request for access to non-public Registration Data incomplete (1) | ||
Registrant - Former | 1 | 1 | The complaint is out of scope because the complainant did not provide the requested information (1) | - | - | - | - | |||
LEA, Consumer Protection, Government or Data Protection Agency | 1 | 1 | The complaint is out of scope because it is regarding a country-code top-level domain (1) | - | - | 1 | - | The registrar corrected its noncompliance;Access to non-public Registration Data denied (1) | ||
Authorized Representative of Registrant | 1 | 1 | The complaint is out of scope (1) | - | - | - | - | |||
Registrant - Current | 2 | - | - | - | - | - | ||||
Information Security Researcher | 1 | - | - | - | - | - | ||||
Other | 2 | 1 | The complaint is out of scope because the complainant did not provide the requested information (1) | 1 | - | - | 1 | |||
Other Complaint Types also including disclosure requests for gTLD Registration Data: | ||||||||||
Abuse | IP Lawyer/Brand Protection | 1 | - | 1 | 1 | - | 1 | |||
LEA, Consumer Protection, Government or Data Protection Agency | - | - | - | - | - | 1 | ||||
Other | 1 | - | 2 | - | 2 | - | The registrar demonstrated compliance; The registrar responded to abuse report (2) | |||
Consent To Display Registration Data | Registrant - Current | 2 | 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 ICANN is not a registrar (1) | - | - | - | - | ||
Registrant - Former | 1 | 1 | The complaint is out of scope because the complainant did not provide the requested information (1) | - | - | - | - | |||
gTLD Registration Data - RDDS | ||||||||||
Abuse | Non-Governmental Organization | - | - | - | - | 1 | - | The registrar responded to abuse report (1) | ||
Generic Registrar | IP Lawyer/Brand Protection | - | - | 1 | - | - | 1 | |||
ICANN Compliance | - | - | - | - | - | 1 | ||||
Total | 14 | 8 | 7 | 1 | 9 | 9 |
June 2023 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 2023 Registrar Closed Complaints Summary
Closure Code Category | # of Complaints |
---|---|
Resolved | 302 |
Out of Scope | 570 |
ICANN Issue | - |
Registrar Closed Complaints Total | 872 |
June 2023 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. | 36 |
The registrar corrected its noncompliance. | 1 | |
The registrar demonstrated compliance. | 1 | |
The registrar responded to the abuse report. | 31 | |
The registrar responded to the illegal activity reports. | 1 | |
Disclosure of gTLD Registration Data | The contracted party provided incomplete or insufficient information in request for disclosure of non-public registration data. | 1 |
The contracted party provided rationale for denying access to non-public registration data. | 4 | |
Domain Renewal/Redemption | The domain has been renewed with the same registrant. | 3 |
The registrar corrected its Expired Registration Recovery Policy (ERRP) noncompliance. | 14 | |
The registrar corrected its noncompliance. | 1 | |
The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements. | 8 | |
Domain Suspension | The registrar demonstrated compliance. | 4 |
Generic Registrar | The registrar corrected its noncompliance. | 1 |
Registrar Data Escrow | The registrar completed its data escrow deposit. | 112 |
The registrar's data escrow file content issue is resolved. | 10 | |
Registrar Fees | The registrar paid its ICANN fees. | 2 |
Registration Data Inaccuracy | The domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint. | 29 |
The registrar corrected its noncompliance. | 1 | |
The registrar demonstrated compliance. | 1 | |
The registrar verified the domain's WHOIS information is correct. | 2 | |
The WHOIS data has been updated. | 15 | |
Transfer | The registrar corrected its noncompliance. | 1 |
The registrar demonstrated compliance with its contractual requirements. | 2 | |
The registrar demonstrated compliance. | 4 | |
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 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. | 1 | |
The transfer cannot be completed due to the change of registrant lock. | 1 | |
The transfer has been completed. | 8 | |
Uniform Domain-Name Dispute-Resolution (UDRP) | The registrar demonstrated compliance with the Uniform Domain Name Dispute Resolution Policy (UDRP) requirements. | 1 |
The registrar locked a domain subject to a Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding. | 2 | |
The registry corrected its noncompliance. | 1 | |
The Uniform Domain Name Dispute Resolution Policy (UDRP) decision cannot be implemented due to an intervening lawsuit. | 1 | |
Resolved Category Total | 302 |
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. | 6 |
The complaint is out of scope because ICANN is not a registrar. | 2 | |
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. | 7 | |
The complaint is out of scope because it is about an illegal activity that is outside of ICANN's contractual authority. | 2 | |
The complaint is out of scope because it is incomplete or broad. | 4 | |
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. | 38 | |
The complaint is out of scope because spam is outside of ICANN's contractual authority. | 2 | |
The complaint is out of scope because the complainant did not provide the requested information. | 89 | |
The complaint is out of scope because the domain is not registered. | 5 | |
The complaint is out of scope because there is no evidence of an abuse report with the registrar. | 130 | |
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 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 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. | 2 | |
The complaint is out of scope because the complainant did not provide the requested information. | 2 | |
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. | 2 | |
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. | 8 | |
The complaint is out of scope because the complainant did not provide the requested information. | 36 | |
Domain Suspension | 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. | 5 | |
The complaint is out of scope because the complainant did not provide the requested information. | 15 | |
Generic Registrar | 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 incomplete or broad. | 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. | 28 | |
The complaint is out of scope because there is no evidence of an abuse report with the registrar. | 5 | |
Registrar Data Escrow | The complaint is out of scope because it is a duplicate of an open complaint. | 1 |
Registration Data (service down) | The complaint is out of scope because ICANN is not a registrar. | 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. | 4 | |
The complaint is out of scope because there is no evidence of an abuse report with the registrar. | 2 | |
Registration Data Inaccuracy | 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. | 6 | |
The complaint is out of scope because the complainant did not provide the requested information. | 17 | |
Transfer | 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 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. | 2 | |
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. | 15 | |
The complaint is out of scope because the complainant did not provide the requested information. | 75 | |
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. | 6 | |
Uniform Domain-Name Dispute-Resolution (UDRP) | 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. | 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 it is regarding a country-code top-level domain. | 1 | |
Out of Scope Category Total | 570 |
Registries
Registry Complaint Volume & Distribution
Complaint Type | June 2023 | Closed before 1st Inquiry / Notice |
---|---|---|
Abuse Contact Data | 2 | 2 |
Bulk Zone File Access (ZFA) | 2 | - |
Code of Conduct | 6 | 6 |
Generic Registry | 9 | 3 |
Registry Data Escrow | 43 | 65 |
Reserved Names | 2 | 1 |
Zone File Access | 21 | 4 |
REGISTRY Total | 85 | 81 |
Compliance Process Volume
June 2023 | Quantity Sent |
---|---|
Volume 1st Inquiry/Notice Sent | 29 |
Volume 2nd Inquiry/Notice Sent | 3 |
Volume 3rd Inquiry/Notice Sent | 4 |
Escalated Notice | - |
Volume Breach | 1 |
Volume Termination | - |
Volume Contract Non-Renewal | - |
Volume Closed All - as of Current Month = 107 |
Registry Additional Information on Complaints Related to GAC Category 1 Safeguards
Details on GAC Category 1 Type | Complaint Type | June 2023 |
---|---|---|
Highly Regulated (Safeguards 1-8)::Charity | Zone File Access | 1 |
Regulated (Safeguards 1-3)::Intellectual Property | Zone File Access | 1 |
Total | 2 |
June 2023 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 2023 Registry Closed Complaints Summary
Closure Code Category | # of Complaints |
---|---|
Resolved | 91 |
Out of Scope | 16 |
ICANN Issue | - |
Registry Closed Complaints Total | 107 |
June 2023 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. | 67 |
Zone File Access | The registry demonstrated compliance. | 1 |
Bulk Zone File Access (ZFA) | The registry corrected its noncompliance. | 2 |
Service Level Agreement Alerts | The registry corrected its noncompliance. | 21 |
Resolved Category Total | 91 |
Out of Scope
Complaint Types | Closure Code Description | # of Complaints |
---|---|---|
Abuse Contact Data | 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 there is no evidence of an abuse report with the registrar. | 1 | |
Reserved Names | 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. | 2 |
The complaint is out of scope because the complainant did not provide the requested information. | 2 | |
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 a duplicate of an open complaint. | 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 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. | 2 | |
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. | 2 | |
Out of Scope Category Total | 16 |
Complaint Volume & Closure Rate
Volume Trend
Jun-22 | Jul-22 | Aug-22 | Sep-22 | Oct-22 | Nov-22 | Dec-22 | Jan-23 | Feb-23 | Mar-23 | Apr-23 | May-23 | Jun-23 |
1459 | 947 | 3490 | 904 | 1198 | 850 | 929 | 981 | 964 | 1295 | 1653 | 1554 | 1401 |
Total Volume
Counts | May 2023 | June 2023 |
---|---|---|
Total New | 1554 | 1401 |
Total Closed | 1631 | 979 |