Get Your TLD Strategy

Got questions about new gTLDs? You’re in the right place.

Whether you’re applying for your first TLD, navigating the ICANN process, or exploring registry service providers, this FAQ covers it all.  Browse by topic to get clear, expert-backed answers on what matters most.

Can’t find what you’re looking for?  Email us and we’ll be happy to help.

General FAQ

The next round of ICANN New gTLD applications is expected to open in April 2026. The application window will be open for a limited period of 12-15 weeks.

Any individuals, organizations, or entities with a legitimate interest in operating a gTLD can apply.  This includes businesses, non-profits, governments, and other organizations.

Applicants can apply for the following types of TLDs:

  • Generic TLDs:  These are open to a wide range of applicants and cover all types of domain names, such as .COM, .ORG, .SHOP, and others.
  • Brand TLDs:  Reserved for companies or brands to create their own domains, such as .APPLE or .GOOGLE.
  • Community TLDs:  Intended for specific communities or sectors, such as .MUSIC for the music industry or .SPORT for sports-related organizations.
  • Geographic TLDs:  Representing geographic locations, such as .LONDON or .NYC.
  • Internationalized Domain Name (IDN) TLDs:  TLDs in non-Latin scripts (e.g., .中国 for China).
  • IDN Variant TLDs:  Different variations of the same string in different scripts or languages.

Applicants must demonstrate:

  • Technical Capability:  The ability to manage a gTLD registry and ensure the technical stability of the system
  • Financial Capability:  The financial resources to operate a registry successfully
  • Operational Capability:  The operational experience or plans in place to support the gTLD registry

Additionally, community-based applications must provide evidence of community support and clearly define their community.

Yes, applicants can apply for multiple new gTLDs.  However, each application will require a separate evaluation fee and must meet the necessary eligibility requirements.  you can submit multiple applications for different strings under the same entity as long as they comply with ICANN rules.

If multiple applicants apply for the same string, a contention set is formed.  ICANN will attempt to resolve contention through methods such as Community Priority Evaluation (CPE) or an ICANN Auction.  See contention sets.

The application process is extensive and includes evaluation, contracting, and delegation.  It typically takes several months to complete.  Applicants should prepare for a multi-year journey – from submission to successful delegation of their gTLD.

Application Fees FAQ

The ICANN gTLD evaluation fee is $227,000 USD per application.  This fee covers all required evaluations, including Extended Evaluation if applicable.  It helps fund ICANN’s New gTLD Program, ensuring the program operates independently without relying on other funding sources.  Payment is due within seven days after the application window closes.  Late payments may result in the application being canceled.

Yes. The Applicant Support Program (ASP) offers a 75% – 85% fee reduction for eligible applicants, lowering the fee to between $34,500 and $56,750 USD.

Applicants requesting variant strings – including registry operators from the 2012 round applying for variants of their existing gTLD – can include up to four variants at no additional cost. If more than four variants are requested, each additional string requires the full evaluation fee.

ICANN may require applicants to undergo conditional evaluations for specific status or exemptions. These evaluations are billed separately, with fees depending on the evaluation type. For example:

  • Brand TLD Eligibility: $500 USD 
  • Geographic Name Review:  $18,000 – $25,000 USD
  • Community Priority Evaluation (CPE):  Estimated between $50,000 – $80,000 USD
  • Name Collision High-Risk Mitigation Plan:  Estimated between $100,000 – $150,000 USD

Fees for conditional evaluations are due when the evaluation occurs, and applicants are notified of the amounts before confirming participation.

If the gTLD evaluation fee is not paid within seven days of the close of the application period, your application will generally be canceled and will not be processed further.  In rare cases, if an applicant is awaiting ASP evaluation, their application may be put on hold until the fee is determined.

Back to FAQ menu

Application Refunds FAQ

There are three refund windows based on when you withdraw or terminate your application:

  1. First Window (65% Refund):  From receipt of the evaluation fee until 10 days after String Confirmation Day
  2. Second Window (35% Refund):  From 11 days after String Confirmation Day until the start of Application and Applicant Evaluation
  3. Third Window (20% Refund):  From the start of Application and Applicant Evaluation until you sign a Registry Agreement with ICANN

If your application is terminated by ICANN, you will be notified and can request a refund within 90 days.  The refund will depend on the refund window and your application status, so it’s important to act within this time frame.

Yes, you may be eligible for a refund in these situations:

  • Material Changes:  If ICANN makes significant changes to the Applicant Guidebook or program processes that affect your evaluation
  • High-Risk Name Collision:  If your string is flagged as high-risk and you withdraw within 90 days, you can get a 65% refund (unless it’s for strings like .HOME, .CORP, or .MAIL)

Yes, if your gTLD application is blocked due to IDN ccTLD string similarity and you have government support or non-objection, you’re eligible for a full refund if your application was submitted before the related ccTLD evaluation.

If the number of applications exceeds 1,000 (ICANN’s cost recovery target), applicants can opt into a volume refund.  Refunds are proportional to the total number of applications submitted once ICANN recovers its estimated $70 million USD in implementation costs.

  • To maximize your refund:

    • Withdraw early to secure a larger refund
    • Submit your refund request on time (especially within the 90-day window for terminated applications)
    • Stay informed about any material changes in the Applicant Guidebook that may make you eligible for a refund

Replacement String FAQ

Think of a Replacement String as your safety net in the gTLD application process! It’s a backup string you can designate alongside your main choice.  If there’s any conflict or contention with other applicants, you can switch to your backup – keeping things moving smoothly!

If you choose to designate a Replacement String, this will have to be included with your gTLD application submission.  Once it’s in, that’s your choice – no changes allowed.

Great question! A Replacement String is your secret weapon for sidestepping contention drama.  If your primary string runs into competition, having a backup lets you pivot quickly – keeping your application on track and minimizing delays.  Just note: if your replacement string is also in a contention set, you won’t be able to use it. In that case, you’re back in the ring with everyone else.

Nope – just one shot at a backup!  Each application gets a single replacement string. It’s your one-and-only lifeline for your primary applied-for string, so choose wisely!

You’ll have the opportunity to switch to your replacement string during the 14-day Replacement Period, which begins after Reveal Day (when ICANN publishes the list of applications).  If your original string is in contention with another applicant’s, you can decide to use the replacement string during this period.

If you don’t act during the Replacement Period, you’ll remain with your original applied-for string.  Once the Replacement Period ends, no more changes can be made, so it’s all about timing.

No, once you’ve chosen your replacement string and ICANN finalizes the list, you can’t switch back to your original applied-for string.  The replacement string becomes your official applied-for string for the rest of the process.

Yes, even after choosing a replacement string, you may still face issues like contention if the replacement string is similar to another applicant’s.  It’s important to choose a replacement string that minimizes these risks, such as avoiding singular/plural variations.

Back to FAQ menu

String Contention FAQ

A contention set is a group of applied-for strings that are in conflict because they are either identical, variants, singular/plural forms, or similar. Contention occurs when strings are:

  • Identical (e.g., two applicants for .EXAMPLE)

  • Variants of each other (e.g., .EXAMPLE and .EXAMPLE1)

  • Singular/Plural versions of the same word (e.g., .DOG and .DOGS)

  • Visually/Phonetically similar to another string.

  • Direct Contention: Happens when strings are identical or variants of each other. For example, two applicants applying for .EXAMPLE are in direct contention.
  • Indirect Contention: Occurs when strings are in contention with other strings but not directly with each other. For example, if .EXAMPLE and .EXAMPLES are both in contention with .EXAMPL, then .EXAMPLE and .EXAMPLES are in indirect contention.

In some cases of indirect contention, multiple applications may be allowed to proceed if their strings don’t directly conflict. For example, if one application prevails, others in the indirect contention set could still move forward, provided no direct string similarity exists.

Contention can be resolved through two main methods:

  1. Community Priority Evaluation (CPE): Available to community-based applications. If the community application meets certain criteria, it receives priority over other applications in the same contention set. If more than one community applicant wins the CPE, they may go to auction.
  2. ICANN Auction: If CPE doesn’t resolve the contention (or doesn’t apply), applicants will proceed to an auction to determine the winner.

No!  ICANN strictly prohibits private resolution of contention sets. Applicants cannot negotiate settlements, share information about strategies, or make deals outside of the official processes.  This ensures a fair and transparent resolution of contention.

To reduce the risk of contention:

  • Choose a unique string that’s less likely to conflict with others
  • Avoid submitting strings that could be singular/plural versions of popular words
  • Consider using a replacement string early in the process to have a backup option

ICANN Auction FAQ

The ICANN Auction is the final method used to resolve string contention when multiple applicants apply for the same gTLD string.  The auction uses an ascending-clock, second-price format, where the price increases in timed intervals.  The last bidder remaining wins, but they pay the second-highest bid, ensuring the price reflects market value.

For the 2026 round, ICANN has eliminated private resolutions and private auctions. All contention sets must go through official ICANN processes, including Community Priority Evaluation or the ICANN Auction. 

Contention sets can proceed to auction if they meet these conditions:

  • Completed String Evaluation
  • Resolved Objections and Appeals
  • Resolved Evaluation Challenges
  • Completed CPE (if applicable)
  • No Open Change Requests or Accountability Issues

Applicants will be notified 30 days before their auction date.

Applicants who receive support through the Applicant Support Program (ASP) are eligible for a 35% discount on the winning bid amount, capped at $1.75 million USD per application.  This helps supported applicants increase their chances in the auction.

The proceeds from the auction are used by ICANN to cover operational costs and support the gTLD program, contributing to the development and sustainability of the domain name system. The funds are not redistributed to applicants.

In the 2012 round, ICANN resolved 16 contention sets through auctions. Winning bid prices varied widely, showing the importance of evaluating your string’s market value and preparing for a competitive auction. Be ready for potential high bids if your string is highly sought after.

  • Plan Financially: Prepare a maximum bid strategy and set a budget.
  • Leverage ASP: If eligible, apply for Applicant Support to get bid credits.
  • Monitor Timelines: Keep track of auction schedules and the 30-day notice.
  • Research Auction Prices: Understand your string’s demand and be prepared for competition.
Back to FAQ menu

Prioritization Draw FAQ

The Prioritization Draw is a process that determines the Priority Number of applications, which dictates the order in which ICANN processes them.  It is expected to be held no later than 30 days after String Confirmation Day.  The draw is a live event where each application will be randomly assigned a Priority Number, and this number will determine the order of processing for the application.

The Prioritization Draw is a live, randomized event where each application receives a Priority Number based on a physical drawing of tickets.  Applicants can choose to participate by purchasing a ticket for each application they wish to prioritize.  Tickets must be purchased in person and each application requires one ticket.  The Draw will proceed in groups of 500 applications until all have been assigned a priority number.

No, participation is optional. Applicants who do not wish to participate in the Draw will still receive a Priority Number, but it will be assigned after all applications that entered the Draw.  Non-participating applications will be processed once all drawn applications are processed.

IDN applications (Internationalized Domain Names) have specific rules for prioritization in the Draw:

  • Variant strings of IDN gTLDs from the 2012 round are processed first and receive automatic inclusion in the Draw without needing a ticket.
  • If fewer than 125 remaining IDN applications participate in the Draw, they are processed before non-IDN applications.
  • If there are 125 or more IDN applications, 25% of the first group of 500 will be IDN applications, and the rest will be a mix of IDN and non-IDN applications drawn randomly.

The Prioritization Draw sets the order for processing applications, but factors such as objections, Government Advisory Committee (GAC) advice, extended evaluations, and contention sets can affect the processing order.  If any of these issues arise, ICANN will continue processing applications in priority order until the issues are resolved.

Registry Service Provider FAQ

A Registry Service Provider (RSP) is a third-party company that offers the technical services required to operate a gTLD registry.  RSPs are responsible for managing the technical infrastructure, domain registration, and maintenance of the gTLD.  Most applicants will need to partner with an RSP to handle these services, as most organizations do not have the expertise or resources to run a registry in-house.

When selecting an RSP, applicants should consider:

  • Technical expertise:  Ensure the RSP can handle DNS, security, and registry operations specific to your TLD type (e.g., open, closed, brand)
  • Scalability:  Choose an RSP that can support growth, especially for open or high-traffic TLDs
  • Compliance:  Ensure the RSP meets ICANN’s security standards and any industry-specific requirements
  • Cost:  Make sure the pricing fits your budget and the terms align with your business model

Carefully choosing the right RSP helps ensure smooth and reliable operation for any TLD type.

ICANN provides an RSP Evaluation Program where RSPs must meet specific technical standards to be approved.  You must choose an evaluated RSP for your gTLD application. You can select an RSP from ICANN’s list of approved RSPs once they pass ICANN’s technical evaluation (they will be listed here).  When submitting your application, you will need to provide details of the RSP you plan to work with and confirm their commitment to supporting your registry.

Yes, RSPs must meet specific criteria set by ICANN to ensure they can provide the necessary services to run a secure and stable registry.  These include:

  • Technical Capability:  RSPs must demonstrate their ability to manage DNS operations, security measures, and ensure high availability
  • Financial and Operational Stability:  RSPs must be financially stable and capable of supporting the ongoing operations of a TLD registry
  • Security and Compliance:  RSPs must comply with ICANN’s operational requirements, including measures to protect against abuse and ensure the integrity of the DNS

Yes, you can change your Registry Service Provider after submitting your application, but you must inform ICANN and provide the necessary updated documentation.  If you choose a new RSP after submission, you will need to go through the Extended Evaluation process to ensure the new RSP meets ICANN’s requirements and the registry operations remain compliant with ICANN’s policies.

Back to FAQ menu

Evaluation Process FAQ

ICANN conducts several evaluations to ensure that an applicant meets the technical, operational, and financial requirements to operate a new gTLD.  These evaluations include:

  • String Evaluation:  Assesses whether the applied-for string is confusingly similar to existing gTLDs, includes a geographic name, or poses other risks such as name collisions
  • Applicant Evaluation:  Examines the applicant’s financial stability, operational capacity, and ability to maintain a secure and stable registry
  • Community Priority Evaluation (CPE):  For community-based applications, this evaluation determines whether the applicant qualifies for priority over other applicants in the same contention set
  • Objections and Appeals:  The evaluation also involves reviewing any objections filed by third parties or applicants.  These objections could be related to string confusion, legal rights, or public interest concerns

String Evaluation is a multi-step process designed to minimize confusion in the DNS and ensure that the string is appropriate for the root zone.  This evaluation includes:

  • String Similarity Evaluation:  A panel assesses whether the applied-for string is visually similar to any existing gTLD (listed here), ccTLD, or blocked names, which could cause user confusion
  • Name Collision Risk Assessment:  ICANN evaluates whether the applied-for string poses a high risk of name collision and may require the applicant to submit a mitigation plan if necessary
  • Safeguard Assessment:  Evaluates whether the string falls into sensitive categories, such as consumer protection or regulated markets, and whether specific safeguards should be put in place
  • Geographic Names Identification:  Checks whether the string corresponds to a geographic location or name that might require special handling under ICANN rules

Once the application list is published, applicants and third parties can file objections to applications.  The grounds for objections include:

  • String Confusion:  If two strings are likely to cause confusion for users
  • Legal Rights:  If an applicant’s string infringes on legal rights
  • Community and Limited Public Interest:  If the application violates community interests or has a limited public interest

The objection filing period is 90 days after String Confirmation Day.  If an applicant is not satisfied with the outcome, they may appeal within 15 days.  All objections are resolved by Dispute Resolution Service Providers (DRSPs).

During the application evaluation, ICANN’s evaluators may issue clarifying questions if they need further information to complete their assessment.  There are two types:

  • Administrative Clarifying Questions:  These need to be answered within 7 days
  • Substantive Clarifying Questions:  These require a more detailed response within 21 days

If you fail to respond within the defined period, you risk losing the opportunity to address any issues raised by the evaluation panel.

If your application faces issues that cannot be resolved through clarifying questions, you may be eligible for extended evaluation.  This process provides additional time and interaction to resolve outstanding issues, such as concerns about your financials, operational capacity, or Registry Service Provider selection.  You can request extended evaluation within 15 days of receiving the evaluation results.

The application process is multi-stage and can take several years to complete. For a straightforward application (no contention or issues), ICANN estimates that it could take 15 months from the close of the application window to process the application.  More complex applications or those that face contention will take longer, and the delegation of new gTLDs could begin by late 2027 or early 2028.

Why TLDz FAQ

We haven’t just filled out applications – we’ve built TLDs from the ground up.  With over 50 applications submitted and more than 40 TLDs launched and operated, TLDz brings deep, hands-on experience across strategy, auctions, marketing, and registry operations.  Where others talk theory, we deliver real-world execution and insight.

But here’s what you should really ask before choosing a vendor:
Have they launched what they applied for – or are their TLDs still sitting on a shelf a decade later?  If they’ve launched, what’s the quality of the registrations?  If they run open TLDs, are the names meaningful or flooded with low-value junk? And most importantly – are they a neutral partner, or a potential competitor you’re handing your business strategy to?

This isn’t just a checkbox exercise.  Choosing the right partner can shape your TLD’s future.  With TLDz, you get experience, transparency, and a partner fully aligned with your success.

Yes – under different banners (dotTBA and HSBC), we achieved a 100% success rate across 50+ applications submitted.  But that was just the start.  We created TLDz to go further, because while others focus solely on the application, we focus on realizing the full business value a TLD can deliver. From strategy and launch to long-term growth, we help our clients turn TLDs into real-world impact and measurable success.

A lot – and we’ve got the track record to prove it.  With 12+ years in the industry, 50+ successful TLD applications, and hands-on operational experience across 40+ live TLDs, we know this space inside out.  From brands to cities to open and restricted strings, we’ve done it all – and we’re ready to help you do it too.

What truly sets us apart?  We’re not just experts – we’re passionate believers in the power of TLDs.  This isn’t just our work. It’s what we care about, what we live and breathe.

Absolutely.  From application to delegation to long-term growth, TLDz guides you through the full TLD lifecycle.  We’re not just here for the paperwork, we’re your partner from day one to year ten (and then some).

From dotBrands and generics to city and community TLDs, we’ve launched TLDs across every major industry.  With 50+ applications and 40+ delegated TLDs, our track record includes finance, tech, telecom, retail, media, and the public sector – each with its own strategy, complexity, and opportunity.

We don’t guess. We know. TLDz blends proven strategy, operational experience, and real-world results to help you build something meaningful- not just check a box.

No conflicts. No bias.  We work 100% in your corner – always – with clear, practical advice rooted in hands-on experience.

Back to FAQ menu

Subscribe to Our Monthly Newsletter

Join our mailing list to receive exclusive content only our newsletter members have access to.