Skip to main content

Submitting a Complaint to ICANN Contractual Compliance

To submit a complaint, select the form next to the issue which best describes your concern in the chart below. Before submitting your complaint, please read the information on this page in its entirety.

ICANN has executed certain agreements with registrars and registry operators. ICANN's Contractual Compliance authority is limited to the obligations set forth in these agreements. These agreements are the Registrar Accreditation Agreement, the Registry Agreements and the Consensus Policies. If your issue is outside of this contractual scope or if it involves a party over whom ICANN has no compliance enforcement powers, ICANN will provide you with alternative avenues you may want to pursue.

Additional information on how to submit complaints concerning requests for access to non-public registration data can be found here.

Information regarding existing policies and requirements, and ongoing policy development work involving Domain Name Registration Data is available here.

The Registration Data associated with a domain name may be available by performing a search here.

ICANN has no contractual authority to address complaints involving country code top-level domains (ccTLDs), such as .us, .eu, .ac, or domain names registered under a ccTLD (e.g.,, ICANN does not accredit registrars or set policy for ccTLDs and has no contractual authority to take compliance action against ccTLD operators. For inquiries and issues involving ccTLDs, you may wish to contact the relevant ccTLD manager using the contact details at This page will also help you determine which top-level domains (TLDs) are country codes (outside of ICANN's scope) and which ones are generic (within ICANN's scope).

ICANN does not have contractual authority or the technical ability to return a lost domain name to you. Additional information on lost domain names can be found at

For information about the process and approach used by ICANN Contractual Compliance to address complaints, please visit

The information provided to ICANN via the complaint forms is subject to Section 2 of ICANN's Privacy Policy.

Issue Additional information & Submit Complaint

A registrar's failure to:

  • Display abuse contacts and procedures.
  • Investigate and respond to an abuse report involving a domain name registered with the registrar.
  • Take mitigation action(s) to stop or disrupt the use of a domain name for DNS Abuse (malware, botnets, phishing, pharming, and spam when spam is used to deliver any of the other four types of DNS Abuse).

A registry operator's failure to:

  • Display abuse contact.
  • Take mitigation action(s) to contribute to stopping or disrupting the use of a domain name for DNS Abuse (malware, botnets, phishing, pharming, and spam when spam is used to deliver any of the other four types of DNS Abuse).

Abuse/DNS Abuse (Registrar)






DNS Abuse (Registry that operates the TLD)

The transfer of a domain name to a different registrar and/or registrant


The renewal and/or redemption of a domain name


The Registration Data associated with a domain name

Registration Data is inaccurate or missing

Request for disclosure of Registration Data by a third party with legitimate interest was denied or not responded to

Registrant requested and consented to the display of their own Registration Data, but it is not displayed

The suspension or deletion of a domain name for which I am or was the holder

Domain name remains suspended or deleted even after responding to Registration Data verification inquiries

The service through which a registrar or registry operator is displaying Registration Data

The WHOIS/RDAP service is not operative

Dispute Resolution Policies & Procedures

Uniform Domain-Name Dispute-Resolution Policy (UDRP)

Uniform Rapid Suspension System (URS)

Public Interest Commitments Dispute Resolution Procedure (PICDRP)

Registry-Restriction Dispute Resolution Procedure (RRDRP)

Trademark Post-Delegation Dispute Resolution Procedure (Trademark PDDRP)

A Privacy/Proxy registration or service


Access to the zone file of a TLD

Zone File Access

A name that has been or must have been reserved by the registry operator

Reserved Names

A registry operator not abiding by the code of conduct of its Registry Agreement

Code of Conduct

A contractual compliance issue not identified above

Generic Registrar Complaint

Generic Registry Complaint

Domain Name System
Internationalized Domain Name ,IDN,"IDNs are domain names that include characters used in the local representation of languages that are not written with the twenty-six letters of the basic Latin alphabet ""a-z"". An IDN can contain Latin letters with diacritical marks, as required by many European languages, or may consist of characters from non-Latin scripts such as Arabic or Chinese. Many languages also use other types of digits than the European ""0-9"". The basic Latin alphabet together with the European-Arabic digits are, for the purpose of domain names, termed ""ASCII characters"" (ASCII = American Standard Code for Information Interchange). These are also included in the broader range of ""Unicode characters"" that provides the basis for IDNs. The ""hostname rule"" requires that all domain names of the type under consideration here are stored in the DNS using only the ASCII characters listed above, with the one further addition of the hyphen ""-"". The Unicode form of an IDN therefore requires special encoding before it is entered into the DNS. The following terminology is used when distinguishing between these forms: A domain name consists of a series of ""labels"" (separated by ""dots""). The ASCII form of an IDN label is termed an ""A-label"". All operations defined in the DNS protocol use A-labels exclusively. The Unicode form, which a user expects to be displayed, is termed a ""U-label"". The difference may be illustrated with the Hindi word for ""test"" — परीका — appearing here as a U-label would (in the Devanagari script). A special form of ""ASCII compatible encoding"" (abbreviated ACE) is applied to this to produce the corresponding A-label: xn--11b5bs1di. A domain name that only includes ASCII letters, digits, and hyphens is termed an ""LDH label"". Although the definitions of A-labels and LDH-labels overlap, a name consisting exclusively of LDH labels, such as"""" is not an IDN."