ICANN Contractual Compliance Dashboard for March 2020

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 March 2020 Closed before 1st
Inquiry / Notice
Abuse14597
CEO Certification10
Customer Service3527
Data Escrow350
Domain Deletion2525
Domain Name System Security Extensions (DNSSEC), Internationalized Domain Names (IDN), Internet Protocol Version 6 (IPv6)88
Domain Renewal8067
Failure To Notify2126
Fees00
Privacy/Proxy21
Registrar Contact1113
Registrar Information Specification (RIS)2314
Registrar Other101
Transfer415436
Uniform Domain-Name Dispute-Resolution (UDRP)216
WHOIS Format96
WHOIS Inaccuracy
breakdown in italics
690564
Quality Review--
Bulk Submission--
Individual Submission690564
Accuracy Reporting System--
WHOIS Service Level Agreements41
WHOIS Unavailable128
Total15471300

Note: ”Closed before 1st Inquiry/Notice” represents complaints closed during the reporting period and can include complaints received in a prior period.

Compliance Process Volume & Turnaround Time

March 2020 Quantity Sent Process Turnaround Time
Volume 1st Notice Sent13710.5
Volume 2nd Notice Sent299.3
Volume 3rd Notice Sent126.0
Volume Breach--
Volume Suspension--
Volume Termination--
Volume Contract Non-Renewal--
 
Volume Closed All - as of Current Month = 1,433

Note: “Quantity Sent” represents activity which occurred during the reporting period and can include complaints received in a prior period.

Additional Information on the Subject Matter of Complaints

Details on Abuse Complaints March 2020
New gTLD
N/A18
New gTLD Total8
Legacy gTLD
N/A1107
Fraudulent, deceptive practices2
Pharmaceuticals1
Trademark or Copyright Infringement12
Legacy gTLD Total122
Not Specified2
N/A115
Not Specified Total15
Details on Abuse Complaints Total145
Details on Transfer Complaints March 2020
New gTLD
N/A17
New gTLD Total7
Legacy gTLD
N/A1259
COR1
Transfer115
Transfer | COR1
Unauthorized Transfer4
Unauthorized Transfer | Unauthorized COR1
Legacy gTLD Total381
Not Specified2
N/A127
Not Specified Total27
Details on Transfer Complaints Total415
Details on WHOIS Inaccuracy Complaints March 2020
New gTLD
N/A146
New gTLD Total46
Legacy gTLD
NA 1551
Operability - WHOIS data inaccuracy9
Legacy gTLD Total560
Not Specified2
N/A184
Not Specified Total84
Details on WHOIS Inaccuracy Complaints Total690

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 November 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 March 2020
Corporate IdentifiersDomain Renewal1
FinancialAbuse1
Intellectual PropertyAbuse3
Failure To Notify1
Transfer1
WHOIS Format1
WHOIS Inaccuracy8
Total16

March 2020 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.

March 2020 Registrar Closed Complaints Summary

Closure Code Category # of Complaints
Resolved212
Out of Scope1221
ICANN Issue0
Registrar Closed Complaints Total1433

March 2020 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.7
The registrar responded to the abuse report.18
CEO CertificationThe registrar corrected its noncompliance.1
The registrar submitted its annual compliance certificate.8
Data EscrowThe registrar completed its data escrow deposit.5
The registrar completed its initial data escrow deposit.1
The registrar corrected its noncompliance.1
The registrar's data escrow file content issue is resolved.5
Domain DeletionThe domain is no longer suspended.3
The domain was not suspended at the time the complaint was processed.1
Domain RenewalThe registrar corrected its Expired Registration Recovery Policy (ERRP) noncompliance.2
The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements.2
FeesThe registrar paid its ICANN fees.2
Registrar OtherThe registrar corrected its noncompliance.9
The registrar demonstrated compliance.1
TransferThe registrar corrected its noncompliance.1
The registrar demonstrated compliance with its contractual requirements.6
The registrar demonstrated compliance.2
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.7
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.1
The transfer cannot be completed due to lack of payment for the prior or current registration period.1
The transfer cannot be completed without proof of the transfer contact's identity.1
The transfer has been completed.29
Uniform Domain-Name Dispute-Resolution (UDRP)The registrar corrected its noncompliance.2
The registrar locked a domain subject to a Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding.3
The registrar verified the domain with the Uniform Domain Name Dispute Resolution Policy (UDRP) provider.1
WHOIS InaccuracyThe domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint.79
The registrar verified the domain's WHOIS information is correct.2
The WHOIS data has been updated.5
WHOIS UnavailableThe registrar's WHOIS service was restored.2
Resolved Category Total212

Out of Scope

Complaint Types Closure Code Description # of Complaints
AbuseThe 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 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 it is regarding a country-code top-level domain.14
The complaint is out of scope because the complainant did not provide the requested information.72
The complaint is out of scope because the domain is not registered.1
Customer ServiceThe 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.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.20
Domain DeletionThe 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.3
The complaint is out of scope because the complainant did not provide the requested information.17
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.3
The complaint is out of scope because the complainant did not provide the requested information.5
Domain RenewalThe complaint is out of scope because it is a duplicate of an open complaint.6
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.58
Failure To NotifyThe complaint is out of scope because ICANN does not process complaints regarding website content.4
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 about a private dispute that does not implicate ICANN's contractual authority.13
The complaint is out of scope because it is about an illegal activity that is outside of ICANN's contractual authority.4
The complaint is out of scope because it is regarding a country-code top-level domain.4
Privacy/ProxyThe complaint is out of scope because the complainant did not provide the requested information.1
Registrar ContactThe 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 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 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.10
Registrar OtherThe complaint is out of scope because customer service issues are outside of ICANN's contractual authority.1
TransferThe 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 a closed complaint.1
The complaint is out of scope because it is a duplicate of an open complaint.31
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.2
The complaint is out of scope because it is regarding a country-code top-level domain.26
The complaint is out of scope because the complainant did not provide the requested information.343
The complaint is out of scope because the complainant is not the transfer contact for the domain.1
The complaint is out of scope because the domain is not registered.2
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 about a private dispute that does not implicate ICANN's contractual authority.3
The complaint is out of scope because the complainant did not provide the requested information.2
WHOIS FormatThe 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.5
WHOIS InaccuracyThe complaint is out of scope because ICANN does not process WHOIS accuracy complaints regarding third-level domains.9
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.3
The complaint is out of scope because it is a duplicate of an open complaint.32
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 information that does not exist in the domain's current WHOIS.2
The complaint is out of scope because it is incomplete or broad.5
The complaint is out of scope because it is irrelevant to ICANN's contractual authority.1
The complaint is out of scope because it is regarding a country-code top-level domain.80
The complaint is out of scope because the complainant did not provide the requested information.373
The complaint is out of scope because the domain is not registered.12
WHOIS Service Level AgreementsThe complaint is out of scope because it is a duplicate of an open complaint.1
WHOIS UnavailableThe 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.2
Out of Scope Category Total1221

Registries

Registry Complaint Volume & Distribution

Complaint Type March 2020 Closed before 1st
Inquiry / Notice
Abuse Contact Data21
Code Of Conduct120
Monthly Report40
Public Interest Commitments (PIC)11
Registration Restrictions Dispute Resolution Procedure11
Registry Data Escrow51
Registry Fees00
Registry Other10
Reserved Names/Controlled Interruption11
Service Level Agreement211
Service Level Agreement Alerts00
Uniform Rapid Suspension (URS)01
Zone File Access17160
Grand Total20077

Note: ”Closed before 1st Inquiry/Notice” represents complaints closed during the reporting period and can include complaints received in a prior period.

Compliance Process Volume & Turnaround Time

March 2020 Quantity Sent Process Turnaround Time
Volume 1st Notice Sent1375.9
Volume 2nd Notice Sent225.8
Volume 3rd Notice Sent116.0
Volume Breach--
Volume Suspension--
Volume Termination--
Volume Contract Non-Renewal--
 
Volume Closed All - as of Current Month = 195

Note: “Quantity Sent” represents activity which occurred during the reporting period and can include complaints received in a prior period.

Registry Additional Information on Complaints Related to GAC Category 1 Safeguards

Details on GAC Category 1 Type Complaint Type March 2020
Corporate IdentifiersZone File Access3
FinancialZone File Access1
Health and FitnessZone File Access1
Health and Fitness | Professional ServicesZone File Access1
Intellectual PropertyZone File Access3
Professional ServicesZone File Access3
Total12

March 2020 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.

March 2020 Registry Closed Complaints Summary

Closure Code Category # of Complaints
Resolved159
Out of Scope36
Registry Closed Complaints Total195

March 2020 Registry Closed Complaints Detail by Category and by Complaint Type

Resolved

Complaint Types Closure Code Description # of Complaints
Code Of ConductThe registry corrected its noncompliance.5
The registry demonstrated compliance.4
Monthly ReportThe registry demonstrated compliance.9
Registry Data EscrowICANN received the required registry data escrow notification.1
Registry FeesThe registry paid its ICANN fees.1
Service Level Agreement AlertsThe registry corrected its noncompliance.2
Zone File AccessThe registry demonstrated compliance.102
The request for zone file access was already approved by the registry operator at the time of processing the complaint.35
Resolved Category Total159

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.1
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 ProcedureThe complaint is out of scope because it is about a requirement that is not applicable to the selected registry.1
Reserved Names/Controlled InterruptionThe complaint is out of scope because it is a duplicate of an open complaint.1
Service Level AgreementThe complaint is out of scope because it is a duplicate of a closed complaint.8
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.2
Uniform Rapid Suspension (URS)The complaint is out of scope because it is about a requirement that is not applicable to the selected registry.1
Zone File AccessThe complaint is out of scope because it is a duplicate of an open complaint.19
The complaint is out of scope because the complainant did not provide the requested information.1
Out of Scope Category Total36

Complaint Volume & Closure Rate

Volume Trend

Mar-19Apr-19May-19Jun-19Jul-19Aug-19Sep-19Oct-19Nov-19Dec-19Jan-20Feb-20Mar-20
2244213019482705215515891616170215802579154713601747

Total Volume

Counts February 2020 March 2020
Total New1,3601,747
Total Closed1,3621,628

Closure Rates

Stage February 2020 March 2020
Received All
Target ≥ 55%
52%55%
Current Month25%36%
Before 1st Inquiry / Notice42%47%
Before 2nd Inquiry / Notice7%7%
Before 3rd Inquiry / Notice2%1%

ICANN Staff Average Turnaround Time

Measures February 2020 March 2020
Open to 1st Inquiry / Notice2.81.9
2nd WIP6.45.3
3rd WIP12.86.4
Formal Notices1.0-

Contractual Compliance Overall Process Turnaround Time

Measures February 2020 March 2020
Received to Closed30.523.4

Note: Average Turnaround Time is shown in business days.