Skip to main content

Prepare to Apply for a New gTLD

Preparation Checklist

The following information highlights key details applicants should consider before applying for a new generic top-level domain (gTLD) in the New gTLD Program: 2026 Round. The application submission period opens on 30 April 2026 and will close on 12 August 2026.

Before you begin, review the Applicant Guidebook. The Applicant Guidebook covers all requirements, evaluation criteria, fees, and timelines. If you have any questions before submitting an application, you can reach out to Global Support at globalsupport@icann.org. After you submit an application, you can send application-specific inquiries to ICANN through TAMS.

  1. Become familiar with the 2026 Round Resources page. It includes topic overviews and Frequently Asked Questions (FAQs) aligned to each stage of the Applicant Journey to help you prepare your responses before you apply through the TLD Application Management System (TAMS). Applicants who prepare their documentation and planned responses in advance will be better positioned to complete their application accurately and on time.
  2. Confirm you meet eligibility requirements. Only legal entities such as corporations, organizations, and institutions as well as governmental, non-governmental, and inter-governmental entities may apply for a new gTLD. For full eligibility requirements, see section 1.1 Pre-Submission Information of the Applicant Guidebook. For common eligibility questions, see the 2026 Round FAQs.
  3. Create an ICANN Account. Before you can access TAMS, you must register for an ICANN user account and enable multi-factor authentication. If you have ever signed up for an ICANN Public Meeting or another ICANN service, you already have an ICANN Account.

  4. Decide on your gTLD string. The 2026 Round supports the following application types: general, community, Geographic Name, Reserved Name, .Brand, IDN, variant of an existing gTLD, and variant of a new gTLD. In some cases, an application may be more than one of these types. For guidance on gTLD types and string selection, see 3.1.6 Application and String Types of the Applicant Guidebook.

    Note: Applications for exclusive use strings (closed generics) will not be approved. See section 3.1.7 Exclusive Use Strings (Closed Generics) of the Applicant Guidebook.

  5. Check that your string doesn't appear on the Blocked or Reserved Names Lists. See sections 3.1.8.1 Blocked Names Identification and 3.1.8.2 Reserved Names Identification of the Applicant Guidebook.
  6. Use the Name Collision Observatory to help assess the risk of name collision. Name collision refers to the situation in which a resource name that is intended to be resolved in one naming system is inadvertently resolved in a different naming system, potentially leading to unexpected behavior such as communication being disrupted or redirected from its intended recipient. It should be noted that the magnitude data for an applied-for string is only one of several factors that will be considered in the Name Collision Initial Assessment. Both quantitative data and qualitative aspects will be considered when assessing the risk associated with that string in the TLD application process. Applicants should not assume that if this tool indicates a low volume of queries for a string, the string will be assessed during the application process as safe to be delegated. For more information see section 7.7 Name Collision in the Applicant Guidebook and the Name Collision webpages.

  7. Gather your documentation. Prepare your technical, operational, and financial documentation before you start drafting your application in TAMS. Incomplete documentation might cause delays, so don't rush this step. For a complete list of new gTLD application questions, see Appendix 1 in the Applicant Guidebook.

    Note: If any supporting documents are not in English, for each document you must provide the original document, an English translation, and a certificate of translation accuracy. The certificate must be written in English and include the translator's qualifications; a statement confirming completeness and accuracy; identification of the document and source language; and the translator's name, signature, and date.

  8. Identify your Registry Service Provider (RSP). The list of evaluated RSPs is available on the RSP Application page. You may specify your RSP at any point before Application Evaluation through the Change Request process, but identifying one early will help you plan your application.

  9. Understand fees and payment. You must pay the full gTLD evaluation fee upon receipt of your invoice, and no later than seven days after the close of the application submission period. If your application includes more than four variant strings, additional fees apply. Depending on the type of application, conditional fees may apply, which will be invoiced at a later stage. Confirm your payment process and banking arrangements within your organization well in advance of the application submission.

    For fee details, see section 3.3 Fees and Payments in the Applicant Guidebook. For common questions, see the gTLD Evaluation Fee FAQs.

  10. Review the Terms and Conditions. You must agree to the Terms and Conditions before submitting your application. Read them in full before you begin.
  11. Plan your string strategy, including whether to designate a replacement string. Review your string for potential sensitivities such as terms related to religion, nationality, or regulated sectors like banking or pharmacy, which may attract scrutiny. For more information, see sections 3.1.6 Application and String Types and 5.1 Replacement Strings in the Applicant Guidebook.
  12. Prepare for the possibility of contention. If another applicant applies for the same or a confusingly similar string as yours, your application will be placed into a contention set. In the 2026 Round, contention must be resolved through replacement strings, Community Priority Evaluation (CPE), or an ICANN auction. For more information, see Module 5 Contention Set Resolution and 5.2.3.1 Prohibited Communications and Activities in the Applicant Guidebook.
  13. Become familiar with the 2026 Base Registry Agreement (RA), which outlines the rights and obligations of new gTLD registry operators and will serve as the form of contractual document between ICANN org and successful applicants in the New gTLD Program: 2026 Round. For common questions, refer to the Base RA FAQs or visit the Base Registry Agreement Homepage.