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. example.us, example.eu, example.ac). 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 https://www.iana.org/domains/root/db. 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 https://www.icann.org/resources/pages/lost-domain-names.

For information about the process and approach used by ICANN Contractual Compliance to address complaints, please visit https://www.icann.org/resources/pages/approach-processes-2012-02-25-en.

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	Transfer
The renewal and/or redemption of a domain name	Renewal/Redemption
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	Privacy/Proxy
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