ICANN Contractual Compliance Dashboard for July 2024

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 July 2024 Closed before 1st
Inquiry / Notice
Consent To Display Registration Data24
Disclosure of gTLD Registration Data54
DNS Abuse and Other Types of Abuse429402
Domain Renewal/Redemption7455
Domain Suspension2314
Generic Registrar8042
Privacy/Proxy66
Registrar Data Escrow240172
Registration Data (service down)93
Registration Data Inaccuracy4429
Transfer116126
Uniform Domain-Name Dispute-Resolution (UDRP)136
REGISTRAR Total1,041863
  • 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

July 2024 Quantity Sent
Volume 1st Inquiry/Notice Sent148
Volume 2nd Inquiry/Notice Sent27
Volume 3rd Inquiry/Notice Sent17
Escalated Notice2
Volume Breach-
Volume Suspension-
Volume Termination-
Volume Contract Non-Renewal-
Volume Closed All - as of Current Month = 1021

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

Registrar Additional Information on Complaints Related to GAC Category 1 Safeguards

Details on GAC Category 1 Type Complaint Type July 2024
Highly Regulated (Safeguards 1-8)::EducationDNS Abuse and Other Types of Abuse1
Highly Regulated (Safeguards 1-8)::EducationDomain Renewal/Redemption1
Regulated (Safeguards 1-3)::Financial;Regulated (Safeguards 1-3)::Intellectual PropertyDomain Suspension1
Regulated (Safeguards 1-3)::Health and FitnessTransfer1
Regulated (Safeguards 1-3)::Intellectual PropertyDNS Abuse and Other Types of Abuse14
Regulated (Safeguards 1-3)::Intellectual PropertyDomain Suspension1
Regulated (Safeguards 1-3)::Intellectual PropertyGeneric Registrar2
Regulated (Safeguards 1-3)::Intellectual PropertyRegistration Data Inaccuracy1
Regulated (Safeguards 1-3)::Intellectual PropertyTransfer3
Regulated (Safeguards 1-3)::Professional ServicesRegistration Data Inaccuracy1
Total26

Registrar Complaints Processed in July 2024 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 Closed Inquiry/ Notice Total Inquires/ Notices in process Closure reason(s) for Inquiries/Notices
Disclosure of gTLD Registration Data
IP Lawyer/Brand Protection21The complaint is out of scope (1)2-The registrar demonstrated compliance.; Access to non-public Registration Data denied (1) The registrar corrected its noncompliance.; Registration Data disclosed (1)
Information Security Researcher-1The complaint is out of scope (1)--
Authorized Representative of Registrant--11The registrar corrected its noncompliance.; Registration Data disclosed (1)
Other11The complaint is out of scope (1)--
Registrant - Current1
UDRP/URS - Complainant11The complaint is out of scope (1)--
Other Complaint Types also including disclosure requests for gTLD Registration Data:
----
Consent To Display Registration Data
Registrant - Current24The complaint is out of scope (4)--
gTLD Registration Data - RDDS
Generic RegistrarInformation Security Researcher---1
Total7832

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

  • 1st Inquiry/Notice
  • 2nd Inquiry/Notice
  • 3rd Inquiry/Notice
  • 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.

*Compliance processes Notices/Inquiries for disclosure of gTLD Registration Data to ensure compliance with Appendix A, Section 4.1 of the Temporary Specification for gTLD Registration Data. Notices/Inquiries may be closed upon a registrar correcting an area of non-compliance or demonstrating compliance, regardless of whether access to Registration Data is granted or denied.

*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 how “the registrar corrected its noncompliance” include:

  • Registrar implemented changes to ensure it was providing reasonable access to non-public Registration Data per Section 4.1 of Appendix A.
  • Registrar responded to a request for access to non-public Registration Data and provided the requested Data or an explanation for denial.
  • 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 how “the registrar demonstrated compliance” include:

  • 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).

July 2024 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.

July 2024 Registrar Closed Complaints Summary

Closure Code Category # of Complaints
Resolved330
Out of Scope689
ICANN Issue2
Registrar Closed Complaints Total1,021

July 2024 Registrar Closed Complaints Detail by Category and by Complaint Type

Resolved

Complaint Types Closure Code Description # of Complaints
AuditThe contracted party provided a timeline and action plan for addressing deficiencies.3
The contracted party provided clarification to clear initial finding(s).10
The contracted party provided the requested data and documents.7
Disclosure of gTLD Registration DataThe registrar corrected its noncompliance.2
The registrar demonstrated compliance.1
DNS Abuse and Other Types of AbuseThe registrar demonstrated having reasonably and promptly investigated and appropriately responded to an abuse report.17
The registrar does not have actionable evidence to determine the domain name is being used for DNS Abuse.6
The registrar suspended or deactivated the domain name. This is a reasonable response to an abuse report.10
The registrar suspended/deactivated the domain name. This is an appropriate mitigation action to stop the use of the domain name for DNS Abuse.12
The registrar took appropriate mitigation action to disrupt the use of the domain name for DNS Abuse.3
The registrar took appropriate mitigation action, other than suspension, to stop the use of the domain name for DNS Abuse.2
Domain Renewal/RedemptionThe domain has been renewed with the same registrant.2
The registrar demonstrated compliance with the Expired Registration Recovery Policy (ERRP) requirements.2
The registrar demonstrated compliance.2
Domain SuspensionThe registrar demonstrated compliance.1
The registrar restored the domain.2
The registrar's deletion of the domain was compliant.3
Privacy/ProxyThe domain name in the complaint is not using a Privacy/Proxy provider.1
Registrar Data EscrowThe registrar completed its data escrow deposit.188
The registrar corrected its noncompliance.1
The registrar demonstrated compliance.6
Registration Data (service down)The registrar's WHOIS service is now compliant.3
Registration Data InaccuracyThe domain is suspended and the registrar is not required to address the WHOIS inaccuracy complaint.12
The WHOIS data has been updated.1
TransferThe registrar corrected its noncompliance.2
The registrar demonstrated compliance with its contractual requirements.3
The registrar demonstrated compliance.5
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 cannot be completed due to a transfer or registration within the past 60 days, or a change of registrant lock.1
The transfer cannot be completed due to a transfer within the past 60 days.1
The transfer cannot be completed due to evidence of fraud.3
The transfer has been completed.12
Uniform Domain-Name Dispute-Resolution (UDRP)The registrar demonstrated compliance.3
The registrar locked a domain subject to a Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding.2
Resolved Category Total330

Out of Scope

Complaint Types Closure Code Description # of Complaints
Consent To Display Registration DataThe complaint is out of scope because the complainant did not provide the requested information.4
Disclosure of gTLD Registration DataThe 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 is not a registrar.1
The complaint is out of scope because the complainant did not provide the requested information.1
DNS Abuse and Other Types of AbuseThe complaint is invalid or not actionable because there is no evidence of an abuse report filed with a registrar or registry.112
The 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.1
The complaint is out of scope because it is a duplicate of a closed complaint.6
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 incomplete or broad.6
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.33
The complaint is out of scope because the complainant did not provide the requested information.130
The complaint is out of scope because the domain is not registered.7
The domain is suspended and suspension is a reasonable response to the abuse report.24
The domain name is suspended or disabled and suspension is a mitigation action to stop DNS Abuse.72
Domain Renewal/RedemptionThe complaint is out of scope because it is a duplicate of an open complaint.4
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.45
Domain SuspensionThe 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.1
The complaint is out of scope because the complainant did not provide the requested information.12
Generic RegistrarThe 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 incomplete or broad.1
The complaint is out of scope because it is regarding a country-code top-level domain.15
The complaint is out of scope because the complainant did not provide the requested information.21
Privacy/ProxyThe 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 the complainant did not provide the requested information.3
Registrar Data EscrowThe complaint is out of scope because ICANN terminated the registrar's accreditation.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 registrar that is not within ICANN's contractual authority.1
Registration Data (service down)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
Registration Data InaccuracyThe 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.23
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 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.16
The complaint is out of scope because the complainant did not provide the requested information.94
The complaint is out of scope because the complainant is not the transfer contact for the domain.2
The complaint is out of scope because the unauthorized transfer was due to hijacking.1
Uniform Domain-Name Dispute-Resolution (UDRP)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.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.1
The complaint is out of scope because there is no Uniform Domain Name Dispute Resolution Policy (UDRP) proceeding.3
Out of Scope Category Total689

ICANN Issue

Complaint Types Closure Code Description # of Complaints
Registrar Data EscrowThe matter has been withdrawn due to an ICANN issue.2
ICANN Issue Category Total2

Registries

Registry Complaint Volume & Distribution

Complaint Type July 2024 Closed before 1st
Inquiry / Notice
Code of Conduct70
DNS Abuse2124
Generic Registry11
Registry Data Escrow3724
Zone File Access13
REGISTRY Total6752

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

July 2024 Quantity Sent
Volume 1st Inquiry/Notice Sent4
Volume 2nd Inquiry/Notice Sent3
Volume 3rd Inquiry/Notice Sent-
Escalated Notice2
Volume Breach2
Volume Termination-
Volume Contract Non-Renewal-
Volume Closed All - as of Current Month = 53

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 July 2024
Regulated (Safeguards 1-3)::Health and FitnessRegistry Data Escrow1
Total1

July 2024 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.

July 2024 Registry Closed Complaints Summary

Closure Code Category # of Complaints
Resolved26
Out of Scope27
ICANN Issue-
Registry Closed Complaints Total53

July 2024 Registry Closed Complaints Detail by Category and by Complaint Type

Resolved

Complaint Types Closure Code Description # of Complaints
DNS AbuseThe registry suspended/deactivated the domain name. This is an appropriate mitigation action to contribute to stopping the use of the domain name for DNS Abuse.1
Registry Data EscrowICANN received the required registry data escrow notification.24
Zone File AccessThe request for zone file access was already approved by the registry operator at the time of processing the complaint.1
Resolved Category Total26

Out of Scope

Complaint Types Closure Code Description # of Complaints
DNS AbuseThe complaint is invalid or not actionable because there is no evidence of an abuse report filed with a registrar or registry.13
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 the domain is not registered.1
The domain name is suspended or disabled and suspension is a mitigation action to stop DNS Abuse.3
The registry operator is not the best-equipped party to review and take appropriate, proportionate, mitigation action in the particular case.1
The reported activity is not DNS Abuse (phishing, pharming, botnets, malware or spam as a delivery mechanism for the other four types of DNS Abuse.) Therefore, DNS Abuse requirements are not applicable.1
Generic RegistryThe complaint is out of scope because it is regarding a country-code top-level domain.1
Zone File AccessThe complaint is out of scope because the complainant did not provide the requested information.2
Out of Scope Category Total27

Complaint Volume & Closure Rate

Volume Trend


Total Volume

Counts June 2024 July 2024
Total New1,1621,108
Total Closed1,3371,074