Skip to main content

Process for Reporting Vulnerabilities Within ICANN Organization Online Services

Public Vulnerability Disclosure Program

ICANN has partnered with HackerOne to provide a method to report vulnerabilities for our online services.

ICANN HackerOne portal is located here:

This program is currently open only to invited users, but will be expanded to all HackerOne users at a later date.

Alternatively, please submit a detailed description of the vulnerability to:

Reports may be submitted using this PGP public key.

For emailed vulnerability reports, please include:

  • Full description of the vulnerability being reported including the exploitability and impact
  • Document all steps required to reproduce the exploit of the vulnerability
  • Provide all:
    • URL(s)/application(s) affected in the submission (even if a code snippet\video was also provided).
    • IPs that were used while testing.
    • The user account (if any) used for the Proof of Concept (PoC).
    • Include all files that were attempted to upload.
    • Provide the complete PoC  with the submission (e.g., a Remote Code Execution that does not change files, upload only "hello world" test files, etc.)
    • Save and attach all logs to the submission.

Responsible Disclosure Guidelines:

In researching vulnerabilities with ICANN org online services, you may not engage in testing that:

  • results in a degradation of ICANN systems,
  • results in you, or any third party, accessing, storing, sharing or destroying ICANN or customer data, or
  • may impact the ICANN community, such as denial of service, social engineering or spam.

Responsible disclosure of a vulnerability consists of providing notification to ICANN in lieu of publicly releasing the details and providing a reasonable timeframe for ICANN to fix the issue. When a potential vulnerability is reported to ICANN through responsible means, ICANN will strive to confirm its existence in a timely manner, evaluate the risk to ICANN and the community and, if necessary, adopt the appropriate corrective timeline with actions to remediate. ICANN sincerely appreciates responsible disclosure of vulnerabilities from all parties, and will make efforts to provide appropriate recognition of those individuals who follow ICANN's disclosure guidelines.

Prohibited Actions:

  • Uploading files that allow arbitrary commands ( e.g., a webshell).
  • Modifying any files or data, including permissions.
  • Deleting any files or data.
  • Interrupting normal operations (e.g., triggering a reboot).
  • Creating and maintaining a persistent connection to the server.
  • Intentionally viewing any files or data beyond what is needed to prove the vulnerability.
  • Failing to disclose any actions taken or applicable required information.

Failure to meet the above conditions and requirements may be considered a breach of responsible disclosure guidelines and eliminate any potential recognition of the submitted research contribution.

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."