ICANN Contractual Compliance Dashboard for March 2021

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 2021 Closed before 1st
Inquiry / Notice
Abuse273235
Consent To Display Registration Data6-
Disclosure of gTLD Registration Data166
Domain Renewal/Redemption156126
Domain Suspension2220
Generic Registrar7033
Privacy/Proxy4-
Registrar Data Escrow13-
Registrar Fees21
Registration Data (service down)1311
Registration Data Inaccuracy9561
Transfer826263
Uniform Domain-Name Dispute-Resolution (UDRP)88
Total1,504764
  • The complaint type “WHOIS Inaccuracy” has been renamed “Registration Data Inaccuracy”. All complaints processed by Compliance in this complaint type are now reported under Registration Data Inaccuracy.
  • Some Complaint Types are from the legacy system.
  • “Closed before 1st Inquiry/Notice” represents complaints closed during the reporting period and can include complaints received in a prior period.

Compliance Process Volume

March 2021 Quantity Sent
Volume 1st Inquiry/Notice Sent159
Volume 2nd Inquiry/Notice Sent31
Volume 3rd Inquiry/Notice Sent9
Escalated Notice-
Volume Breach-
Volume Suspension-
Volume Termination-
Volume Contract Non-Renewal-
 
Volume Closed All - as of Current Month = 905

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

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, phishing110
Malware, botnet37
Spam64
Counterfeiting32
Fraudulent, deceptive practices162
Pharmaceutical17
Trademark or copyright infringement102
Abuse contact / procedures information50
Other61

Note: Activities are selected by the complainant with the submission and are not determined by ICANN Contractual Compliance. One single complaint can include more than one activity; therefore, the sum of the activities above will not necessarily equal the total of Abuse complaints received within the month.

Registrar Additional Information on Complaints Related to GAC Category 1 Safeguards

Details on GAC Category 1 Type Complaint Type March 2021
Regulated (Safeguards 1-3)::EnvironmentalTransfer1
Regulated (Safeguards 1-3)::Environmental;Regulated (Safeguards 1-3)::Health and FitnessRegistration Data Inaccuracy1
Regulated (Safeguards 1-3)::FinancialAbuse1
Regulated (Safeguards 1-3)::FinancialDomain Renewal/Redemption1
Regulated (Safeguards 1-3)::Intellectual PropertyAbuse1
Regulated (Safeguards 1-3)::Intellectual PropertyGeneric Registrar1
Total6

Registrar Complaints Processed in March 2021 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 3rd Inquiry/ Notice Closed Inquiry/Notice Total Inquiries/ Notices in process Closure reason(s) for Inquiries/Notices
Disclosure of gTLD Registration DataIP Lawyer/Brand Protection94ccTLD (1)
Duplicate complaint (open) (1)
Requested evidence not provided (2)
621314Registrar demonstrated compliance (2)
Balancing Test Applied, Access to Non-Public Registration Data Denied (1)
LEA, Consumer Protection, Government or Data Protection Agency1-1---1
Registrant - Current1------
Registrant - Former1-- ----
Other42Duplicate complaint (open) (1)
Requested evidence not provided (1)
-----
Other Complaint Types also including disclosure requests for gTLD Registration Data:
AbuseIP Lawyer/Brand Protection-----1-Registrar demonstrated compliance (1)
Registration Data (service down)Other-1Requested evidence not provided (1)-----
Registration Data InaccuracyIP Lawyer/Brand Protection1------
Consent To Display Registration Data
Authorized Representative3------
Registrant - Current2-----1
Non-Governmental Organization1------
gTLD Registration Data - RDDS
Generic RegistrarOther1-1---2
Information Security Researcher--1--1-Registrar corrected its noncompliance (1)
ICANN Compliance4-4--38Registrar corrected its noncompliance (3)
Registration Data (service down)Information Security Researcher-2Requested evidence not provided (1)
Registrar compliant at submission (1)
-----
Legacy Ticketing System:
Third Party Access-----43Registrar corrected its noncompliance (4)
RDDS-----13Registrar corrected its noncompliance (1)
Total28913211332

*The following columns have been removed from the above table because they had no complaint counts for the reported month:

  • Escalated Notice
  • Breach Notice
  • Suspension Notice
  • Termination Notice

*In the table above, the number of Reporter Complaints received may not equal the total number of closed Reporter Complaints plus the number of Notices/Inquiries sent, for any of the following reasons:

  • Compliance actions took place in different months. The table reflects activity per month. Compliance may send Inquiries, Notices or Closures in different months from which it received the related complaint. For example, Compliance may receive a Reporter Complaint in one month, which is closed or results in an Inquiry/Notice sent to a contracted party the following month. Further, new Reporter Complaints may be pending review and processing by Compliance and therefore, only reported as received in the reported month.
  • The reporter misfiled the complaint. A reporter may submit a complaint using the form for Disclosure of gTLD Registration Data or Consent to Display, which after review, Compliance determines is within the scope of ICANN's contractual authority, but should be processed under a different complaint type.
  • Compliance bundled multiple complaints into a single Inquiry/Notice. A single compliance Inquiry or Notice may be based on one or multiple Reporter Complaints received by compliance, or on Compliance’s own observations of areas of non-compliance.

*Reporter type refers to the capacity in which the reporter submitted the complaint, which is selected by the reporter at the time of submission and is not determined by Compliance.

*Out of scope complaints involving disclosure for gTLD Registration Data may include for example, requests for personal data of privacy or proxy registrant customers, requests for Registration Data that is available in the public Registration Data Directory Services (not redacted), or failure to provide evidence of request made to the contracted party.

*The 'total Inquiries/Notices in process' reflects the number pending during the month, which account for those in 1st, 2nd, or 3rd Inquiry/Notice status, including those for which Compliance may not have sent additional Inquiries or Notices due to ongoing remediation for example.

*For additional details of complaints processed in the legacy ticketing system, please refer to the Monthly Dashboard for May 2020 through August 2020 available here: https://features.icann.org/compliance/dashboard/report-list

*Examples of “the registrar corrected its noncompliance” scenarios:

  • Registrar implemented changes to ensure it was providing reasonable access to non-public Registration Data per Section 4.1 of Appendix A.
  • Registrar implemented changes to ensure it was providing full Registration Data to UDRP providers upon notification of a complaint per Section 1.1 of Appendix E.
  • Registrar implemented changes to the display of Registration Data in its RDDS to address the concerns raised in the compliance inquiry/notice (e.g., registrar is now providing an anonymized email address or a web form to facilitate email communication with the relevant contact).

*Examples of “the registrar corrected its noncompliance” scenarios:

  • Registrar implemented changes to ensure it was providing reasonable access to non-public Registration Data per Section 4.1 of Appendix A.
  • Registrar implemented changes to ensure it was providing full Registration Data to UDRP providers upon notification of a complaint per Section 1.1 of Appendix E.
  • Registrar implemented changes to the display of Registration Data in its RDDS to address the concerns raised in the compliance inquiry/notice (e.g., registrar is now providing an anonymized email address or a web form to facilitate email communication with the relevant contact).

*Examples of “the registrar demonstrated compliance” scenarios:

  • Registrar demonstrated that it previously reviewed and responded to request(s) for access to non-public Registration Data per the requirements in Section 4.1 of Appendix A.
  • Registrar demonstrated that it displays Registration Data in its RDDS pursuant to the requirements of the RAA and Sections 2 and 3 of Appendix A (e.g. registrar demonstrated that it obtained Consent from the registrant to display non-redacted Registration Data in the RDDS, otherwise subject to redaction requirements pursuant to Section 2.1)

March 2021 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 2021 Registrar Closed Complaints Summary

Closure Code Category # of Complaints
Resolved170
Out of Scope735
ICANN Issue-
Registrar Closed Complaints Total905

March 2021 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.35
The registrar demonstrated compliance.1
The registrar published the required abuse contact information.1
The registrar responded to the abuse report.19
Disclosure of gTLD Registration DataThe registrar demonstrated compliance.2
Domain Renewal/RedemptionThe domain has been renewed with the same registrant.1
The registrar corrected its Expired Registration Recovery Policy (ERRP) noncompliance.1
The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements.6
The registrar demonstrated compliance.2
Domain SuspensionThe domain is no longer suspended.4
The registrar's deletion of the domain was compliant.4
Generic RegistrarThe domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint.1
The registrar corrected its noncompliance.9
Registrar Data EscrowThe registrar completed its data escrow deposit.6
Registration Data (service down)The registrar demonstrated compliance.1
The registrar's WHOIS service was compliant at the time the complaint was received.3
The registrar's WHOIS service was restored.4
Registration Data InaccuracyThe domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint.22
The registrar corrected its noncompliance.2
The WHOIS data has been updated.20
TransferThe registrar corrected its noncompliance.1
The registrar demonstrated compliance with the change of registrant requirements.1
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.1
The transfer has been completed.8
The transfer was denied because of a court order received by the registrar.1
Uniform Domain-Name Dispute-Resolution (UDRP)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.9
The registrar verified the domain with the Uniform Domain Name Dispute Resolution Policy (UDRP) provider.2
Resolved Category Total170

Out of Scope

Complaint Types Closure Code Description # of Complaints
AbuseThe complaint is out of scope because customer service issues are outside of ICANN's contractual authority.1
The complaint is out of scope because ICANN does not process complaints regarding website content.9
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.7
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 an illegal activity that is outside of ICANN's contractual authority.2
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.3
The complaint is out of scope because it is regarding a country-code top-level domain.26
The complaint is out of scope because spam is outside of ICANN's contractual authority.2
The complaint is out of scope because the complainant did not provide the requested information.68
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.81
Disclosure of gTLD Registration DataThe 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.3
Domain Renewal/RedemptionThe 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.6
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.96
The complaint is out of scope because the domain is not registered.1
The complaint is out of scope because the registrar voluntarily terminated its ICANN accreditation.1
Domain SuspensionThe complaint is out of scope because the complainant did not provide the requested information.16
Generic RegistrarThe 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.1
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.4
Registrar FeesThe complaint is out of scope because the registrar voluntarily terminated its ICANN accreditation.1
Registration Data (service down)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 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 the complainant did not provide the requested information.4
Registration Data InaccuracyThe 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.3
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.51
TransferThe 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.16
The complaint is out of scope because it is regarding a country-code top-level domain.88
The complaint is out of scope because the complainant did not provide the requested information.153
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 registrar voluntarily terminated its ICANN accreditation.2
Uniform Domain-Name Dispute-Resolution (UDRP)The complaint is out of scope because it is a duplicate of a closed complaint.1
The complaint is out of scope because the complainant did not provide the requested information.5
Out of Scope Category Total735

Registries

Registry Complaint Volume & Distribution

Complaint Type March 2021 Closed before 1st
Inquiry / Notice
Abuse Contact Data3-
Code of Conduct3-
Generic Registry41
Registry Data Escrow42-
Registry Fees2-
Reserved Names3-
Zone File Access8316
Total14017

Note:

  • Some Complaint Types are from the legacy system.
  • ”Closed before 1st Inquiry/Notice” represents complaints closed during the reporting period and can include complaints received in a prior period.

Compliance Process Volume

March 2021 Quantity Sent
Volume 1st Inquiry/Notice Sent15
Volume 2nd Inquiry/Notice Sent1
Volume 3rd Inquiry/Notice Sent3
Escalated Notice1
Volume Breach-
Volume Termination-
Volume Contract Non-Renewal-
 
Volume Closed All - as of Current Month = 18

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 2021
Highly Regulated (Safeguards 1-8)::Corporate IdentifiersZone File Access1
Regulated (Safeguards 1-3)::CharityZone File Access1
Regulated (Safeguards 1-3)::ChildrenRegistry Data Escrow1
Total3

March 2021 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 2021 Registry Closed Complaints Summary

Closure Code Category # of Complaints
Resolved16
Out of Scope2
ICANN Issue-
Registry Closed Complaints Total18

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

Resolved

Complaint Types Closure Code Description # of Complaints
Zone File AccessThe registry demonstrated compliance.1
The request for zone file access was already approved by the registry operator at the time of processing the complaint.15
Resolved Category Total16

Out of Scope

Complaint Types Closure Code Description # of Complaints
Generic RegistryThe complaint is out of scope because it is a duplicate of an open complaint.1
Zone File AccessThe complaint is out of scope because it is a duplicate of an open complaint.1
Out of Scope Category Total2

Complaint Volume & Closure Rate

Volume Trend

Mar-20Apr-20May-20Jun-20Jul-20Aug-20Sep-20Oct-20Nov-20Dec-20Jan-21Feb-21Mar-21
1747163915841362161314861205111112172016209519281644

Total Volume

Counts February 2021 March 2021
Total New1,9281,644
Total Closed822923