ICANN Contractual Compliance Dashboard for May 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 | May 2019 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Abuse | 84 | 69 |
| Customer Service | 12 | 11 |
| Data Escrow | 18 | - |
| Domain Name System Security Extensions (DNSSEC), Internationalized Domain Names (IDN), Internet Protocol Version 6 (IPv6) | 6 | 9 |
| Domain Deletion | 53 | 59 |
| Domain Renewal | 79 | 61 |
| Failure To Notify | 14 | 4 |
| Privacy/Proxy | 3 | 4 |
| Registrar Contact | 6 | 5 |
| Registrar Information Specification (RIS) | 10 | 11 |
| Registrar Other | 1 | - |
| Transfer | 357 | 331 |
| Uniform Domain-Name Dispute-Resolution (UDRP) | 16 | 14 |
| WHOIS Format | 30 | 35 |
| WHOIS Inaccuracy breakdown in italics | 978 | 786 |
| Quality Review | - | - |
| Bulk Submission | - | - |
| Individual Submission | 978 | 786 |
| Accuracy Reporting System | - | - |
| WHOIS Service Level Agreements | 39 | 42 |
| WHOIS Unavailable | 35 | 32 |
| Total | 1741 | 1473 |
Compliance Process Volume & Turnaround Time
| May 2019 | Quantity Sent | Process Turnaround Time |
|---|---|---|
| Volume 1st Notice Sent | 389 | 10.3 |
| Volume 2nd Notice Sent | 77 | 7.6 |
| Volume 3rd Notice Sent | 11 | 12.0 |
| Volume Breach | 2 | 35.0 |
| Volume Suspension | - | - |
| Volume Termination | - | - |
| Volume Contract Non-Renewal | - | - |
| Volume Closed All - as of Current Month = 1,783 | ||
Additional Information on the Subject Matter of Complaints
| Details on Abuse Complaints | May 2019 |
|---|---|
| New gTLD | |
| N/A1 | 1 |
| Fraudulent, deceptive practices | 1 |
| Other | 1 |
| Pharmaceuticals | 1 |
| Spam | 1 |
| New gTLD Total | 5 |
| Legacy gTLD | |
| N/A1 | 28 |
| Fraudulent, deceptive practices | 12 |
| Other | 13 |
| Pharmaceuticals | 6 |
| Pharming, Phishing | 2 |
| Pharming, Phishing | Fraudulent, deceptive practices | 1 |
| Registrar Abuse contact | 6 |
| Spam | 1 |
| Trademark or Copyright Infringement | 2 |
| Legacy gTLD Total | 71 |
| Not Specified2 | |
| N/A1 | 8 |
| Not Specified Total | 8 |
| Details on Abuse Complaints Total | 84 |
| Details on Transfer Complaints | May 2019 |
|---|---|
| New gTLD | |
| N/A1 | 18 |
| COR | 1 |
| Transfer | 1 |
| New gTLD Total | 20 |
| Legacy gTLD | |
| N/A1 | 268 |
| COR | 1 |
| Transfer | 37 |
| Unauthorized COR | 2 |
| Unauthorized Transfer | 7 |
| Unauthorized Transfer | Unauthorized COR | 1 |
| Legacy gTLD Total | 316 |
| Not Specified2 | |
| N/A1 | 20 |
| Unauthorized Transfer | 1 |
| Not Specified Total | 21 |
| Details on Transfer Complaints Total | 357 |
| Details on WHOIS Inaccuracy Complaints | May 2019 |
|---|---|
| New gTLD | |
| N/A1 | 24 |
| New gTLD Total | 24 |
| Legacy gTLD | |
| NA 1 | 737 |
| Identity | 9 |
| Operability - WHOIS data inaccuracy | 124 |
| Operability - Whois data inaccuracy | Operability - Whois data not available | 1 |
| Legacy gTLD Total | 871 |
| Not Specified2 | |
| N/A1 | 83 |
| Not Specified Total | 83 |
| Details on WHOIS Inaccuracy Complaints Total | 978 |
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 | May 2019 |
|---|---|---|
| Financial | WHOIS Inaccuracy | 1 |
| Health and Fitness | Domain Renewal | 1 |
| Intellectual Property | Customer Service | 1 |
| Domain Renewal | 1 | |
| Transfer | 2 | |
| WHOIS Inaccuracy | 4 | |
| Total | 10 |
May 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.
May 2019 Registrar Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 396 |
| Out of Scope | 1387 |
| Registrar Closed Complaints Total | 1783 |
May 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 published the required abuse contact information. | 2 | |
| The registrar responded to the abuse report. | 12 | |
| The registrar's abuse contact information appears in the public WHOIS. | 1 | |
| Data Escrow | The registrar completed its data escrow deposit. | 12 |
| The registrar's data escrow file content issue is resolved. | 3 | |
| Domain Deletion | The domain is no longer suspended. | 7 |
| The domain was not suspended at the time the complaint was processed. | 1 | |
| The registrar restored the domain. | 1 | |
| Domain Name System Security Extensions (DNSSEC), Internationalized Domain Names (IDN), Internet Protocol Version 6 (IPv6) | The registrar corrected its noncompliance. | 1 |
| The registrar now supports Domain Name System Security Extensions (DNSSEC). | 2 | |
| Domain Renewal | The domain has been renewed with the same registrant. | 4 |
| The registrar corrected its Expired Registration Recovery Policy (ERRP) noncompliance. | 2 | |
| The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements. | 18 | |
| Fees | The registrar paid its ICANN fees. | 2 |
| Registrar Other | The registrar corrected its noncompliance. | 1 |
| The registrar demonstrated compliance with the WHOIS accuracy requirements. | 1 | |
| The registrar demonstrated compliance. | 1 | |
| Transfer | The registrar demonstrated compliance with its contractual requirements. | 6 |
| The registrar demonstrated compliance with the change of registrant requirements. | 3 | |
| The registrar demonstrated compliance. | 1 | |
| 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. | 5 | |
| The transfer cannot be completed due to the change of registrant lock. | 3 | |
| The transfer has been completed. | 50 | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | The registrar corrected its noncompliance. | 1 |
| The registrar locked a domain subject to a Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding. | 2 | |
| WHOIS Accuracy Reporting System (WHOIS ARS) | The domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint. | 1 |
| WHOIS Format | The registrar's WHOIS format was compliant at the time the complaint was processed. | 2 |
| WHOIS Inaccuracy | The domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint. | 127 |
| The registrar verified the domain's WHOIS information is correct. | 3 | |
| The WHOIS data has been updated. | 99 | |
| WHOIS Unavailable | The registrar's WHOIS service was restored. | 7 |
| Resolved Category Total | 396 |
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. | 1 | |
| 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. | 8 | |
| 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. | 8 | |
| 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. | 34 | |
| Customer Service | 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. | 3 | |
| 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. | 5 | |
| Domain Deletion | 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 a closed complaint. | 1 | |
| 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. | 3 | |
| 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. | 39 | |
| 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 a duplicate of an open complaint. | 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. | 3 | |
| Domain Renewal | 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 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. | 47 | |
| Failure To Notify | 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 | |
| The complaint is out of scope because there is no evidence of an abuse report with the registrar. | 1 | |
| Privacy/Proxy | 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 regarding a country-code top-level domain. | 1 |
| The complaint is out of scope because the complainant did not provide the requested information. | 4 | |
| Registrar Information Specification (RIS) | 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. | 1 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 8 | |
| Transfer | The complaint is out of scope because customer service issues are outside of ICANN's contractual authority. | 5 |
| The complaint is out of scope because it is a duplicate of an open complaint. | 39 | |
| 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. | 20 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 228 | |
| The complaint is out of scope because the complainant is not the transfer contact for the domain. | 4 | |
| Uniform Domain-Name Dispute-Resolution (UDRP) | 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. | 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. | 6 | |
| WHOIS Format | 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 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. | 5 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 23 | |
| 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. | 2 | |
| The complaint is out of scope because ICANN does not process WHOIS accuracy complaints regarding third-level domains. | 8 | |
| The complaint is out of scope because ICANN is not a registrar. | 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. | 36 | |
| The complaint is out of scope because it is about a domain with known compliant WHOIS. | 1 | |
| The complaint is out of scope because it is about information that does not exist in the domain's current WHOIS. | 4 | |
| 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. | 2 | |
| The complaint is out of scope because it is irrelevant to ICANN's contractual authority. | 3 | |
| 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. | 81 | |
| The complaint is out of scope because it is regarding the complainant's own domain. | 11 | |
| The complaint is out of scope because it is regarding the complainant's own domain; includes information about change of registrant. | 5 | |
| 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. | 568 | |
| The complaint is out of scope because the domain is not registered. | 15 | |
| WHOIS Service Level Agreements | The complaint is out of scope because ICANN does not process complaints regarding website content. | 14 |
| The complaint is out of scope because it is a duplicate of an open complaint. | 9 | |
| 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. | 1 | |
| 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. | 4 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 12 | |
| WHOIS Unavailable | 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. | 7 | |
| The complaint is out of scope because the complainant did not provide the requested information. | 21 | |
| Out of Scope Category Total | 1387 |
Registries
Registry Complaint Volume & Distribution
| Complaint Type | May 2019 | Closed before 1st Inquiry / Notice |
|---|---|---|
| Abuse Contact Data | 3 | 3 |
| Code Of Conduct | 6 | - |
| Public Interest Commitments (PIC) | 1 | 1 |
| Registry Data Escrow | 1 | - |
| Registry Other | 1 | - |
| Reserved Names/Controlled Interruption | 3 | - |
| Registration Restrictions Dispute Resolution Procedure | 2 | 2 |
| Service Level Agreement | 5 | - |
| Uniform Rapid Suspension (URS) | 1 | - |
| Zone File Access | 184 | 76 |
| Total | 207 | 82 |
Compliance Process Volume & Turnaround Time
| May 2019 | Quantity Sent | Process Turnaround Time |
|---|---|---|
| Volume 1st Notice Sent | 53 | 5.8 |
| Volume 2nd Notice Sent | 9 | 6.0 |
| Volume 3rd Notice Sent | 1 | 19.3 |
| Volume Breach | 1 | - |
| Volume Suspension | - | - |
| Volume Termination | - | - |
| Volume Contract Non-Renewal | - | - |
| Volume Closed All - as of Current Month = 105 | ||
Registry Additional Information on Complaints Related to GAC Category 1 Safeguards
| Details on GAC Category 1 Type | Complaint Type | May 2019 |
|---|---|---|
| Corporate Identifiers | Zone File Access | 1 |
| Financial | Zone File Access | 5 |
| Financial | Professional Services | Zone File Access | 1 |
| Gambling | Zone File Access | 1 |
| Intellectual Property | Code Of Conduct | 1 |
| Reserved Names/Controlled Interruption | 3 | |
| Professional Services | Zone File Access | 3 |
| Total | 15 |
May 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.
May 2019 Registry Closed Complaints Summary
| Closure Code Category | # of Complaints |
|---|---|
| Resolved | 79 |
| Out of Scope | 26 |
| Registry Closed Complaints Total | 105 |
May 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. | 5 |
| Monthly Report | The registry corrected its noncompliance. | 1 |
| Zone File Access | The registry demonstrated compliance. | 20 |
| The request for zone file access was already approved by the registry operator at the time of processing the complaint. | 53 | |
| Resolved Category Total | 79 |
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. | 3 |
| Public Interest Commitments (PIC) | The complaint is out of scope because it is about a requirement that is not applicable to the selected registry. | 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. | 2 |
| Zone File Access | The complaint is out of scope because it is a duplicate of an open complaint. | 18 |
| The complaint is out of scope because it is about a requirement that is not applicable to the selected registry. | 2 | |
| Out of Scope Category Total | 26 |
Complaint Volume & Closure Rate
Volume Trend
| May-18 | Jun-18 | Jul-18 | Aug-18 | Sep-18 | Oct-18 | Nov-18 | Dec-18 | Jan-19 | Jan-19 | Feb-19 | Mar-19 | Apr-19 | May-19 |
| 2829 | 2378 | 5422 | 4687 | 2100 | 2119 | 2295 | 1777 | 2274 | 1934 | 2244 | 2130 | 1948 |
Total Volume
| Counts | April 2019 | May 2019 |
|---|---|---|
| Total New | 2,130 | 1,948 |
| Total Closed | 2,266 | 1,888 |
Closure Rates
| Stage | April 2019 | May 2019 |
|---|---|---|
| Received All Target ≥ 55% | 67% | 62% |
| Current Month | 52% | 49% |
| Before 1st Inquiry / Notice | 55% | 51% |
| Before 2nd Inquiry / Notice | 10% | 8% |
| Before 3rd Inquiry / Notice | 2% | 2% |
ICANN Staff Average Turnaround Time
| Measures | April 2019 | May 2019 |
|---|---|---|
| Open to 1st Inquiry / Notice | 1.3 | 3.2 |
| 2nd WIP | 2.6 | 2.4 |
| 3rd WIP | 3.8 | 6.8 |
| Formal Notices | 9.0 | 1.0 |
Contractual Compliance Overall Process Turnaround Time
| Measures | April 2019 | May 2019 |
|---|---|---|
| Received to Closed | 14 | 14 |
Note: Average Turnaround Time is shown in business days.