ICANN Contractual Compliance Dashboard for February 2019
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 | February 2019 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Abuse | 87 | 58 |
| CEO Certification | 19 | 4 |
| Customer Service | 13 | 11 |
| Data Escrow | 6 | - |
| Domain Name System Security Extensions (DNSSEC), Internationalized Domain Names (IDN), Internet Protocol Version 6 (IPv6) | 8 | 10 |
| Domain Deletion | 74 | 80 |
| Domain Renewal | 78 | 73 |
| Failure To Notify | 11 | 8 |
| Fees | 7 | - |
| Privacy/Proxy | 2 | 5 |
| Registrar Contact | 13 | 14 |
| Registrar Information Specification (RIS) | 1 | 2 |
| Registrar Other | 6 | - |
| Transfer | 322 | 229 |
| Uniform Domain-Name Dispute-Resolution (UDRP) | 16 | 8 |
| WHOIS Format | 22 | 20 |
| WHOIS Inaccuracy breakdown in italics | 991 | 928 |
| Quality Review | - | - |
| Bulk Submission | - | 3 |
| Individual Submission | 991 | 925 |
| Accuracy Reporting System | - | - |
| WHOIS Service Level Agreements | 34 | 22 |
| WHOIS Unavailable | 68 | 41 |
| Total | 1778 | 1513 |
Compliance Process Volume & Turnaround Time
| February 2019 | Quantity Sent | Process Turnaround Time |
|---|---|---|
| Volume 1st Notice Sent | 277 | 12.3 |
| Volume 2nd Notice Sent | 70 | 7.7 |
| Volume 3rd Notice Sent | 16 | 9.0 |
| Volume Breach | 1 | - |
| Volume Suspension | - | - |
| Volume Termination | - | - |
| Volume Contract Non-Renewal | - | - |
| Volume Closed All - as of Current Month = 1,913 | ||
Additional Information on the Subject Matter of Complaints
| Details on Abuse Complaints | February 2019 |
|---|---|
| New gTLD | |
| Other | 2 |
| Pharming, Phishing | 1 |
| Trademark or Copyright Infringement | 1 |
| New gTLD Total | 4 |
| Legacy gTLD | |
| N/A1 | 42 |
| Malware, Botnet | Counterfeiting | 1 |
| Other | 3 |
| Pharmaceuticals | 2 |
| Pharming, Phishing | 3 |
| Pharming, Phishing | Fraudulent, deceptive practices | 1 |
| Registrar Abuse contact | 1 |
| Spam | 6 |
| Trademark or Copyright Infringement | 11 |
| Legacy gTLD Total | 70 |
| Not Specified2 | |
| N/A1 | 12 |
| Trademark or Copyright Infringement | 1 |
| Not Specified Total | 13 |
| Details on Abuse Complaints Total | 87 |
| Details on Transfer Complaints | February 2019 |
|---|---|
| New gTLD | |
| N/A1 | 6 |
| Transfer | 1 |
| New gTLD Total | 7 |
| Legacy gTLD | |
| N/A1 | 275 |
| Transfer | 14 |
| Unauthorized Transfer | 3 |
| Legacy gTLD Total | 292 |
| Not Specified2 | |
| N/A1 | 23 |
| Not Specified Total | 23 |
| Details on Transfer Complaints Total | 322 |
| Details on WHOIS Inaccuracy Complaints | February 2019 |
|---|---|
| New gTLD | |
| N/A1 | 60 |
| Operability - WHOIS data inaccuracy | 2 |
| New gTLD Total | 62 |
| Legacy gTLD | |
| NA 1 | 766 |
| Identity | 4 |
| Operability - WHOIS data inaccuracy | 73 |
| Operability - Whois data not available | 1 |
| Legacy gTLD Total | 844 |
| Not Specified2 | |
| N/A1 | 85 |
| Not Specified Total | 85 |
| Details on WHOIS Inaccuracy Complaints Total | 991 |
1. "N/A" represents tickets which are in process and the detailed complaint type has not yet been determined, as well as tickets closed prior to 1st Notice.
2. "Not specified" represents complaints for which the TLD type is not specified. Domain Name or TLD information is not always provided in the complaint or may pertain to a Registrar or Registry.
Registrar Additional Information on Complaints Related to GAC Category 1 Safeguards
| Details on GAC Category 1 Type | Complaint Type | February 2019 |
|---|---|---|
| Bullying/Harassment | WHOIS Inaccuracy | 1 |
| Children | WHOIS Inaccuracy | 1 |
| Children | Intellectual Property | WHOIS Inaccuracy | 1 |
| Corporate Identifiers | WHOIS Inaccuracy | 1 |
| Environmental | WHOIS Inaccuracy | 1 |
| Health and Fitness | Customer Service | 1 |
| Intellectual Property | Transfer | 1 |
| WHOIS Inaccuracy | 5 | |
| Total | 12 |
February 2019 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.
February 2019 Registrar Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 482 |
| Out of Scope | 1427 |
| ICANN Issue | 4 |
| Registrar Closed Complaints Total | 1913 |
February 2019 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. | 11 |
| The registrar maintained abuse records. | 1 | |
| The registrar responded to the abuse report. | 13 | |
| The registrar's abuse contact information appears in the public WHOIS. | 2 | |
| CEO Certification | The registrar submitted its annual compliance certificate. | 9 |
| The registrar's annual compliance certificate has been corrected. | 1 | |
| Data Escrow | The registrar completed its data escrow deposit. | 5 |
| The registrar completed its initial data escrow deposit. | 1 | |
| The registrar's data escrow file content issue is resolved. | 2 | |
| Domain Deletion | The domain is no longer suspended. | 5 |
| The domain was not suspended at the time the complaint was processed. | 1 | |
| The registrar's deletion of the domain was compliant. | 1 | |
| Domain Renewal | The domain has been renewed with the same registrant. | 2 |
| The registrar corrected its noncompliance. | 1 | |
| The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements. | 4 | |
| Fees | The registrar paid its ICANN fees. | 4 |
| Registrar Other | The domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint. | 2 |
| The registrar corrected its noncompliance. | 2 | |
| The registrar demonstrated compliance. | 2 | |
| Transfer | The change of registrant has been completed. | 3 |
| The registrar corrected its noncompliance. | 2 | |
| The registrar demonstrated compliance with its contractual requirements. | 6 | |
| 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. | 4 | |
| The transfer cannot be completed due to evidence of fraud. | 2 | |
| The transfer has been completed. | 27 | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | The registrar corrected its noncompliance. | 1 |
| 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 | |
| WHOIS Format | The registrar corrected its WHOIS format. | 1 |
| WHOIS Inaccuracy | The domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint. | 260 |
| The registrar demonstrated compliance. | 3 | |
| The registrar verified the domain's WHOIS information is correct. | 5 | |
| The WHOIS data has been updated. | 66 | |
| WHOIS Quality Review | The domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint. | 1 |
| WHOIS Service Level Agreements | The registrar's WHOIS service was compliant at the time the complaint was received. | 1 |
| WHOIS Unavailable | The registrar is not violating its WHOIS service obligations with ICANN. | 1 |
| The registrar's WHOIS service was restored. | 20 | |
| Resolved Category Total | 482 |
Out of Scope
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Abuse | 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 a closed complaint. | 4 | |
| 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. | 12 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 37 | |
| Customer Service | 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. | 9 | |
| Domain Deletion | 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 regarding a country-code top-level domain. | 7 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 57 | |
| The complaint is out of scope because the domain is not registered. | 1 | |
| Domain Name System Security Extensions (DNSSEC), Internationalized Domain Names (IDN), Internet Protocol Version 6 (IPv6) | 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. | 7 | |
| The complaint is out of scope because the domain is not registered. | 1 | |
| Domain Renewal | 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. | 8 | |
| 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. | 4 | |
| 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 | |
| Failure To Notify | 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. | 2 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 4 | |
| 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 the complainant did not provide the requested information. | 4 | |
| Registrar Contact | 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 website that the registrar does not use for registrar services or is not operated by the registrar. | 1 | |
| 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 regarding a country-code top-level domain. | 1 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 9 | |
| Registrar Information Specification (RIS) | The complaint is out of scope because the complainant did not provide the requested information. | 2 |
| Transfer | 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. | 23 | |
| The complaint is out of scope because it is not about an ICANN contracted party. | 2 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 23 | |
| The complaint is out of scope because the change of registrant requirements were not applicable at the time of the change. | 1 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 166 | |
| The complaint is out of scope because the complainant is not the transfer contact for the domain. | 3 | |
| The complaint is out of scope because the unauthorized transfer was due to hijacking. | 5 | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | 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 the complainant did not provide the requested information. | 4 | |
| The complaint is out of scope because there is no Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding. | 2 | |
| WHOIS Format | 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. | 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. | 2 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 14 | |
| The complaint is out of scope because the domain is not registered. | 1 | |
| WHOIS Inaccuracy | The complaint is out of scope because customer service issues are outside of ICANN's contractual authority. | 6 |
| The complaint is out of scope because ICANN does not process complaints regarding website content. | 9 | |
| The complaint is out of scope because ICANN does not process WHOIS accuracy complaints regarding third-level domains. | 3 | |
| The complaint is out of scope because ICANN is not a registrar. | 6 | |
| The complaint is out of scope because it is a duplicate of a closed complaint. | 7 | |
| The complaint is out of scope because it is a duplicate of an open complaint. | 62 | |
| 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 about information that does not exist in the domain's current WHOIS. | 6 | |
| The complaint is out of scope because it is about the WHOIS of a known privacy or proxy service. | 1 | |
| The complaint is out of scope because it is incomplete or broad. | 10 | |
| The complaint is out of scope because it is irrelevant to ICANN's contractual authority. | 2 | |
| The complaint is out of scope because it is not about an ICANN contracted party. | 2 | |
| The complaint is out of scope because it is regarding a country-code top-level domain. | 78 | |
| The complaint is out of scope because it is regarding the complainant's own domain. | 9 | |
| The complaint is out of scope because it is regarding the complainant's own domain; include information about change of registrant for domain with privacy/proxy service. | 3 | |
| The complaint is out of scope because it is regarding the complainant's own domain; includes information about change of registrant. | 7 | |
| The complaint is out of scope because spam is outside of ICANN's contractual authority. | 1 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 612 | |
| The complaint is out of scope because the domain is not registered. | 28 | |
| The complaint is out of scope because there is no evidence of an abuse report with the registrar. | 1 | |
| WHOIS Service Level Agreements | The complaint is out of scope because ICANN does not process complaints regarding website content. | 6 |
| The complaint is out of scope because it is a duplicate of a closed complaint. | 3 | |
| 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 about an illegal activity that is outside of ICANN's contractual authority. | 1 | |
| The complaint is out of scope because it is not about an ICANN contracted party. | 1 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 7 | |
| WHOIS Unavailable | The complaint is out of scope because ICANN does not process complaints regarding website content. | 1 |
| 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 an open complaint. | 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. | 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 spam is outside of ICANN's contractual authority. | 1 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 26 | |
| The complaint is out of scope because there is no evidence of an abuse report with the registrar. | 1 | |
| Out of Scope Category Total | 1427 |
ICANN Issue
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| CEO Certification | The matter has been withdrawn due to an ICANN issue. | 4 |
| ICANN Issue Category Total | 4 |
Registries
Registry Complaint Volume & Distribution
| Complaint Type | February 2019 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Abuse Contact Data | 2 | 2 |
| Code Of Conduct | 18 | - |
| Monthly Report | 1 | - |
| Registry Data Escrow | 10 | - |
| Registry Fees | 2 | - |
| Registry Other | 8 | 5 |
| Reserved Names/Controlled Interruption | - | 1 |
| Registration Restrictions Dispute Resolution Procedure | 1 | 1 |
| Service Level Agreement | 2 | 7 |
| Service Level Agreement Alerts | 6 | - |
| Uniform Rapid Suspension (URS) | 1 | 1 |
| Zone File Access | 105 | 29 |
| Total | 156 | 46 |
Compliance Process Volume & Turnaround Time
| February 2019 | Quantity Sent | Process Turnaround Time |
|---|---|---|
| Volume 1st Notice Sent | 191 | 6.1 |
| Volume 2nd Notice Sent | 62 | 6.5 |
| Volume 3rd Notice Sent | 15 | - |
| Volume Breach | - | - |
| Volume Suspension | - | - |
| Volume Termination | - | - |
| Volume Contract Non-Renewal | - | - |
| Volume Closed All - as of Current Month = 183 | ||
Registry Additional Information on Complaints Related to GAC Category 1 Safeguards
| Details on GAC Category 1 Type | Complaint Type | February 2019 |
|---|---|---|
| Charity | Zone File Access | 1 |
| Corporate Identifiers | Zone File Access | 1 |
| Financial | Zone File Access | 1 |
| Intellectual Property | Zone File Access | 1 |
| Professional Services | Uniform Rapid Suspension (URS) | 1 |
| Zone File Access | 1 | |
| Total | 6 |
February 2019 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.
February 2019 Registry Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 154 |
| Out of Scope | 29 |
| Registry Closed Complaints Total | 183 |
February 2019 Registry Closed Complaints Detail by Category and by Complaint Type
Resolved
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Code Of Conduct | The registry corrected its noncompliance. | 9 |
| The registry demonstrated compliance. | 11 | |
| Continued Operations Instrument (COI) | The registry corrected its noncompliance. | 1 |
| Monthly Report | The registry corrected its noncompliance. | 2 |
| Registry Data Escrow | ICANN received the required registry data escrow notification. | 1 |
| Service Level Agreement Alerts | The registry corrected its noncompliance. | 2 |
| Zone File Access | The registry corrected its noncompliance. | 2 |
| The registry demonstrated compliance. | 112 | |
| The request for zone file access was already approved by the registry operator at the time of processing the complaint. | 14 | |
| Resolved Category Total | 154 |
Out of Scope
| Complaint Types | Closure Code Description | # of Complaints |
|---|---|---|
| Abuse Contact Data | The complaint is out of scope because it is about a requirement that is not applicable to the selected registry. | 1 |
| The complaint is out of scope because the complainant did not provide the requested information. | 1 | |
| Registration Restrictions Dispute Resolution Procedure | The complaint is out of scope because it is about a requirement that is not applicable to the selected registry. | 1 |
| Registry Other | The complaint is out of scope because it is a duplicate of an open complaint. | 1 |
| The complaint is out of scope because the complainant did not provide the requested information. | 4 | |
| Reserved Names/Controlled Interruption | The complaint is out of scope because the complainant did not provide the requested information. | 1 |
| Service Level Agreement | The complaint is out of scope because the complainant did not provide the requested information. | 7 |
| Uniform Rapid Suspension (URS) | 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 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 the complainant did not provide the requested information. | 2 | |
| The complaint is out of scope because the registry voluntarily terminated. | 2 | |
| Out of Scope Category Total | 29 |
Complaint Volume & Closure Rate
Volume Trend
| Feb-18 | Mar-18 | Apr-18 | May-18 | Jun-18 | Jul-18 | Aug-18 | Sep-18 | Oct-18 | Nov-18 | Dec-18 | Jan-19 | Jan-19 |
| 3028 | 3036 | 2979 | 2829 | 2378 | 5422 | 4687 | 2100 | 2119 | 2295 | 1777 | 2274 | 1934 |
Total Volume
| Counts | January 2019 | February 2019 |
|---|---|---|
| Total New | 2,274 | 1,934 |
| Total Closed | 2,515 | 2,096 |
Closure Rates
| Stage | January 2019 | February 2019 |
|---|---|---|
| Received All Target ≥ 55% | 66% | 66% |
| Current Month | 49% | 51% |
| Before 1st Inquiry / Notice | 53% | 49% |
| Before 2nd Inquiry / Notice | 11% | 14% |
| Before 3rd Inquiry / Notice | 2% | 2% |
ICANN Staff Average Turnaround Time
| Measures | January 2019 | February 2019 |
|---|---|---|
| Open to 1st Inquiry / Notice | 1.2 | 1.3 |
| 2nd WIP | 4.1 | 4.2 |
| 3rd WIP | 2.1 | 2.3 |
| Formal Notices | 1.3 | 1.0 |
Contractual Compliance Overall Process Turnaround Time
| Measures | January 2019 | February 2019 |
|---|---|---|
| Received to Closed | 16 | 14 |
Note: Average Turnaround Time is shown in business days.