The internet is buzzing about ICANN’s upcoming 2026 application window for new generic Top-Level Domains (gTLDs). But before you start dreaming up your own .awesome or .brand, it’s essential to understand gTLD eligibility – the rules that decide who can actually apply. This is the critical, non-negotiable question you have to answer: “Am I even allowed to apply?”
This isn’t just a box to tick; it’s the very first hurdle that determines if your gTLD ambition has any shot at becoming a reality. Many aspiring digital moguls miss the eligibility basics and end up wasting a colossal amount of time and money on an application that’s dead on arrival.
Getting the gTLD eligibility 2026 requirements wrong is like showing up to a marathon in flip-flops – you’re not getting past the starting line. We see many aspiring registry operators, fueled by fantastic ideas for the next .shop or .club, trip at this very first step because they overlooked the fundamental ICANN gTLD applicant requirements. Their journey ends before it even starts, along with a hefty, non-refundable portion of their application fee. Ouch.
Think of this guide as your no-nonsense breakdown of ICANN’s eligibility rules. We’ll cut through the dense legalese to explain exactly who can apply, what they need, and the absolute deal-breakers that will get an application thrown out. Consider it your first essential checkpoint.
The challenge is definitely steeper this time around. The 2026 application round is a major step up in complexity from the last one in 2012. Back then, applicants had to answer about 50 questions covering their ownership, finances, and technical plans. A recent ICANN webinar revealed a shocking statistic for this round.
For 2026, that number has exploded to over 200 questions. This signals a much more rigorous and detailed evaluation process, leaving far less room for error. You can discover more insights about the evolving gTLD application process to see just how much has changed.
Key Takeaway: Answering “Am I allowed to apply?” isn’t a formality. It’s the foundational step that decides whether you can even enter the race to secure your own piece of internet real estate.
Meeting TLD application eligibility is the first, non-negotiable step. In the sections that follow, we’ll dive into the specifics – from the types of legal entities allowed to the good faith requirements that prove you’re a serious player. But first, let’s get you prepared.
Think of ICANN’s new gTLD program as the most exclusive tech party of the decade. Before you can even think about what your gTLD string will be, you need to get your name on the guest list. And believe me, the bouncer – ICANN – is incredibly selective.
The first, most fundamental rule for gTLD eligibility 2026 is that only established legal entities can apply.
This means individuals and sole proprietors, no matter how brilliant their idea for .pizza or .ninja, simply aren’t invited. If you’re a solo entrepreneur with a vision for the next great TLD, your first move isn’t brainstorming a logo; it’s forming a legal corporation or organization. ICANN needs to see a formal structure with real legal accountability.
So, who actually gets a seat at this table? The list is strictly limited to verifiable, legally constituted organizations. This is one requirement that has absolutely no wiggle room.
.dev to startups hoping to launch an open gTLD like .music.eco is a great example.nyc or .berlinA critical point to remember is that ICANN doesn’t deal in hypotheticals. Your entity must exist at the time of application. You can’t apply as a “to-be-formed” joint venture or a company that’s still in the incorporation process. All the paperwork has to be filed, signed, and officially recognized beforehand. No “future entities” allowed. For brand TLDs, you must also show a clear link to a registered trademark, and this comes with its own conditional evaluation fee to prove it.
This infographic breaks down the hierarchy of key requirements, starting with the absolute necessity of a valid legal entity.
As the visual makes clear, your legal status is the bedrock of your entire application. Without it, everything else – your financial plans, your technical capabilities – is completely irrelevant.
| Applicant Type | Eligibility Status | Reasoning and Examples |
|---|---|---|
| Registered C-Corp/LLC | Eligible | A legally recognized business entity with defined liability. Example: A tech company applying for .cloud. |
| Individual/Sole Proprietor | Ineligible | Lacks the formal legal structure and separation ICANN requires for accountability. |
| Not-Yet-Formed JV | Ineligible | The entity must legally exist at the time of submission. Future promises don’t count. |
| Government Agency | Eligible | Public entities are permitted. Example: The city of Paris applying for .paris. |
| Registered Non-Profit | Eligible | Legally constituted organizations can apply. Example: A non-profit for .eco. |
| Shell Company (No Assets) | Likely Ineligible | Fails financial viability tests and may be seen as lacking operational substance. |
Ultimately, proving who can apply for a gTLD comes down to documentation and legal standing. For those representing communities with fewer resources, it’s worth noting that ICANN has programs designed to help support the application fee. You can learn more about how ICANN’s Applicant Support Program helps you get a gTLD for under $60k and see if your organization qualifies. Getting your entity right from the start prevents a world of headaches later on.
Alright, so you’ve got your paperwork in order and proved you’re a legally recognized entity, not just a brilliant idea sketched on a napkin. That’s a huge first step toward gTLD eligibility 2026.
But ICANN’s job isn’t done yet. Now they need to dig deeper, past the corporate filings, and get a real sense of your intentions.
This is where the “bona fide intent” requirement comes into play, a cornerstone of the ICANN gTLD applicant requirements. It’s not just another box to check; it’s a formal pledge that you actually plan to operate your gTLD as a real, functioning registry. It’s ICANN’s main line of defense against digital prospectors looking for a quick flip. You can’t just apply for .music with the secret plan of auctioning it off to the highest bidder.
Think of it this way: ICANN is handing you the keys to a piece of the internet’s core infrastructure. They need to know you’ll be a responsible steward, not just a squatter hoping to sell the land for a fast profit. This rule exists to weed out purely speculative “land grabs” where an applicant has no real plan, team, or desire to actually run a registry. ICANN can and will reject applications it deems not in good faith.
The implication is crystal clear: don’t apply if you’re not prepared to run a registry.
Key Insight: Proving bona fide intent is all about showing ICANN you have a legitimate, well-developed plan for your TLD. It’s about demonstrating you have the means and the commitment to manage, market, and maintain your little corner of the internet.
Take .eco, for example. Its operators had a clear mission to create a trusted online space for the environmental community. Amazon’s application for .aws was another no-brainer, directly tied to its massive cloud services brand. These are perfect examples of good faith intent.
So, how do you actually prove your intentions are pure? While the application has a formal attestation, your entire submission needs to back up that claim.
.bank) or supports your brand’s mission (like .google)Ultimately, this requirement ensures that new gTLDs add real value to the internet ecosystem. It’s a foundational part of TLD application eligibility that separates the serious players from the speculators. If your legal entity gets you in the door, your bona fide intent is what lets you stay.
So, you’ve proven you’re a legitimate legal entity with good intentions. Congratulations, you’ve made it past the velvet rope. Now it’s time to learn the house rules, and when it comes to the gTLD eligibility 2026 process, ICANN’s are non-negotiable.
This next phase is all about formally agreeing to the terms of the game, and it starts with their digital gateway.
The entire show is run through one central portal: the TLD Application Management System (TAMS). Don’t even think about couriers, paper submissions, or faxes from 1998. If your information isn’t correctly entered into TAMS, it simply doesn’t exist in ICANN’s eyes. This is the only way in.
Using TAMS comes with a critical consequence that catches many people off guard, especially if you plan to apply for more than one gTLD. The moment you submit your first application – let’s say for .brand - your core organizational information gets permanently locked in.
What does that mean? If your company also wants to go after .store and .shop, every single one of those applications must come from the exact same legal entity. You can’t use different subsidiaries or joint ventures for different applications under one main applicant. It’s a strict one-entity-per-applicant rule.
Key Takeaway: The very first application you submit sets the legal and organizational foundation for all others from your company. There are no do-overs here, so it’s absolutely crucial to get your primary entity right from the get-go.
This rule is in place to stop applicants from creating messy, confusing corporate webs. ICANN needs a single, clear point of contact and accountability for each applicant, no matter how many TLDs they’re trying for. For example, a global conglomerate can’t use its European arm for one TLD application and its North American division for another. Everything has to flow through that one, pre-defined legal entity.
Alongside getting the hang of TAMS, every applicant has to formally accept the TLD Application Terms & Conditions. This isn’t your average user agreement; it’s a hefty legal document that lays out every single obligation, rule, and potential penalty. It’s not a negotiation – it’s a take-it-or-leave-it deal that governs the entire journey.
These terms are spelled out in detail in the official Applicant Guidebook (AGB), which is the bible for this whole process. The AGB covers everything from fees to how disputes are handled. For a closer look, check out our analysis now that the draft applicant guidebook has been released and get ready to acquire your own gTLD.
Signing this document is the final handshake before your application officially enters the evaluation gauntlet. It formalizes your commitment and makes sure you understand the high stakes of managing a piece of the internet’s core infrastructure. Following these ICANN new gTLD round rules isn’t just suggested; it’s the price of admission.
While some parts of the gTLD eligibility 2026 process are nuanced, others are bright, uncrossable lines. Step over one, and your application is done. These aren’t flexible guidelines; they are absolute deal breakers that will stop your application dead in its tracks.
Understanding these red lines is just as critical as knowing who can apply. Ignoring them is a surefire way to waste hundreds of thousands of dollars on an application that’s doomed before an ICANN evaluator even opens the file.
First up is the ban on “closed generics.” In plain English, you can’t apply for a generic, dictionary-word TLD and then wall it off for your exclusive use. Imagine applying for .book only to declare that your company is the only one allowed to register domains under it. ICANN has put its foot down on this. Generic TLDs are meant to be open resources, and locking one down is seen as anti-competitive and is outright banned (unless a future policy changes this). If you want an exclusive TLD, you need a registered trademark for a .brand extension.
Next, a whole host of potential TLD strings are completely off-limits. ICANN keeps a long list of reserved and restricted names that are permanently blocked from registration. The TLD Application Management System (TAMS) is even programmed to automatically reject any application for these strings on sight. If your dream TLD lands in one of these buckets, save your pixels – it’s a hard no:
Before you spend a single dollar, meticulously comb through the official ICANN Applicant Guidebook’s list of reserved and restricted strings. It’s a simple check that can save you a world of pain and wasted money. Avoiding these common pitfalls is mission-critical for anyone serious about successfully navigating the ICANN new gTLD round rules.
ICANN isn’t just looking at your business plan; they’re looking at you. Every key individual tied to an application has to go through a mandatory and very thorough background check.
This level of scrutiny applies to:
The check is designed to weed out anyone with a history of cybercrime, fraud, or other serious legal issues that would make ICANN question their integrity. If any key person fails this check, the entire application can be thrown out. ICANN needs to know you’ll be a responsible steward of internet infrastructure, and a clean record isn’t negotiable.
Finally, every applicant must be in full compliance with international law – specifically, with global sanctions lists from bodies like OFAC. This is a straightforward pass/fail test. If your organization or its key leaders will be checked, and if anyone shows up on a sanctions list, your application is DOA (dead on arrival). This rule ensures the gTLD program operates within established legal frameworks and prevents sanctioned entities from controlling pieces of the internet.
Knowing the rules for gTLD eligibility 2026 is one thing. Actually navigating the common traps that snag even the most buttoned-up applicants is another game entirely. Many well-meaning hopefuls don’t fail because their idea for .fashion or .tech is bad, but because they stumble over entirely avoidable structural and procedural mistakes.
Think of these pitfalls as hidden rocks just beneath the surface. They might look harmless from the deck, but they can tear a hole in your application’s hull in a heartbeat.
One of the most frequent errors we see is the use of a “shell” or “newco” structure. It’s tempting, I get it. Creating a shiny new legal entity just for the gTLD application feels clean and focused. The problem is, if this new company has zero operational history, no real assets, and no formal, legally binding backing from a parent company, ICANN’s evaluators will see right through it and your application risks failure.
Key Takeaway: A brand-new entity with no track record is a major red flag. Your application’s strength comes from the proven stability and resources of an established organization, not a freshly printed certificate of incorporation.
Another classic blunder is trying to “pool” eligibility after the fact. Picture this: two companies decide on a brilliant joint venture for a new TLD. They have a handshake deal and a killer pitch, but the actual JV isn’t legally formed by the submission deadline. Unfortunately for them, their application is dead on arrival.
The ICANN gTLD applicant requirements are rigid on this point: the application has to stand on the merits of a single, existing legal entity at the time of submission. You can’t just staple two companies’ credentials together and hope it holds. That’s not accepted.
[Download Our Free Applicant Eligibility Checklist to Avoid These Mistakes]
So, after wading through all the legal jargon and technical hoops, what’s the real answer to the title? You’re allowed to apply only if you’re a legal entity with good faith intent and real operational capacity.
You’re definitely on the guest list if you’re a formally established legal entity – not an individual or a loosely-defined joint venture. That entity must be acting in good faith, armed with a genuine, documented plan to actually operate a registry for a string like .cpa or .shop, rather than just squatting on digital real estate.
Beyond that, you have to be ready to meet a whole host of strict background, financial, and legal requirements. These aren’t just bureaucratic hurdles; they are the bedrock of your entire application and a core part of the ICANN new gTLD round rules and gTLD eligibility 2026 framework. Eligibility isn’t just a formality – it sets the foundation for evaluation success.
The Big Picture: Eligibility is ICANN’s way of ensuring you are a serious, capable, and trustworthy partner to manage a piece of the internet’s core infrastructure. It proves you have the stability and accountability to play in this high-stakes environment.
Passing these checks shows you’re not a speculator but a potential steward of a small piece of the internet.
Ultimately, meeting the ICANN gTLD applicant requirements is the first, most critical test in what is a long and demanding journey. It separates the dreamers from the doers and establishes the credibility you’ll need for the intense evaluation phases that follow. For a deeper dive into the application process, you can check out TLDz’s expert guide on how to apply for your own TLD.
If you’ve cleared these hurdles and can confidently say your organization meets every single one of these criteria, congratulations! You’ve passed a significant milestone that trips up many aspiring registry operators. But this is just the beginning.
Now comes the next, equally important question: even if you’re eligible, can you afford it? Next we break down the $227,000 fee, refunds, and hidden costs. Stay tuned.
Next, we break down the real numbers in gTLD Financial Projections: How to Pass ICANN’s Toughest Test, including application fees, refunds, and long-term operating costs.
Ready to see if your organization has what it takes? Download our comprehensive Applicant Eligibility Checklist to validate your readiness and confirm you meet gTLD eligibility 2026 requirements. TLDz provides the expert guidance you
Subscribe to Our Monthly Newsletter
Join our mailing list to receive exclusive content only our newsletter members have access to.