Skip to main content
Resources

ICANN Complaints Office

Overview

The Complaints Office is a function within the ICANN org that:

  • Provides a centralized location to submit complaints related to the ICANN org.
  • Receives complaints, researches them, collects facts, reviews, analyzes, and resolves issues as openly as possible.
  • Helps the ICANN org build on its effectiveness, and contributes to increased transparency from the Org.
  • Aggregates the data from complaints to identify and solve for operational trends that should be improved.

The Complaints Office handles complaints regarding the ICANN org that don't fall into an existing complaints mechanism, such as Contractual Compliance, Request for Reconsideration and the Ombudsman. This may include complaints about how a request has been handled, a process that appears to be broken, insufficient handling of an issue, or something that may be an indication of a systemic issue, among other things.

The Complaints Office reviews verifiable information to ensure recommendations and resolutions are based in fact. It strives to be open and transparent, responsive and accountable to all parties, and to make recommendations that are constructive and actionable. Above all else, the Complaints Office acts with the utmost integrity in service of ICANN's mission.

Submitting a Complaint

Anyone wishing to submit a complaint related to the ICANN org may do so by completing this web-form. When submitting a complaint, please be sure to include all relevant information. Once a complaint is received, it will be reviewed to ensure it falls within the scope of the office and you will be notified of next steps via email. Out of scope submissions are forwarded and responded to by ICANN's Global Support Center team who has expertise in navigating the entire ICANN org and will get the submitter the information and/or assistance they are looking for.

Submissions that fall within the scope of the Complaints Office, will be handled in the following stages:

  • Receive, Acknowledge, and Publish:
    • Acknowledge receipt of the complaint.
    • Remind submitter that the process is transparent, that the complaint will be published on the Complaints Office Report page with personal information redacted (as appropriate), and provide estimated timeframe for next update.
  • Evaluate and Consider:
    • The Complaints Officer interviews ICANN org employees with subject-matter expertise, collects, reviews and analyzes facts, researches appropriate data, and works with management to determine if improvements are warranted and if so—what can be done.
    • The Complaints Officer is independent and will make recommendations based on research and facts.
    • If there is disagreement regarding improvements between the Complaints Officer and relevant department executives, the issue is escalated to the Complaints Officer's supervisor and the ICANN CEO.
  • Response Drafting:
    • Once a complaint is fully researched, a path forward is identified.
    • A path forward can be many things, for example: improvements to a process, an educational opportunity, no improvements can be implemented, among others.
    • The path forward is agreed upon and the Complaints Officer drafts a response to the submitter.
  • Response Issued and Published:

Resources about the Complaints Office

Terms and Conditions for Submission to the Complaints Office

Submitted complaints will be handled in accordance with the ICANN bylaws and the ICANN Privacy Policy. By submitting this web-form you acknowledge that the complaints process shall operate to the maximum extent feasible in an open and transparent manner and consistent with procedures designed to ensure fairness. Except as noted above, information you submit is subject to being published on the ICANN website.

By submitting my personal data, I agree that my personal data will be processed in accordance with the ICANN Privacy Policy, and agree to abide by the website Terms of Service.

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""icann.org"" is not an IDN."