ICANN Contractual Compliance Dashboard for January 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 January 2019 Closed before 1st
Inquiry / Notice
Abuse10797
CEO Certification2-
Customer Service1014
Data Escrow73-
Domain Name System Security Extensions (DNSSEC), Internationalized Domain Names (IDN), Internet Protocol Version 6 (IPv6)78
Domain Deletion7981
Domain Renewal9282
Failure To Notify1515
Fees6-
Privacy/Proxy51
Registrar Contact1314
Registrar Information Specification (RIS)65
Registrar Other41
Reseller Agreement--
Transfer289307
Uniform Domain-Name Dispute-Resolution (UDRP)3128
WHOIS Format3944
WHOIS Inaccuracy
breakdown in italics
12601199
Quality Review2-
Bulk Submission1845
Individual Submission12401154
Accuracy Reporting System--
WHOIS Service Level Agreements2824
WHOIS Unavailable3941
Total21051961

Compliance Process Volume & Turnaround Time

January 2019 Quantity Sent Process Turnaround Time
Volume 1st Notice Sent53413.9
Volume 2nd Notice Sent8411.0
Volume 3rd Notice Sent216.9
Volume Breach-22.0
Volume Suspension--
Volume Termination--
Volume Contract Non-Renewal--
 
Volume Closed All - as of Current Month = 2,438

Additional Information on the Subject Matter of Complaints

Details on Abuse Complaints January 2019
New gTLD
Other5
Pharming, Phishing2
Registrar Abuse contact2
Trademark or Copyright Infringement5
New gTLD Total14
Legacy gTLD
N/A125
Fraudulent, deceptive practices8
Malware, Botnet | Trademark or Copyright Infringement | Counterfeiting1
Other2
Pharmaceuticals5
Pharming, Phishing1
Registrar Abuse contact6
Spam5
Trademark or Copyright Infringement18
Legacy gTLD Total71
Not Specified2
N/A121
Malware, Botnet1
Not Specified Total22
Details on Abuse Complaints Total107
Details on Transfer Complaints January 2019
New gTLD
N/A14
Transfer1
New gTLD Total5
Legacy gTLD
N/A1231
Change of Registrant1
Transfer24
Transfer | Change of Registrant1
Unauthorized Change of Registrant1
Unauthorized Transfer2
Legacy gTLD Total260
Not Specified2
N/A124
Not Specified Total24
Details on Transfer Complaints Total289
Details on WHOIS Inaccuracy Complaints January 2019
New gTLD
N/A170
Operability - WHOIS data inaccuracy3
New gTLD Total73
Legacy gTLD
NA 1848
Identity7
Operability - WHOIS data inaccuracy248
Operability - Whois data inaccuracy | Identity2
Operability - Whois data inaccuracy | Operability - Whois data not available3
Operability - Whois data not available1
Legacy gTLD Total1109
Not Specified2
N/A178
Not Specified Total78
Details on WHOIS Inaccuracy Complaints Total1260

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 January 2019
Corporate IdentifiersDomain Renewal1
EnvironmentalWHOIS Service Level Agreements1
FinancialDomain Name System Security Extensions (DNSSEC), Internationalized Domain Names (IDN), Internet Protocol Version 6 (IPv6)1
WHOIS Inaccuracy10
Intellectual PropertyAbuse5
Failure To Notify1
Transfer1
Uniform Domain-Name Dispute-Resolution (UDRP)2
WHOIS Format1
WHOIS Inaccuracy5
Professional ServicesWHOIS Inaccuracy1
Total29

January 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.

January 2019 Registrar Closed Complaints Summary

Closure Code Category # of Complaints
Resolved642
Out of Scope1795
ICANN Issue1
Registrar Closed Complaints Total2438

January 2019 Registrar Closed Complaints Detail by Category and by Complaint Type

Resolved

Complaint Types Closure Code Description # of Complaints
AbuseThe domain is suspended and suspension is a reasonable response to the abuse report.21
The registrar demonstrated compliance.2
The registrar documented a valid response to the abuse report.1
The registrar published the required abuse contact information.1
The registrar responded to the abuse report.22
Customer ServiceThe registrar corrected its noncompliance.1
Data EscrowThe registrar completed its data escrow deposit.48
The registrar completed its initial data escrow deposit.1
The registrar's data escrow file content issue is resolved.4
Domain DeletionThe domain is no longer suspended.7
The domain was not suspended at the time the complaint was processed.3
The registrar's deletion of the domain was compliant.1
Domain RenewalThe domain has been renewed with the same registrant.1
The registrant indicated the registrar provided the requested assistance for domain renewal.1
The registrar corrected its Expired Registration Recovery Policy (ERRP) noncompliance.3
The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements.7
FeesThe registrar paid its ICANN fees.3
Registrar OtherThe domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint.1
The registrar corrected its noncompliance.1
The registrar corrected its WHOIS accuracy noncompliance.1
Reseller AgreementThe registrar demonstrated compliance.1
TransferThe registrar corrected its noncompliance.2
The registrar demonstrated compliance with its contractual requirements.4
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.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.3
The transfer cannot be completed due to evidence of fraud.2
The transfer cannot be completed without proof of the transfer contact's identity.4
The transfer has been completed.17
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.4
The registrar demonstrated compliance with the Uniform Domain Name Dispute Resolution Policy (UDRP) requirements.2
The registrar locked a domain subject to a Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding.4
WHOIS FormatThe registrar corrected its WHOIS format.3
The registrar's WHOIS format was compliant at the time the complaint was processed.1
WHOIS InaccuracyThe domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint.360
The registrar demonstrated compliance.2
The registrar verified the domain's WHOIS information is correct.11
The WHOIS data has been updated.70
WHOIS Quality ReviewThe domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint.3
The registrar demonstrated compliance with the WHOIS accuracy requirements.1
WHOIS UnavailableThe registrar's WHOIS service is now compliant.3
The registrar's WHOIS service was compliant at the time the complaint was received.4
The registrar's WHOIS service was restored.2
Resolved Category Total642

Out of Scope

Complaint Types Closure Code Description # of Complaints
AbuseThe 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 not about an ICANN contracted party.2
The complaint is out of scope because it is regarding a country-code top-level domain.21
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
Customer ServiceThe 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.2
The complaint is out of scope because the complainant did not provide the requested information.8
Domain DeletionThe 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.6
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 spam is outside of ICANN's contractual authority.1
The complaint is out of scope because the complainant did not provide the requested information.55
The complaint is out of scope because the domain is not registered.4
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.6
Domain RenewalThe complaint is out of scope because it is a duplicate of an open complaint.12
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.68
Failure To NotifyThe 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.4
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 regarding a country-code top-level domain.4
The complaint is out of scope because the complainant did not provide the requested information.1
Privacy/ProxyThe complaint is out of scope because it is a duplicate of an open complaint.1
Registrar ContactThe complaint is out of scope because it is a duplicate of an open complaint.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.2
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 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 OtherThe complaint is out of scope because it is about an illegal activity that is outside of ICANN's contractual authority.1
TransferThe complaint is out of scope because customer service issues are outside of ICANN's contractual authority.3
The complaint is out of scope because it is a duplicate of an open complaint.46
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.25
The complaint is out of scope because the complainant did not provide the requested information.219
The complaint is out of scope because the complainant is not the domain registrant or the registrant's designated agent for purposes of a change of registrant.1
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.8
Uniform Domain-Name Dispute-Resolution (UDRP)The complaint is out of scope because it is a duplicate of a closed complaint.5
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.7
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.1
The complaint is out of scope because the complainant did not provide the requested information.7
The complaint is out of scope because there is no Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding.1
WHOIS FormatThe 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.3
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.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 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.27
The complaint is out of scope because the domain is not registered.1
WHOIS InaccuracyThe complaint is out of scope because customer service issues are outside of ICANN's contractual authority.3
The complaint is out of scope because ICANN does not process complaints regarding website content.4
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.9
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.9
The complaint is out of scope because it is a duplicate of an open complaint.40
The complaint is out of scope because it is about a domain with known compliant WHOIS.2
The complaint is out of scope because it is about a private dispute that does not implicate ICANN's contractual authority.6
The complaint is out of scope because it is about information that does not exist in the domain's current WHOIS.14
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.7
The complaint is out of scope because it is regarding a country-code top-level domain.76
The complaint is out of scope because it is regarding the complainant's own domain.21
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.6
The complaint is out of scope because it is regarding the complainant's own domain; includes information about change of registrant.16
The complaint is out of scope because the complainant did not provide the requested information.821
The complaint is out of scope because the domain is not registered.18
WHOIS Service Level AgreementsThe complaint is out of scope because ICANN does not process complaints regarding website content.7
The complaint is out of scope because ICANN is not a registrar.4
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.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.8
WHOIS UnavailableThe 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.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 regarding a country-code top-level domain.2
The complaint is out of scope because the complainant did not provide the requested information.30
Out of Scope Category Total1795

ICANN Issue

Complaint Types Closure Code Description # of Complaints
WHOIS InaccuracyThe matter has been withdrawn due to an ICANN issue.1
ICANN Issue Category Total1

Registries

Registry Complaint Volume & Distribution

Complaint Type January 2019 Closed before 1st
Inquiry / Notice
Abuse Contact Data79
Code Of Conduct13-
Continued Operations Instrument (COI)1-
Monthly Report6-
Registry Data Escrow1-
Registry Other42
Reserved Names/Controlled Interruption1-
Registration Restrictions Dispute Resolution Procedure22
Service Level Agreement61
Service Level Agreement Alerts2-
Zone File Access12626
Total16940

Compliance Process Volume & Turnaround Time

January 2019 Quantity Sent Process Turnaround Time
Volume 1st Notice Sent246.0
Volume 2nd Notice Sent54.4
Volume 3rd Notice Sent55.0
Volume Breach122.5
Volume Suspension--
Volume Termination--
Volume Contract Non-Renewal--
 
Volume Closed All - as of Current Month = 77

Registry Additional Information on Complaints Related to GAC Category 1 Safeguards

Details on GAC Category 1 Type Complaint Type January 2019
Bullying/HarassmentZone File Access1
EnvironmentalZone File Access1
Environmental | Health and FitnessZone File Access1
FinancialZone File Access2
GamblingZone File Access2
Intellectual PropertyZone File Access1
Total8

January 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.

January 2019 Registry Closed Complaints Summary

Closure Code Category # of Complaints
Resolved61
Out of Scope16
Registry Closed Complaints Total77

January 2019 Registry Closed Complaints Detail by Category and by Complaint Type

Resolved

Complaint Types Closure Code Description # of Complaints
Bulk Registration Data AccessThe registry corrected its noncompliance.1
Monthly ReportThe registry corrected its noncompliance.4
Registry FeesThe registry paid its ICANN fees.3
Service Level Agreement AlertsThe registry corrected its noncompliance.5
Zone File AccessThe registry corrected its noncompliance.6
The registry demonstrated compliance.17
The request for zone file access was already approved by the registry operator at the time of processing the complaint.25
Resolved Category Total61

Out of Scope

Complaint Types Closure Code Description # of Complaints
Abuse Contact DataThe complaint is out of scope because it is about a requirement that is not applicable to the selected registry.5
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 Restrictions Dispute Resolution ProcedureThe complaint is out of scope because it is about a requirement that is not applicable to the selected registry.2
Registry OtherThe complaint is out of scope because the complainant did not provide the requested information.2
Service Level AgreementThe complaint is out of scope because the complainant did not provide the requested information.1
Zone File AccessThe complaint is out of scope because the complainant did not provide the requested information.2
Out of Scope Category Total16

Complaint Volume & Closure Rate

Volume Trend

Jan-18Feb-18Mar-18Apr-18May-18Jun-18Jul-18Aug-18Sep-18Oct-18Nov-18Dec-18Jan-19
3308302830362979282923785422468721002119229517772274

Total Volume

Counts December 2018 January 2019
Total New1,7772,274
Total Closed1,5532,515

Closure Rates

Stage December 2018 January 2019
Received All
Target ≥ 55%
51%66%
Current Month26%49%
Before 1st Inquiry / Notice37%53%
Before 2nd Inquiry / Notice12%11%
Before 3rd Inquiry / Notice1%2%

ICANN Staff Average Turnaround Time

Measures December 2018 January 2019
Open to 1st Inquiry / Notice1.31.2
2nd WIP2.84.1
3rd WIP3.82.1
Formal Notices1.01.3

Contractual Compliance Overall Process Turnaround Time

Measures December 2018 January 2019
Received to Closed1316

Note: Average Turnaround Time is shown in business days.