To show support to Ukraine, should the ICANN block Russia from participating in the next round of the ICANN new gTLD program?

The question of whether ICANN should block Russia from the next round of the new gTLD program to show support for Ukraine touches upon ICANN's core mission, its neutrality, and the broader debate about the "Splinternet."

Here's a breakdown of the key considerations based on ICANN's principles and previous decisions:

Arguments Against Blocking Russia (ICANN's Position and Principles):

• Neutrality and Mission: ICANN's primary mission is technical—to ensure a single, stable, and globally interoperable Internet through the coordination of unique identifier systems (domain names and IP addresses). ICANN has historically maintained a stance of neutrality in geopolitical conflicts, arguing that its role does not extend to taking punitive actions, issuing sanctions, or restricting access to the Internet based on political disputes.
• Previous Precedent: Following Russia's invasion of Ukraine, ICANN rejected a request from Ukraine to revoke Russia's top-level domains (.ru, .рф, .su) and associated SSL certificates. ICANN's leadership cited the importance of its neutrality and the need to support the global Internet's security, stability, and resiliency.
• Risk of "Splinternet": Actions that fragment the global Internet along political boundaries—often termed the "Splinternet"—are seen as dangerous. Restricting participation based on nationality or political action could set a precedent that undermines the Internet's foundational principle of being a universal resource, potentially leading to widespread negative effects on global communication and human rights.
• Focus on Technical Function: ICANN's mandate is limited to the technical administration of identifiers. Using this technical function for political or punitive purposes is seen as overstepping its authority and potentially compromising the trust essential to the multistakeholder model of Internet governance.

Arguments for Blocking or Restricting Russia's Participation:

• Showing Support and Applying Pressure: Supporters of a block would argue that excluding Russia is a powerful, visible show of support for Ukraine and a form of economic/political pressure, aligning with sanctions imposed by many countries.
• Alignment with Sanctions: While ICANN itself is non-governmental and not a sanctions body, applicants for gTLDs may be required to abide by relevant economic sanctions, such as those overseen by the U.S. Office of Foreign Assets Control (OFAC). Russian government entities or sanctioned individuals/companies could face hurdles regardless of ICANN's intent.
• Ethical or Moral Considerations: Some argue that, in extraordinary circumstances like a large-scale invasion, technical bodies should not remain completely blind to the ethical implications of allowing sanctioned states to participate fully in global programs.

Conclusion:

Based on ICANN's stated mission, its adherence to a neutral, technical role, and its previous rejection of requests to "disconnect" Russian domains, it is highly unlikely that ICANN would unilaterally block Russia from participating in the next round of the new gTLD program.

Any restrictions on Russian applicants would most likely stem from an applicant's inability to meet the financial or legal requirements—specifically, clauses requiring adherence to international economic sanctions (e.g., U.S. sanctions) that may apply to the contracting process, rather than a political decision by ICANN to exclude the country as a show of support.

What is the annual budget to launch an ICANN new generic top-level domain in 2026?

The annual budget to launch an ICANN new generic top-level domain (gTLD) in 2026 is not a single, fixed number but rather a combination of various fees and potential additional costs. The total cost can easily exceed half a million dollars.

Here's a breakdown of the key expenses:

• ICANN Application Fee: The base application fee for a new gTLD in 2026 is $227,000 USD. This fee covers the processing and evaluation of your application by ICANN. It's important to note that this is just the starting point and does not cover other expenses.
• Registry Service Provider (RSP) Costs: To operate a gTLD, you need a backend registry partner unless you build one yourself. ICANN requires that your chosen provider is pre-evaluated. These costs include:
  • One-time setup fees
  • Ongoing fees for services like DNS, WHOIS, uptime, and ICANN compliance. These costs can range from $10,000 to $25,000 EUR per year.
• Legal and Consulting Fees:
  • Legal review and representation, especially if your proposed gTLD string overlaps with trademarks or has potential for objections.
  • Consulting services for application preparation. These can range from $20,000 to $50,000 EUR.
• Additional ICANN Fees:
  • Certain types of applications may have additional fees. For example, a Brand Application Evaluation fee of $500 USD applies to brand TLDs.
  • Objections, challenges, and appeals will require additional fees and can significantly increase costs.
• Contention Sets and Auctions: If multiple applicants apply for the same or a similar string, they enter a contention set. While private resolutions are now prohibited, the dispute can lead to an auction where the cost to acquire the gTLD can escalate to hundreds of thousands or even millions of dollars.

In summary, while the ICANN application fee is $227,000, a realistic budget for launching a new gTLD must account for a wide range of additional expenses, including legal, consulting, and registry operation fees, bringing the total annual budget to a much higher figure.

Shouldn't 2026 Registries announce their new gTLD application(s) to avoid too much competition?

This is an excellent question that gets to the heart of the strategic considerations for applying for a new gTLD. The idea of publicly announcing an application to "scare off" potential competition is a valid one, and it was a strategy that was considered and sometimes used in the first round of the New gTLD Program in 2012.

However, the reality of the situation is complex, and for the 2026 round, there are many reasons why applicants may choose not to announce their intentions publicly.

Here's a breakdown of the key factors to consider:

1. The "Reveal Day" and Contention

The most significant event in the application process is "Reveal Day," when ICANN publishes a list of all applied-for strings and the associated applicants. Before this day, applications are confidential.

• Public Announcements: If a company announces its intention to apply for a specific gTLD (e.g., .BRAND), this public statement could indeed serve as a deterrent to other potential applicants. It sends a message that the brand is serious and prepared for a potential contention resolution process.
• The Risk of Private Auctions: In the 2012 round, many contention sets (when multiple applicants applied for the same or a confusingly similar string) were resolved through private auctions. A public announcement might encourage a competitor to enter the process, hoping to force a private auction and get a payout, even if they had no real intention of operating the TLD.
• Contention Resolution in 2026: ICANN is making changes to the 2026 round to address some of the issues from 2012. For example, private resolution of contention sets is now prohibited, reinforcing transparency and fairness. This might reduce the incentive for "speculative" applications aimed at a quick payout.

2. Strategic and Legal Considerations

• Confidentiality: Keeping the application confidential allows a company to maintain a strategic advantage. It prevents competitors from knowing the company's plans, budget, and the specific strings they are targeting.
• Flexibility: An applicant may have multiple strings in mind or may be working on a more complex strategy. Announcing a single string prematurely could limit their flexibility if they later decide to change course or if they find out about unexpected competition.
• Intellectual Property: Announcing an application could also draw unwanted attention from parties with similar trademarks or intellectual property, potentially leading to legal objections.

3. The New Features of the 2026 Round

ICANN has introduced several new elements for the upcoming round that directly impact the strategy for handling competition:

• Replacement Strings: Applicants can now include a "Replacement String" in their application. If their primary string ends up in a contention set on Reveal Day, they can choose to switch to their alternative string at no additional cost. This provides a strategic escape hatch to avoid auctions and disputes.
• No Private Auctions: The prohibition of private auctions means that contention sets must be resolved through a more public and structured process, such as a community priority evaluation or a public auction. This makes the process more transparent and potentially less lucrative for speculative applicants.
• Registry Service Provider (RSP) Pre-Evaluation: The new RSP program allows service providers to be pre-evaluated by ICANN. This streamlines the technical review for applicants who use an approved RSP, making the process smoother and faster.

Conclusion: A Shift in Strategy

In the 2012 round, public announcements were a more viable strategy to deter competition, especially with the prevalence of private auctions.

For the 2026 round, the landscape has changed. The introduction of replacement strings and the prohibition of private auctions significantly reduces the incentive for "bad faith" competition. As a result, many applicants may find it more beneficial to keep their intentions confidential until the application is submitted. This allows them to maintain a competitive advantage, retain flexibility, and avoid attracting unnecessary attention or potential legal challenges before "Reveal Day."

The new rules and mechanisms put in place by ICANN are designed to make the process more predictable and less about who can "bluff" their way to an advantage, which ultimately reduces the need for public announcements as a competitive strategy.

Is "Champagne", as a Geographical Indication, ready for .CHAMPAGNE new gTLD?

The readiness of "Champagne" as a Geographical Indication (GI) for a .CHAMPAGNE new gTLD is a complex issue that involves both the established legal protection of the name and the specific requirements of ICANN's new gTLD program.

Here is a breakdown of the key factors:

Legal Protection of "Champagne" as a GI

• Strong and Long-standing Protection: "Champagne" is one of the most well-known and strongly protected GIs in the world. Its protection dates back to French law in the early 20th century and is recognized internationally through treaties and agreements. The name can only be used by producers of sparkling wine from the Champagne region of France.
• Active Defense by the CIVC: The Comité Interprofessionnel du Vin de Champagne (CIVC) is the interprofessional body that actively defends the name "Champagne" globally against misuse and infringement. They have a long history of legal action and are well-versed in intellectual property disputes.
• GI vs. Trademark: While a GI is not the same as a trademark, it serves a similar function in protecting the name's association with a specific product from a specific region. The CIVC has successfully argued for the protection of "Champagne" as a GI in various legal forums, even in cases where they didn't hold a trademark.

Readiness for a .CHAMPAGNE gTLD

The next round of new gTLD applications is expected to open in April 2026. The readiness of "Champagne" for a new gTLD is determined by the specific rules and requirements of ICANN's program, particularly for "geographic gTLDs."

• Community and Geographic Applications: ICANN's application process has a specific track for geographic names, which includes places, regions, and communities. The "Champagne" GI is a perfect example of a community-based application.
• Governmental Support: A crucial requirement for a geographic gTLD is the need for formal support or non-objection from the relevant government or public authority. For .CHAMPAGNE, this would require backing from the French government or an appropriate regulatory body. Given the strong legal protection and national importance of the name, it is highly likely that such support would be secured.
• Applicant and Operational Readiness: The entity applying for the gTLD (most likely the CIVC or an entity they designate) must demonstrate the technical, financial, and operational capacity to run a registry. This is a significant undertaking that requires a detailed business plan, a solid financial backing, and a partnership with a qualified registry service provider.
• Potential for Objections: The application for a .CHAMPAGNE gTLD would be subject to a public comment and objection period. While the legal rights to the name are very strong, there could be objections from various parties on different grounds, such as string confusion or public interest. The CIVC's long history of defending the name would be a significant advantage in this process.

Conclusion

Based on the strong legal and institutional framework surrounding the "Champagne" Geographical Indication, it is highly ready for a .CHAMPAGNE new gTLD. The established protection, the active defense by the CIVC, and the clear community and geographic connection align perfectly with the requirements of ICANN's new gTLD program. The primary remaining steps would be the formal application process itself, including securing governmental support and demonstrating the technical and financial capacity to operate the registry.

What is the best way to fail a new gTLD project in 2026?

1. Ignore the New ICANN Applicant Guidebook and Timelines

The next round of new gTLD applications is anticipated to open in 2026, with a final Applicant Guidebook (AGB) due to be published in late 2025. A surefire way to fail is to ignore the new rules and deadlines.

• Don't read the new AGB: A significant amount of the information from the 2012 round is still relevant, but ICANN has been working on a new framework since then. Ignoring the updated guidelines will likely lead to an incomplete or non-compliant application.
• Miss the application window: The 2026 application window is expected to be condensed. Failing to prepare and submit your application within this short period will guarantee failure.
• Disregard new requirements: The new round will likely have stricter technical, compliance, and abuse-mitigation requirements. Not including a robust plan for handling DNS abuse and other issues will be a red flag for evaluators.

2. Lack of a Cohesive Business Plan and Strategy

A new gTLD is a long-term investment that requires a well-defined strategy. To fail, simply skip this step.

• Don't have a clear purpose: Submitting an application without a solid plan for what you will do with the gTLD will result in a project with no demand and no return on investment.
• Fail to budget properly: The application fee alone is substantial (estimated to be around $227,000). This doesn't include legal, technical, and marketing costs. To fail, underestimate these expenses dramatically.
• Don't build a marketing plan: A TLD is not a "build it and they will come" business. To ensure failure, assume that simply launching the TLD will generate a user base. Without a plan to build demand, your TLD will languish with no registrations.

3. Fail to Secure the Right Partners and Internal Support

Operating a new gTLD is a complex technical and legal undertaking. To fail, try to do it all yourself or pick the wrong partners.

• Don't engage a Registry Service Provider (RSP): RSPs provide the essential technical infrastructure for operating a TLD. Without a qualified and pre-evaluated RSP, your project will likely face technical rejection or a host of operational problems.
• Lack of legal and financial advisors: The application process is legally and financially complex. Attempting to navigate it without specialized legal and financial expertise will lead to critical errors.
• No internal stakeholder alignment: The new gTLD process requires coordination across different departments, including legal, marketing, and IT. To fail, keep the project siloed and a secret until it's too late.

4. Overlook Technical and Security Requirements

ICANN has stringent technical and security requirements to ensure the stability and security of the internet. A great way to fail is to ignore them.

• Don't implement proper DNS security: Fail to use DNSSEC and other modern security protocols. This will not only violate ICANN's requirements but also make your TLD a target for malicious activity and cause a loss of user trust.
• Ignore the importance of a robust infrastructure: Fail to have a resilient DNS infrastructure with geographic diversity and a comprehensive disaster recovery plan. This will result in poor performance and potential downtime, which can lead to your TLD being removed from the root zone.
• Allow abuse to run rampant: A high rate of spam, phishing, and other malicious activities will lead to your TLD being delisted by major search engines and email providers, effectively making it unusable and ensuring its failure.

Does it make sense to create a .META new gTLD and why?

It would be challenging to create a .META new generic Top-Level Domain (gTLD), and it's highly likely that Meta Platforms, Inc. would be the only entity to successfully apply for and operate it. The rationale behind this is primarily centered on trademark and intellectual property rights.

Why It's Unlikely for Others to Create .META

The primary hurdle is that META is a highly recognized and protected trademark owned by Meta Platforms, Inc. The Internet Corporation for Assigned Names and Numbers (ICANN), the organization responsible for managing the new gTLD program, has mechanisms in place to protect trademarks and intellectual property during the application process.

• Legal Rights Objection: A central part of the new gTLD application process is the "Legal Rights Objection." If another entity were to apply for the .META gTLD, Meta Platforms, Inc. could file a formal objection, arguing that the string infringes on their existing legal rights. Given the global recognition and massive investment in the "Meta" brand, this objection would almost certainly be successful.
• "DotBrand" gTLD Category: The ICANN new gTLD program has a specific category for "DotBrand" gTLDs. These are TLDs created for a single company's exclusive use, such as .google or .apple. This is the most logical path for a company like Meta to secure and manage its own brand-specific TLD. The application process for a DotBrand requires the applicant to demonstrate ownership of the trademark and a plan for its use.

The Business Case for Meta Platforms, Inc.

For Meta Platforms, Inc., creating a .META gTLD makes perfect business and strategic sense, and is in line with what other major corporations have already done.

• Brand Protection and Consolidation: A .META gTLD would allow Meta to consolidate its online presence and protect its brand from cybersquatting, phishing, and other malicious activities. They could create domains like connect.meta, about.meta, or jobs.meta, ensuring that all official content is hosted under their exclusive TLD.
• Enhanced Trust and Security: An exclusive TLD signals to users that the website is officially associated with the company. This helps build trust and ensures that users are not visiting a fake or fraudulent site.
• Marketing and Branding: A branded TLD is a powerful marketing tool. It reinforces the brand identity and creates a memorable, unique online address.
• Control and Flexibility: Owning the gTLD gives the company complete control over its domain name policy, naming conventions, and future expansion. It provides a flexible platform for innovative uses that are not possible with traditional TLDs.

In conclusion, while it's technically possible for an entity to apply for the .META gTLD, the application would likely be rejected due to legal rights objections from Meta Platforms, Inc. For Meta, however, creating a .META gTLD is a logical and strategic move for brand protection, security, and marketing.

New gTLDs and LinkedIn: what could be the use of a ".linkedIn" new domain name extension in 2026?

A .linkedin new gTLD (generic Top-Level Domain) could be a powerful strategic asset for LinkedIn, offering a wide range of uses in 2026. This type of gTLD is a ".brand" domain, and it would give LinkedIn complete control over its own online ecosystem, allowing for enhanced branding, security, and a streamlined user experience.

Here are some of the potential uses for a .linkedin new domain name extension in 2026:

1. Enhanced Security and Trust:

• Combatting Phishing and Scams: One of the most significant advantages is the ability to create a secure and trusted environment. Phishing attacks that impersonate LinkedIn are a major problem. A .linkedin TLD would allow the company to guarantee that any site ending in .linkedin (e.g., login.linkedin, jobs.linkedin) is authentic and secure. Users would learn to trust the .linkedin extension, making it easier to spot and avoid fraudulent sites.
• Centralized Security Management: Owning the TLD would give LinkedIn a single point of control for all of its domain names, making it easier to enforce security protocols and respond to threats.

2. Brand Control and Marketing:

• Creating a Unified Brand Experience: A .linkedin TLD would reinforce the brand's identity and create a more cohesive online presence. It would be a powerful marketing tool, instantly recognizable and memorable to users.
• Creative and Memorable URLs: LinkedIn could use the TLD to create clear, simple, and memorable web addresses for specific services or campaigns. For example:
  • jobs.linkedin
  • courses.linkedin
  • news.linkedin
  • careers.linkedin
  • support.linkedin
  • events.linkedin
• Future-Proofing the Brand: As the digital landscape continues to evolve, owning a .linkedin TLD would give the company the flexibility to adapt its online presence without being constrained by the availability of domain names on other TLDs like .com.

3. Streamlined User Experience:

• Improved Navigation: A .linkedin TLD would simplify the user journey. Instead of navigating through subdomains or different TLDs for various LinkedIn services, users would know that all official services are under the .linkedin umbrella.
• Internal DNS Structuring: For a large company like LinkedIn, a .linkedin TLD could simplify internal network and domain management, making it easier to manage different departments, projects, or applications.

4. Potential for Innovation:

• Partner and Verified User Domains: LinkedIn could explore the possibility of offering .linkedin domains to its verified business partners or even to premium users. This would create a powerful ecosystem of verified professional identities, further solidifying LinkedIn's position as a platform for professional networking and business. For example, a trusted partner could have a domain like partnername.linkedin.
• Integration with Future Technologies: As new technologies like AI and blockchain become more prevalent, a .linkedin TLD could be a platform for new, innovative services that require a trusted and branded online space.

In short, a .linkedin TLD would not just be a new domain extension; it would be a fundamental part of LinkedIn's digital infrastructure, giving the company a competitive advantage in terms of security, branding, and user trust. The next round of new gTLDs is expected in 2026, making it a key strategic consideration for major brands like LinkedIn.