ICANN Contractual Compliance Dashboard for July 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 | July 2022 | Closed before 1st Inquiry / Notice |
---|---|---|
Abuse | 306 | 228 |
Consent To Display Registration Data | 1 | 2 |
Disclosure of gTLD Registration Data | 24 | 17 |
Domain Renewal/Redemption | 52 | 41 |
Domain Suspension | 21 | 14 |
Generic Registrar | 34 | 22 |
Privacy/Proxy | 2 | - |
Registrar Data Escrow | 147 | 631 |
Registrar Fees | 2 | - |
Registration Data (service down) | 5 | 5 |
Registration Data Inaccuracy | 147 | 34 |
Transfer | 100 | 82 |
Uniform Domain-Name Dispute-Resolution (UDRP) | 13 | 1 |
Total | 854 | 1,077 |
Compliance Process Volume
July 2022 | Quantity Sent |
---|---|
Volume 1st Inquiry/Notice Sent | 246 |
Volume 2nd Inquiry/Notice Sent | 31 |
Volume 3rd Inquiry/Notice Sent | 14 |
Escalated Notice | - |
Volume Breach | - |
Volume Suspension | - |
Volume Termination | - |
Volume Contract Non-Renewal | - |
Volume Closed All - as of Current Month = 1251 |
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 | 164 |
Malware, botnet | 35 |
Spam | 76 |
Counterfeiting | 47 |
Fraudulent, deceptive practices | 161 |
Pharmaceutical | 26 |
Trademark or copyright infringement | 98 |
Abuse contact / procedures information | 28 |
Other | 55 |
Registrar Additional Information on Complaints Related to GAC Category 1 Safeguards
Details on GAC Category 1 Type | Complaint Type | July 2022 |
---|---|---|
Regulated (Safeguards 1-3)::Financial | Abuse | 1 |
Regulated (Safeguards 1-3)::Intellectual Property | Disclosure of gTLD Registration Data | 2 |
Regulated (Safeguards 1-3)::Intellectual Property | Domain Renewal/Redemption | 1 |
Regulated (Safeguards 1-3)::Intellectual Property | Transfer | 1 |
Regulated (Safeguards 1-3)::Intellectual Property | Uniform Domain-Name Dispute-Resolution (UDRP) | 2 |
Total | 7 |
Registrar Complaints Processed in July 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 | Closed Inquiry/Notice | Total Inquiries/ Notices in process | Closure reason(s) for Inquiries/Notices |
---|---|---|---|---|---|---|---|---|---|
Disclosure of gTLD Registration Data | |||||||||
IP Lawyer/Brand Protection | 19 | 14 | The complaint is out of scope (1) Requested evidence not provided (6) Duplicate complaint (open) (7) | - | - | 1 | 6 | The registrar corrected its noncompliance; Request for access to non-public Registration Data incomplete (1) | |
Authorized Representative of Registrant | 2 | 1 | Requested evidence not provided (1) | 1 | - | - | 1 | ||
LEA, Consumer Protection, Government or Data Protection Agency | 1 | - | - | - | 1 | 1 | The registrar demonstrated compliance; Registration Data disclosed (1) | ||
Reseller | - | 1 | Requested evidence not provided (1) | - | - | - | - | ||
Registrant - Current | 1 | - | - | - | - | - | |||
Other | - | - | - | - | - | 1 | |||
UDRP/URS - Provider | 1 | 1 | The complaint is out of scope (1) | 1 | - | 1 | - | The registrar corrected its noncompliance. (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 | - | - | - | - | - | 1 | ||
Other | 1 | 1 | Requested evidence not provided (1) | - | - | - | - | ||
gTLD Registration Data - RDDS | |||||||||
Generic Registrar | IP Lawyer/Brand Protection | - | - | 1 | 1 | - | 1 | ||
ICANN Compliance | - | - | - | - | 1 | 4 | The registrar corrected its noncompliance. (1) | ||
Total | 25 | 18 | 3 | 2 | 4 | 17 |
July 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.
July 2022 Registrar Closed Complaints Summary
Closure Code Category | # of Complaints |
---|---|
Resolved | 820 |
Out of Scope | 431 |
ICANN Issue | - |
Registrar Closed Complaints Total | 1251 |
July 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. | 30 |
The registrar documented a valid non-action in response to the abuse report. | 1 | |
The registrar responded to the abuse report. | 28 | |
Consent To Display Registration Data | The registrar corrected its noncompliance. | 1 |
Disclosure of gTLD Registration Data | The registrar corrected its noncompliance. | 1 |
The registrar demonstrated compliance. | 1 | |
Domain Renewal/Redemption | The domain has been renewed with the same registrant. | 2 |
The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements. | 3 | |
Domain Suspension | The domain is no longer suspended. | 3 |
The registrar restored the domain. | 1 | |
The registrar's deletion of the domain was compliant. | 2 | |
Generic Registrar | The domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint. | 1 |
The registrar corrected its noncompliance. | 4 | |
The registrar demonstrated compliance. | 1 | |
Registrar Data Escrow | The registrar completed its data escrow deposit. | 638 |
The registrar's data escrow file content issue is resolved. | 1 | |
Registration Data (service down) | The registrar's WHOIS service is now compliant. | 1 |
Registration Data Inaccuracy | The domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint. | 10 |
The registrar corrected its noncompliance. | 1 | |
The registrar verified the domain's WHOIS information is correct. | 1 | |
The WHOIS data has been updated. | 53 | |
Transfer | The registrar corrected its noncompliance. | 3 |
The registrar demonstrated compliance with its contractual requirements. | 3 | |
The registrar demonstrated compliance. | 3 | |
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 dispute over the identity of the registrant or administrative contact. | 2 | |
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 has been completed. | 19 | |
Uniform Domain-Name Dispute-Resolution (UDRP) | The registrar demonstrated compliance. | 3 |
Resolved Category Total | 820 |
Out of Scope
Complaint Types | Closure Code Description | # of Complaints |
---|---|---|
Abuse | 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. | 4 | |
The complaint is out of scope because ICANN is not a registrar. | 1 | |
The complaint is out of scope because it contains offensive language. | 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. | 6 | |
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 incomplete or broad. | 6 | |
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. | 39 | |
The complaint is out of scope because the complainant did not provide the requested information. | 51 | |
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. | 103 | |
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 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. | 7 | |
The complaint is out of scope because it is incomplete or broad. | 1 | |
The complaint is out of scope because the complainant did not provide the requested information. | 9 | |
Domain Renewal/Redemption | 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 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. | 33 | |
Domain Suspension | 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 regarding a country-code top-level domain. | 2 | |
The complaint is out of scope because the complainant did not provide the requested information. | 9 | |
Generic Registrar | 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 regarding a country-code top-level domain. | 1 | |
The complaint is out of scope because the complainant did not provide the requested information. | 14 | |
The complaint is out of scope because there is no evidence of an abuse report with the registrar. | 1 | |
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. | 3 | |
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. | 7 | |
The complaint is out of scope because the complainant did not provide the requested information. | 26 | |
Transfer | The complaint is out of scope because it contains offensive language. | 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. | 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. | 62 | |
The complaint is out of scope because the complainant is not the transfer contact for the domain. | 2 | |
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 |
Out of Scope Category Total | 431 |
Registries
Registry Complaint Volume & Distribution
Complaint Type | July 2022 | Closed before 1st Inquiry / Notice |
---|---|---|
Abuse Contact Data | 3 | 3 |
Bulk Zone File Access (ZFA) | 2 | - |
Code of Conduct | 2 | 3 |
Generic Registry | 5 | 4 |
Registry Data Escrow | 49 | 25 |
Reserved Names | 1 | 1 |
Zone File Access | 31 | 9 |
Total | 93 | 45 |
Compliance Process Volume
July 2022 | Quantity Sent |
---|---|
Volume 1st Inquiry/Notice Sent | 154 |
Volume 2nd Inquiry/Notice Sent | 5 |
Volume 3rd Inquiry/Notice Sent | 3 |
Escalated Notice | 4 |
Volume Breach | - |
Volume Termination | - |
Volume Contract Non-Renewal | - |
Volume Closed All - as of Current Month = 68 |
Registry Additional Information on Complaints Related to GAC Category 1 Safeguards
Details on GAC Category 1 Type | Complaint Type | July 2022 |
---|---|---|
Highly Regulated (Safeguards 1-8)::Charity | Zone File Access | 1 |
Regulated (Safeguards 1-3)::Intellectual Property | Zone File Access | 1 |
Total | 2 |
July 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.
July 2022 Registry Closed Complaints Summary
Closure Code Category | # of Complaints |
---|---|
Resolved | 52 |
Out of Scope | 16 |
ICANN Issue | - |
Registry Closed Complaints Total | 68 |
July 2022 Registry Closed Complaints Detail by Category and by Complaint Type
Resolved
Complaint Types | Closure Code Description | # of Complaints |
---|---|---|
Code of Conduct | The registry demonstrated compliance. | 1 |
Registry Data Escrow | ICANN received the required registry data escrow notification. | 33 |
Zone File Access | The registry demonstrated compliance. | 6 |
The request for zone file access was already approved by the registry operator at the time of processing the complaint. | 9 | |
Bulk Zone File Access (ZFA) | The registry corrected its noncompliance. | 2 |
Registry Fees | The registry paid its ICANN fees. | 1 |
Resolved Category Total | 52 |
Out of Scope
Complaint Types | Closure Code Description | # of Complaints |
---|---|---|
Abuse Contact Data | The complaint is out of scope because it is regarding a country-code top-level domain. | 2 |
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 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 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 there is no evidence of an abuse report with the registrar. | 1 | |
Registry Data Escrow | The complaint is out of scope because it is a duplicate of an open complaint. | 1 |
Zone File Access | The complaint is out of scope because it is a duplicate of an open complaint. | 3 |
The complaint is out of scope because the complainant did not provide the requested information. | 2 | |
Reserved Names | The complaint is out of scope because the complainant did not provide the requested information. | 1 |
Out of Scope Category Total | 16 |
Complaint Volume & Closure Rate
Volume Trend
Jul-21 | Aug-21 | Sep-21 | Oct-21 | Nov-21 | Dec-21 | Jan-22 | Feb-22 | Mar-22 | Apr-22 | May-22 | Jun-22 | Jul-22 |
1496 | 900 | 1016 | 1285 | 915 | 891 | 816 | 2058 | 1240 | 1124 | 856 | 1459 | 947 |
Total Volume
Counts | June 2022 | July 2022 |
---|---|---|
Total New | 1,459 | 947 |
Total Closed | 884 | 1,319 |