Should I own a registered trademark to submit a dotBrand new gTLD application to the ICANN in 2026?

📝 Registered Trademark Requirement for dotBrand

Yes, based on the requirements from the previous round and the current planning for the next round (expected to open in April 2026), a registered trademark is a mandatory requirement for a dotBrand (\text{.brand}) new gTLD application.

Here are the key points:

- String Match: The domain extension (the "string") you apply for must be identical to a registered trademark that your organization (the Registry Operator) owns.

- Trademark Clearinghouse (TMCH): You must provide proof of this registered trademark, typically by having the mark recorded with the Trademark Clearinghouse (TMCH). This process helps verify the legitimacy of the brand name you are applying for.

- Restricted Use: The dotBrand gTLD is a restricted namespace, meaning only the Registry Operator, its affiliates, or trademark licensees are permitted to register second-level domain names (like website.yourbrand). This restriction is tied directly to the trademark ownership.

- Non-Generic: The applied-for string cannot be considered a "Generic String" (a standard dictionary word or common term).

In summary, for a dotBrand application, having a valid, registered trademark that matches the TLD string and registering it with the TMCH is a fundamental part of establishing your eligibility and right to the name.

🗓️ Important Dates for the Next ICANN Round (2026)

ICANN has provided a projected timeline for the next round of the New gTLD Program:

- Applicant Guidebook (AGB) Publication: The final AGB, which contains all the definitive rules and requirements, is expected to be published around December 2025.

- Application Window Opens: The application submission period is projected to open in April 2026 and last for approximately 12–15 weeks.

I recommend closely monitoring ICANN's official "New gTLD Program: Next Round" website for the final release of the Applicant Guidebook in late 2025, as this document will contain the definitive, non-negotiable rules for the 2026 application window.

Which strings cannot be submitted as new gTLD applications in the 2026 ICANN round?

In the upcoming 2026 ICANN New gTLD round, not all strings are eligible for application. ICANN enforces strict technical, public interest, and "confusing similarity" rules to protect the stability and security of the Domain Name System (DNS).

The following categories of strings cannot be submitted or will be blocked during the application process:

1. Technical & Formatting Prohibitions

Strings must meet specific syntax requirements to ensure they work across all internet software.

Too Short or Too Long: Strings must be between 3 and 63 characters long. Single-character (e.g., .a) and two-character (e.g., .ab) ASCII strings are prohibited.

Invalid Characters: Strings cannot contain digits (0–9), dashes (-), or special symbols. They must consist only of alphabetic characters (a–z) or valid Internationalized Domain Name (IDN) scripts.

Leading/Trailing Dashes: While dashes are generally banned in the TLD itself, they are also prohibited at the start or end of any internal label components.

2. Reserved & Blocked Names

ICANN maintains a Blocked Names List that prevents the registration of strings with high global sensitivity or technical risk.

Country and Territory Names: High-level names of countries and territories (e.g., .america, .france, .china) are generally reserved or require specific government support.

Intergovernmental Organizations (IGOs): Strings that mimic the names of major international bodies (e.g., .olympic, .redcross, .un) are often protected.

Internal Technical Strings: Strings used for internal networking that could cause "name collision" are banned. This includes:

.local, .home, .corp, .lan, .onion

3. "Confusingly Similar" Strings

To prevent user confusion, ICANN will reject applications for strings that are visually or functionally too close to existing or other applied-for TLDs.

Existing TLDs: You cannot apply for a string that is a visual "look-alike" to an existing one (e.g., if .apple exists, a string that looks identical in another script might be blocked).

Plural vs. Singular: A major change for the 2026 round is the strict handling of singular and plural versions of the same word (e.g., if .sport exists, .sports may be deemed confusingly similar and blocked).

Variant Strings: For IDNs (non-Latin scripts), "variants" that are visually identical to the primary string are treated as part of the same application and cannot be applied for separately.

4. Policy-Based Prohibitions

Closed Generics: In the 2026 round, ICANN has determined that "Closed Generics" (generic terms like .book or .shoe that a single company wants to use exclusively for itself without opening registrations to others) are prohibited.

Brand TLD Constraints: For "dotBrand" applications, the string must exactly match a trademarked label in the Trademark Clearinghouse. You cannot apply for a brand string that does not have a matching Signed Mark Data (SMD) file.

How many new gTLD applications will be submitted to the ICANN in April 2026?

The official application window for ICANN’s New gTLD Program: Next Round is scheduled to open on April 30, 2026.

Because this is the very first day of a 12–15 week submission period, the exact number of applications that will be submitted specifically within the month of April 2026 is unknown, but it is likely to be a small fraction of the total. Most organizations will use the full window to finalize their technical and financial documentation.

Estimated Total Applications

While ICANN does not have a "fixed" number of applications, industry experts and ICANN's own planning documents suggest the following projections for the entire round:

Projected Range: Between 500 and 3,500 applications.

Specific Industry Plans: Some players have already announced major moves; for example, Nova Registry has publicly stated intentions to apply for at least 200 new gTLDs.

Historical Context: In the previous round (2012), ICANN received 1,930 applications. Experts anticipate this round could be similar or slightly larger due to the rise of ".brand" domains and Internationalized Domain Names (IDNs) in non-Latin scripts.

Key Factors Influencing the Number

High Entry Cost: The application fee is set at $227,000 per gTLD. This significant investment naturally limits the pool to established corporations, well-funded startups, and government entities.

Process Complexity: The 2026 round features an expanded Applicant Guidebook (AGB) with over 200 questions, requiring extensive technical, financial, and legal preparation.

Brand Strategy: Many global brands that sat out in 2012 are expected to participate this time to secure their own digital namespaces (e.g., .brand).

Important Dates for 2026:

• Application Window: Opens April 30, 2026
• Submission Period: Duration 12 to 15 weeks
• Projected Window Close: July – August 2026
• Initial Evaluation Results Expected 2027

Note: ICANN has mandated that the final Applicant Guidebook be available at least four months before the window opens. It was officially adopted in late 2025 to ensure the April 30, 2026, launch date remains on track.

Brand and Trademark Protections in the new gTLD program: what should an applicant know?

Brand and trademark protection for applicants in the new gTLD program involves both proactively protecting your own brand by applying for a brand TLD, and reactively defending your trademarks against third-party gTLD applications.

Applicants should know about the following mechanisms and strategic considerations:

🛡️ Proactive Protection: The Brand TLD (.brand)

Applying for a Brand TLD (a "dotBrand," e.g., .google, .nike) is the highest level of digital control and protection for a trademark owner.

1. The .Brand TLD Designation

Closed Registry: The primary characteristic is that the registry is restricted. Only the brand owner and its affiliates or licensees are permitted to register second-level domains (e.g., shop.nike). Third-party registrations are prohibited.

Enhanced Security: This provides unprecedented control, allowing the brand owner to implement high-level security protocols (like DNSSEC) across all domains, significantly reducing phishing and counterfeiting risks.

Eligibility: The applied-for string must typically be identical to a registered trademark owned by the Registry Operator.

2. Specification 13

This is a critical addendum to the Base Registry Agreement that grants special exemptions for Brand TLDs.

Exemptions: It provides relief from certain obligations designed for open registries, such as the mandatory requirement to publish contact information for registrants.

Sunrise Deferral: It defers the mandatory Sunrise period (priority registration for trademark holders) for as long as the TLD remains a closed, qualified Brand TLD. This avoids a public launch process.

⚔️ Defensive Protection: Rights Protection Mechanisms (RPMs)

If you are not applying for your own TLD, you must be prepared to defend your trademarks against other gTLD applications using these tools:

1. Legal Rights Objection (LRO)

This is a pre-delegation dispute resolution procedure to formally challenge a third-party gTLD application.

Grounds: An objection may be filed if the applied-for gTLD string, or the applicant’s potential use of it, would cause impermissible infringement of the objector's existing trademark.

Procedure: LROs are resolved by an independent panel of experts, primarily administered by the WIPO Arbitration and Mediation Center.

2. Trademark Clearinghouse (TMCH)

The TMCH is the central, global database of verified trademark information and is foundational for protection.

Sunrise Services: All new gTLD registries must offer a Sunrise Period (at least 30 days) where verified trademark holders from the TMCH can register corresponding domain names before public access.

Trademark Claims Service: For at least 90 days after general public registration opens, the registry must use the TMCH to provide notice to both the new domain registrant (warning of the conflict) and the trademark holder (if the registration proceeds).

3. Uniform Rapid Suspension System (URS)

This is a post-delegation dispute mechanism for clear-cut cases of trademark infringement (cybersquatting) in a newly delegated TLD.

Process: URS is a faster and less expensive alternative to the Uniform Domain Name Dispute Resolution Policy (UDRP).

Remedy: The only remedy is the temporary suspension of the infringing domain name, making it suitable for quick relief in obvious cases of abuse.

What are the Different gTLD Application Types in the next ICANN new gTLD Round?

The new ICANN gTLD round (often called the Next Round, anticipated for 2026) classifies applications into two main groups: General Applications and Specialized Applications. Within the Specialized category, there are several key types defined by the string itself, the applicant, and/or the intended use.

Here are the different gTLD application types:

1. General Application (Standard)

A General Application is the default type for most commercial or unrestricted gTLDs.
Description: These applications do not fall into any specialized category. They are subject to the standard set of requirements outlined in the Applicant Guidebook (AGB) and do not have additional conditional requirements or special designations.
Intended Use: The registry is typically open for any person or entity to register a second-level domain (e.g., .shop, .app, or a generic name like .auto).

2. Specialized Application Types

Specialized Applications have specific conditional requirements, varying fees, or eligibility standards depending on the string, the applicant, or the intended use.

A. Community Application 🌐
Description: The application is filed by an entity acting on behalf of a clearly delineated community (e.g., cultural, linguistic, or professional).

Requirement: The applicant must demonstrate a clear and strong nexus between the proposed gTLD string and the community it seeks to serve.

Advantage: If the string is contested, the applicant may undergo a Community Priority Evaluation (CPE) to receive priority over other applicants if they score 14 or more out of 16 points.

B. Brand TLD Application ℠
Description: The application is for a gTLD that is the trade name, trademark, or service mark of a single, private entity (e.g., .google, .nike, .bank).

Requirement: The applicant must affirm its intention to operate the gTLD as a closed registry, restricting registration of second-level domains only to itself and its affiliates.

Advantage: Specification 13 in the Registry Agreement provides specific contractual benefits and obligations tailored to protecting corporate brands. This type often involves a conditional evaluation to confirm its status.

C. Geographic Name Application 🗺️

Description: The applied-for gTLD string represents a geographic name (e.g., a city, region, or country).

Requirement: The applicant must obtain specific letters of support or non-objection from the relevant governments or public authorities associated with that geographic name. Without this, the application for a Geographic Name is rejected.

D. Reserved Name Application 🛑

Description: Applications for strings that were reserved from general application in previous rounds due to their special status (e.g., related to inter-governmental organizations or specific humanitarian groups).

Eligible Applicants: Only the entities for whom the names are reserved—such as the Red Cross Red Crescent (RCRC) or International Governmental Organizations (IGOs)—can apply for these strings.

E. Internationalized Domain Name (IDN) Application

Description: Applications for gTLD strings that are not written using the basic 26-letter ASCII (Latin) script, but rather in scripts like Arabic, Chinese, Cyrillic, or Devanagari.

Requirement: The applied-for string must comply with the rules established by the relevant Root Zone Label Generation Rules (RZ-LGR) for that script to ensure technical stability and prevent confusion.

The Applicant Guidebook (AGB) for the Next Round details the specific requirements, fees, and evaluation criteria that apply to each of these application types.

Round 2 of new gTLDs: what are Replacement String and the Replacement Period?

The Replacement String and the Replacement Period are new mechanisms introduced for the next round of new gTLD applications (often informally called "Round 2" or the "Next Round," currently planned for 2026). They are designed to give applicants a mechanism to avoid contention sets and potential auctions.

This feature was developed as a direct result of lessons learned in the 2012 round, where many identical applications were forced into time-consuming and costly private resolutions or auctions.

🔁 Replacement String

A Replacement String is a second-choice Top-Level Domain (TLD) name that an applicant can optionally designate in their original application, in addition to their first-choice Applied-for String (or original string).

• Optional: Applicants are not required to provide a Replacement String, but it is highly recommended as a strategic contingency.
• Irreversible: If an applicant chooses to switch to their Replacement String during the Replacement Period, that string permanently and irreversibly replaces the original string for the remainder of the application process.They cannot switch back.
• No Contention: The primary goal is to provide a backup that is less likely to be contested. If an applicant's Replacement String is identical to the Applied-for String or Replacement String of another applicant, the applicant will not be allowed to switch to it, as this would simply create a new contention set.

🗓️ Replacement Period

The Replacement Period is a defined, short window of time during which applicants must decide whether to switch their application from their original Applied-for String to their pre-designated Replacement String.

• Timing: The period is scheduled to be 14 days following Reveal Day.
• Reveal Day: This is the day when ICANN publishes the public-facing portions of all received gTLD applications, including the original strings and all designated Replacement Strings. On this day, applicants get a clear picture of:
• Which applicants are applying for the identical string as their first choice.
• Which applicants have designated the same string as their Replacement String.
• Decision Window: Applicants in a contention set can use the 14-day Replacement Period to assess their chances in a potential auction or evaluation (like Community Priority Evaluation). They can then strategically opt to switch to their backup string to exit the contention set and proceed faster with evaluation.
• No Rationale Required: The decision to switch is at the applicant's sole discretion, and they are not required to provide ICANN with a rationale.

Strategic Significance

The introduction of the Replacement String and Replacement Period offers applicants a non-auction path to reduce risk and streamline the application process. By providing a low-contention backup name upfront, applicants can potentially save time and significant cost associated with prolonged string contention procedures, especially mandatory ICANN auctions (as private resolutions, which were common in Round 1, are now prohibited in the Next Round).

Would you like to know more about the ICANN Auction process and why applicants would be motivated to avoid it?

What are GAC Member Early Warnings and GAC Consensus Advice in the next ICANN new gTLD Round?

Both GAC Member Early Warnings and GAC Consensus Advice are mechanisms used by the Governmental Advisory Committee (GAC) in the ICANN new gTLD process to raise public policy concerns regarding specific applications.

They differ significantly in their source, purpose, and impact on the application's fate.

⚠️ GAC Member Early Warnings

An Early Warning is a non-binding notice provided by one or more individual GAC members (representing a national government) to an applicant. Its main goal is to provide an early caution about potential issues.

Source: Issued by individual GAC members (one or more governments); it does not require consensus from the full GAC.

Purpose: To signal to the applicant that the applied-for gTLD string is regarded as potentially sensitive or problematic by a specific government or governments, often due to national law, regulatory concerns (like finance or health), or public order issues.

Impact: It is non-binding and does not directly stop the application.

It gives the applicant an early opportunity to address the concerns, potentially through amending the application, proposing changes to their registry policies, or withdrawing the application for an 80% refund of the application fee (a key incentive to withdraw).

It is a strong indicator that the application may be subject to a formal GAC Consensus Advice or an Objection later in the process.

⚖️ GAC Consensus Advice

GAC Consensus Advice is a formal, collective recommendation from the Governmental Advisory Committee to the ICANN Board of Directors, reflecting the consensus position of the governments represented on the GAC.

Source: Issued by the full GAC and requires a consensus among its members.

Purpose: To formally advise the ICANN Board on public policy issues related to an application, often resulting from unresolved concerns raised during the Early Warning phase or during the GAC's own review.

Impact: It carries significant weight and creates a strong presumption that the application should not be approved or should proceed only with specific conditions (remediation).

If the ICANN Board chooses to take an action inconsistent with GAC Consensus Advice, the Board must publicly articulate the reasons for its decision and attempt to find a mutually acceptable solution with the GAC. Historically, the ICANN Board has consistently followed GAC Consensus Advice to reject or place conditions on an application.

The advice must be clearly enunciated, actionable, and accompanied by a rationale.
The mechanisms for the next gTLD round are being refined through the Subsequent Procedures Policy Development Process (SubPro), but the fundamental roles of the Early Warning (precursor, non-binding) and Consensus Advice (binding on the Board, subject to appeal) are expected to remain the same.

Would you like to know about the types of Public Interest Commitments (PICs) an applicant might offer to resolve GAC concerns?

What are new gTLD Community Priority Evaluation?

The Community Priority Evaluation (CPE) is an optional, high-stakes mechanism within the ICANN New gTLD Program designed to resolve contention for a domain name string when one or more of the applicants claim to represent a legitimate community.

Its primary function is to award priority to a community-based application, allowing it to move forward and prevail over all non-community applicants in the contention set, potentially avoiding a competitive auction.

Key Concepts

Contention Resolution CPE is triggered only when multiple parties apply for the exact same gTLD string.

Purpose It grants a community application priority status if it meets a high threshold, thereby resolving the conflict in its favor against commercial or other non-community applications for the same string.

Third-Party Panel The evaluation is conducted by an independent panel of experts (e.g., The Economist Intelligence Unit - EIU in the 2012 round).

The Four Evaluation Criteria

The CPE panel scores the community application based on four criteria, each worth up to 4 points, for a total maximum score of 16. A minimum score of 14 out of 16 points is required to prevail.

1. Community Establishment (Max 4 points)
   This criterion evaluates the existence, organization, and longevity of the claimed community. The panel assesses whether the community is clearly delineated, existed prior to the new gTLD program, and possesses a demonstrable organizational structure.
2. Nexus between Proposed String and Community (Max 4 points)
   This assesses the relevance and association of the applied-for gTLD string to the community it claims to represent. It looks at how closely the string describes the community and whether the name is unique to that community.
3. Registration Policies (Max 4 points)
   This evaluates the applicant's proposed policies for registering second-level domains (e.g., example.community). The panel ensures these policies are commensurate with the purpose and needs of the identified community and support the community's interests.
4. Community Endorsement (Max 4 points)
   This criterion measures the level of support and opposition the application has received. The panel looks for written endorsements from established, legitimate institutions representing the community, and weighs the significance of any opposition.

The Outcome

Prevailing Score (14+ points): The community application is granted priority. It wins the contention set against all non-community applicants and proceeds with the rest of the application process.

Non-Prevailing Score (Less than 14 points): The application loses its priority status. It must then participate in an ICANN Auction to resolve the contention set along with the other competing applications (community or non-community).

The CPE process safeguards names with genuine community significance, awarding them priority over commercial applicants seeking the same string.

Would you like to know more about the ICANN Auction process that resolves contention when CPE is not used or is unsuccessful?

New gTLDs: what are Community Input?

Here is a breakdown of Community Input in the context of the ICANN new gTLD Program.

👂 1. Community Input

1. Community Input is a general mechanism for the public, governments, and other interested parties to provide information, raise issues, and express opinions on a new gTLD application. It is primarily an advisory and informational process.
2. To bring relevant information and issues to the attention of ICANN, applicants, and evaluators.
3. Input is typically submitted via the Application Comment Forum on ICANN's website after applications are published.
4. It is generally non-binding on the evaluators or the ICANN Board, but comments can be used by evaluators to verify facts or by the Governmental Advisory Committee (GAC) to formulate advice.
5. Key Types
1. Application Comments: General public submissions.
2. GAC Member Early Warnings: An early, non-binding signal from a government that an application may be problematic under national law or sensitivities.
3. GAC Consensus Advice: Formal, binding advice from the GAC (representing governments) to the ICANN Board that may lead to rejection or specific conditions on an application.

The key difference from Objections is that Community Input does not trigger a formal, adversarial dispute resolution proceeding.

ICANN new gTLDs: what are Objections and Appeals?

Objections and Appeals are mechanisms within the ICANN new gTLD Program that allow third parties to challenge or seek review of a new Top-Level Domain (gTLD) application. They are designed to ensure that the introduction of new gTLDs is fair and does not infringe on existing rights or contravene public interests.

🛑 Objections

A formal Objection allows a qualified third party to argue that a new gTLD application should be rejected based on one of four specific grounds. These objections initiate a Dispute Resolution Proceeding that is handled by independent third-party Dispute Resolution Service Providers (DRSPs), not ICANN itself.

The four specific grounds for filing a formal Objection are:

1. String Confusion Objection: The applied-for gTLD string is confusingly similar (visually, aurally, or in meaning) to an existing Top-Level Domain (TLD) or another gTLD application in the same round. Standing: Generally, only existing TLD operators or other gTLD applicants in the same round can file.
2. Legal Rights Objection: The applied-for gTLD string infringes the existing legal rights (like a trademark) of the objector. Standing: Must be filed by a rights holder whose rights are being infringed.
3. Limited Public Interest Objection: The applied-for gTLD string is contrary to generally accepted legal norms of morality and public order recognized under principles of international law. Standing: Anyone may file, though frivolous or abusive objections are filtered out.
4. Community Objection: There is substantial opposition to the gTLD application from a significant portion of the community that the string is explicitly or implicitly targeting. Standing: Must be an established institution associated with a clearly defined community.

⚖️ Appeals

An Appeal is the process for seeking review of a final Expert Determination made by a Dispute Resolution Service Provider (DRSP) panel in an objection proceeding.

Who can appeal? The party that was non-successful (the applicant or the objector) in the initial Objection proceeding.

Process: The non-prevailing party can file an appeal with the relevant DRSP, usually within a short timeframe (e.g., 15 days) from the date the initial Expert Determination was issued.

Standard of Review: The appeal is generally considered under a "clearly erroneous" standard of review. This means the appellate panel will not re-hear the case from scratch, but will primarily determine if the initial expert panel made a decision that was clearly wrong based on the evidence and rules.

Outcome: The appeal results in an Appellate Expert Determination, which is the final word on the objection within the ICANN process.

As a generic new gTLD Registry, how much should I sell my domain names to the network of accredited Registrars?

This is one of the most critical decisions for a new gTLD Registry, as there is no fixed price and your wholesale price (the price you charge Registrars) will heavily influence your success. Unlike older gTLDs like .com, new gTLDs have no ICANN price caps, giving you full flexibility.
Your price should be determined by balancing cost recovery, market positioning, and demand generation.

🔑 Key Factors to Determine Your Wholesale Price

Your wholesale price must cover your costs and allow for a healthy profit, while remaining competitive and attractive to both Registrars and end-users.

Factor | Description & Consideration

1. Registry Operating Costs | Calculate your fixed costs (ICANN fees, backend provider, marketing, personnel, etc.). Your wholesale price for standard domains must cover these costs at your projected volume to be sustainable.
2. Target Market and TLD Type | Premium/Niche TLDs: If your TLD is highly specific (e.g., .inc, .bank), a higher price is justifiable due to perceived value, exclusivity, and lower expected volume. Generic TLDs: If your TLD is broad (e.g., .app, .shop), a lower, volume-driven price is often better to compete with established TLDs.
3. Competitive Landscape | Research the wholesale prices of comparable new gTLDs that are targeting a similar audience or are in the same price range. You generally need to offer competitive value relative to alternatives.
4. End-User Price Expectation | Remember, Registrars will add their own markup (which can be 20-100% or more, depending on their strategy). If your wholesale price is $$10, the end-user might pay \$15-\$25. If your wholesale price is too high, the resulting retail price might deter mass adoption.
5. 5. Pricing Structure | Do you plan on a single flat price or a tiered/premium pricing model? Most successful registries use premium pricing.

💰 Standard vs. Premium Pricing Strategy

The industry best practice for new gTLDs is a variable or tiered pricing model:

1. Standard Domains (Bulk Volume)
   These are the vast majority of domains (random strings, long names) that drive volume and retention.
   Goal: Maximize registration volume and market share.
   Wholesale Range: The prices are highly variable for new gTLDs, but a common range for a non-premium standard domain might be between $8 - $25 USD per year to the Registrar.
   Note: This is a rough benchmark; prices can be lower (for high-volume TLDs) or much higher (for niche TLDs).
   Strategy: Keep this price reasonable to encourage Registrars to offer attractive retail prices (often \$15 - \$35 to the customer).
2. Premium Domains (High Margin)
   These are the most valuable, short, generic, or keyword-rich domains (e.g., car.tld, money.tld).
   Goal: Drive significant revenue and ROI.
   Wholesale Range: These can range from $100 to thousands of dollars for a single registration, often with a different (but still high) renewal price.
   Strategy: Create a tiered premium list with multiple price bands. Premiums are crucial for funding your registry operations, especially in the early years. The end-user price can vary greatly (e.g., \$100 to over \$1,000).

📈 Initial Launch and Promotional Considerations

A good pricing strategy also includes promotional elements to drive early adoption:

• Sunrise/Trademark Period: Often priced higher than the general availability price to compensate for the specialized validation process.
• General Availability (GA) Launch: Consider a temporary promotional price (e.g., 20-50% discount) for a limited time to incentivize Registrars to push your TLD and drive early registrations. This price should still be profitable.
• Renewal Price: The wholesale renewal price is critical. A common tactic is to offer a lower initial registration price to registrars, knowing that the renewal price (paid annually) will be significantly higher to ensure long-term profitability. This higher renewal price is what sustains your business.

In summary, instead of aiming for a single number, focus on a structure that includes a sustainable, volume-driving standard price and a lucrative, tiered premium pricing system.

ICANN Round 2 of new gTLDs: is it mandatory to deposit data of a Registry with an escrow agent?

Yes, it is mandatory for gTLD Registry Operators (including those from the New gTLD Program, which is often referred to as "Round 1" and the anticipated "Round 2") to deposit certain registration data with an ICANN-approved Data Escrow Agent (DEA).

This requirement is a key part of the contractual agreement between the Registry Operator and ICANN (the Registry Agreement).

🔑 Key Points

• Mandatory Requirement: Registry Operators are required by their Registry Agreements to escrow specific registration data.
• Purpose: The primary purpose of Registry Data Escrow is to protect the interests of domain name registrants and ensure the stability of the DNS. The escrowed data serves as a continuity mechanism in the event of a Registry Operator's technical, financial, or business failure.
• Agent: The data must be deposited with an ICANN-approved Data Escrow Agent (DEA).
• Schedule: Deposits are typically required on a regular schedule (e.g., daily incremental updates and weekly full deposits).

This requirement is a long-standing and essential safeguard mechanism within ICANN's regulatory framework for generic Top-Level Domains (gTLDs).

Can you apply for an ICANN new gTLD with a budget of 800,000€?

While an initial budget of 800,000€ is substantial and likely covers the core ICANN application fee, it is highly unlikely to be enough for the entire process of applying for, launching, and operating a new generic Top-Level Domain (gTLD) successfully.

The total cost can easily escalate to over €1 million, and sometimes much higher, especially if there are disputes or auctions.

Here is a breakdown of the typical costs:

---

1. Core ICANN Application Fee 🧾

The mandatory fee you pay directly to ICANN for the application and evaluation process for the upcoming round is significant.

• Expected Fee: $227,000 USD (approximately €210,000 - €220,000 as of late 2024/early 2025, but this is subject to currency fluctuations).

• What it Covers: This fee covers the cost of processing and evaluating your application by ICANN. It is only the entry ticket.

---

2. Additional ICANN & Associated Fees ⚖️

This is where the costs begin to increase beyond the baseline.

Cost Component	Estimated Range (USD)	Notes
Conditional Evaluations (e.g., Community Priority, .Brand Status)	$50,000 - $80,000	Optional fees if you seek special status, such as proving you represent a community or applying for a dedicated brand TLD.
Geographic Name Review	$18,000 - $25,000	Mandatory if your TLD could be considered a geographic name (e.g., .PARIS).
Initial Annual Fee	$25,750 USD	A fixed annual fee paid to ICANN, which begins once the gTLD is launched.
Contention Resolution	Unpredictable	If another party applies for the same or a confusingly similar string, you enter a "contention set," which can lead to costly private negotiations, arbitration, or auctions that can cost millions (e.g., .app and .web went for tens of millions in the last round).

---

3. Operational & Professional Costs 🛠️

These are the non-ICANN costs that consume the majority of the total budget.

• Application Preparation & Consultancy: Preparing the complex application requires highly specialized consultants, legal advice, and technical experts. This alone can cost hundreds of thousands of euros.

• Registry Backend Services: You need a dedicated technical partner (Registry Service Provider) to handle the DNS, EPP, WHOIS, uptime, and ICANN compliance. This involves:

  • One-time setup fees.

  • Ongoing annual fees (often $25,000 - $100,000+ USD depending on service level).

• Legal Fees: Legal review is mandatory for the application and contracts. If there are objections or disputes, legal fees can quickly reach tens of thousands or hundreds of thousands of euros.

• Marketing & Launch: A TLD won't gain users on its own. You need a significant budget for marketing, outreach to registrars, and establishing a presence, which often costs hundreds of thousands of euros per year for a public TLD.

Conclusion

With a budget of 800,000€, you have enough to cover the ICANN application fees, conditional evaluations, and initial consultation.

However, this budget is likely to be insufficient for the total all-in cost which includes legal defense against objections, the technical setup, and the multi-year marketing and operational costs necessary for a successful launch and operation. For an uncontested, simple application, some estimates put the low-end total cost at €300,000–€400,000, but for a public-facing TLD with any contention risk, the true cost is often €500,000 to over €1 million, not including potential auction bids.

Are 4 months enough to decide to submit a new gTLD application in the next ICANN new gTLD round?

That's a very compressed timeframe for such a significant undertaking. The ICANN new gTLD application is a highly complex business and technical proposal that typically requires many months, or even a year or more, of dedicated preparation.

Here's a breakdown of why 4 months is likely not enough time:

⚠️ The Scale of the ICANN Application

The application is essentially a detailed plan to operate a piece of critical Internet infrastructure for many years. It covers:

• Business Plan: Detailed financial projections, marketing strategy, and rationale for the new gTLD.
• Technical Operations: A robust plan for the registry system, including security, stability, scalability, and disaster recovery.
• Legal and Regulatory: Compliance with the comprehensive Applicant Guidebook (AGB) and a detailed understanding of ICANN policies.
• Financial Capability: Demonstrating sufficient funds for the application fee (which was $185,000 USD in the last round, and is expected to be similar or higher), operational setup, and initial years of running the registry.
• Registry Service Provider (RSP): You must either build your own system or, more commonly, contract with an established, ICANN-evaluated Registry Service Provider. This selection and contracting process is time-consuming.

📅 Next Round Timeline (Based on Current Information)

The expected timeline for the next ICANN New gTLD Round suggests that the application window is projected to open in April 2026 and last for about 12-15 weeks.
As of November 2025 (the current time), the Applicant Guidebook (AGB)—the essential rulebook—is expected to have been finalized and published.

• April 2026: Application Submission Period expected to open (for 12-15 weeks).
• December 2025 (Expected): Final Applicant Guidebook (AGB) published.

This means that while the formal submission is still months away, the preparation period is now.

✅ Key Tasks That Take Longer Than 4 Months

• Business Case Development (6+ months): Thorough market research, financial modeling (5-10 years), and legal entity setup.
• Registry Service Provider (RSP) Selection/Contracting (3-6+ months): Identifying an RSP, negotiating a contract, and defining the scope of services. Many RSPs require long lead times for new clients.
• Technical Documentation (3-4 months): The RSP will provide much of this, but you must integrate it, and your legal team must review and approve it for compliance with the AGB.
• Drafting the Application (4-6 months): Answering hundreds of questions and compiling extensive supporting documentation requires multiple drafts and review cycles by business, technical, and legal experts.
• Contention Strategy: If your proposed string is popular (e.g., .app, .web), you'll likely face other applicants. Preparing for potential dispute resolution or an auction requires strategic planning and budget allocation.

In summary, 4 months from deciding to submitting is extremely ambitious and potentially risky.

💡 Your Next Steps Now

If you are committed to applying, you must act immediately and compress the preparation schedule into the remaining time before the April 2026 opening:

• Secure Professional Advisers: Engage specialized gTLD consultants, legal counsel, and financial experts who have experience with the previous ICANN round.
• Define Your TLD & Application Type: Solidify the string (e.g., .brand, .geo, .community) and application category (Standard, Community, etc.).
• Finalize the Registry Service Provider: Sign a Letter of Intent or a contract with a pre-evaluated RSP as quickly as possible, as their technical documents are crucial for your application.
• Study the Applicant Guidebook (AGB): Dedicate a team to review the AGB as soon as it is published (expected by December 2025) to ensure full compliance.

What does the latest ICANN 84 GAC communiqué says about the next new gTLD round2 in 2026?

The ICANN 84 Governmental Advisory Committee (GAC) Communiqué was issued following the Annual General Meeting in Dublin (October 25-30, 2025). While the full text of the Communiqué should be reviewed for all GAC advice, the key points regarding the next new gTLD round (expected to launch in 2026) are:

🌐 Key Takeaways on the Next New gTLD Round

• GAC Preparation and Capacity Building: The GAC highlighted its commitment to readying its membership for their role in the Next Round of New gTLDs. This includes devoting substantial resources for capacity development of all committee participants, recognizing the complexity of the process.
• Engagement on the Applicant Guidebook (AGB): The GAC was actively discussing the New gTLD Applicant Guidebook (AGB) and other related subsequent procedures during ICANN 84. The GAC's advice to the Board is often informed by these discussions.
• The Board's Action: The ICANN Board adopted the Applicant Guidebook (AGB) for the 2026 round of the New gTLD Program at ICANN 84, clearing the path for the program launch. The Board directed the ICANN organization (org) to publish the AGB no later than December 30, 2025.

🗓️ Projected Timeline for the Next Round

While the Communiqué focuses on GAC advice, related ICANN announcements made at ICANN 84 confirm the expected timeline:

• Final Applicant Guidebook (AGB) Publication: No later than December 2025.
• Application Submission Period Opens: Projected for April 2026 and expected to remain open for 12–15 weeks.

The GAC continues to emphasize a cautious and well-structured approach to the upcoming round, focusing on priority topics like the Applicant Support Program (ASP), Objections (including Early Warnings and GAC Advice), GeoTLDs (Geographic TLDs), and Contention Sets.