New Domain Extensions 2026: The ICANN New gTLD Round Explained

ICANN published the list of applications for its 2026 round of new generic top-level domains on 7 October 2026: 1,615 of them. If you own a website, you have probably seen the headlines promising a wave of fresh extensions. Almost everyone gets one thing wrong: none of these can be registered yet. Not one. Delegation is estimated to start around 15.5 months after String Confirmation Day (17 November 2026), which puts the earliest realistic availability in early 2028. Read this before you panic-buy anything or rethink your domain strategy.

What follows covers what the 2026 round is, how it differs from 2012, the Reveal Day numbers, the timeline from now to delegation and what a .brand extension costs. It also asks whether any of this helps your SEO (spoiler: Google settled that in 2015). Last comes a developer section on Universal Acceptance, which will stop your forms rejecting valid domains.

What the 2026 round actually is

A generic top-level domain is the bit after the last dot: .com, .org, .shop, .bank. Periodically, ICANN runs rounds in which organisations can apply to operate a brand new one. The application window for this round ran from 30 April 2026 to 12 August 2026. On 7 October, ICANN revealed every applied-for string and the entity behind it.

The last round at this scale came in 2012. Per ICANN, it produced more than 1,200 new gTLDs, including brand extensions like .microsoft and .sky, geographic names such as .africa and .berlin, and general terms like .bank and .eco. It was only the second major expansion in over a decade.

What is different this time? The programme runs on the 2026 Round Applicant Guidebook, which the ICANN Board adopted at ICANN84 with publication by 30 December 2025. One notable rule change: closed generic gTLDs are not permitted in this round unless ICANN approves a methodology for them, following a Board decision in January 2024. A closed generic would be a company running a common dictionary word as an extension and refusing to let anyone else register under it. That door is shut for now.

Then there is the Applicant Support Program. Of the 1,615 applications, 51 came through it, a route aimed at applicants who could not otherwise afford the fees. The fees are covered below, because they are the reason you are not seeing individuals apply for vanity extensions.

Reveal Day by the numbers

ICANN published this data on 7 October 2026. It reflects primary string applications as of that date, and the final figures are confirmed on String Confirmation Day.

Category	Count
Total applications	1,615
Brand applications	333
Community-based applications	16
Self-identified geographic names	15
IDN applications	21
Variant applications	9
Applicant Support Program applications	51

And by region, which is where it gets interesting:

Region	Applications
North America	864
Europe	506
Asia / Australia / Pacific	218
Africa	16
Latin America and the Caribbean	11

North America and Europe together account for 1,370 of the 1,615. Africa and Latin America combined submitted 27. Whatever you think the next generation of the DNS looks like, the applications are concentrated in two regions. The 51 Applicant Support Program applications are a deliberate attempt to widen that. But the skew is still stark.

The 333 brand applications are the headline number for most readers. These are companies applying to run their own extension. Variant applications (9 of them) cover strings with equivalent forms in other scripts such as Arabic or Chinese, which matters for internationalised domains.

The timeline: now to delegation

This is the section to screenshot. Identity Digital laid out the operational phases in its 19 October 2026 analysis, "Beyond Reveal Day", and it is the clearest breakdown of what happens next. Reveal Day did not open any registrations. It started a clock.

Phase	Dates	What happens
Replacement Period	8 to 21 October 2026	Applicants in contention may switch to an eligible replacement string
String Confirmation Day	17 November 2026	ICANN publishes the final list of strings and exact-match contention sets
Withdrawal refund deadline	by 27 November 2026	Withdraw and get a 65% refund ($147,550)
Community input and objections	17 Nov 2026 to 16 Mar 2027	Public comments, singular/plural notices, GAC Early Warnings, formal objections
String evaluation	180 days from 17 Nov 2026	Similarity, name collision, safeguards, geographic, singular/plural reviews
Prioritization draw	first half of 2027	Sets the order for evaluation and contention resolution
Delegation begins	~15.5 months after 17 Nov 2026	Estimated per the Applicant Guidebook

Do the arithmetic on that last row. Add 15.5 months to 17 November 2026 and you land roughly in early 2028. That is the Applicant Guidebook estimate for when delegation starts, and delegation is just the first extensions going live in the root zone. Public registration for any given TLD comes after that, once the registry operator runs its sunrise and general availability phases.

So when someone tells you "new domain extensions are coming in 2026", they are half right and fully misleading. The applications came in 2026. The domains do not.

What a .brand TLD costs and who it suits

This is why there are 333 brand applications and not 33,000. Per ICANN's cost FAQ, the expected evaluation fee is USD 227,000, and that buys only the evaluation of your application. It is set on a cost-recovery basis, so the programme funds itself without dipping into ICANN's operating budget. Registry infrastructure, legal counsel, objection defence and ongoing operations all sit outside it.

There is a partial escape hatch. Per Identity Digital, applicants who withdraw by 27 November 2026 receive a 65% refund of the application fee, which is $147,550 back. That is 65% of the USD 227,000 evaluation fee. ICANN built in an early exit for applicants who discover their string is hopelessly contested or objected to.

Who should run a .brand TLD? Realistically, large organisations with a long-term digital identity play. Think a bank wanting every customer-facing property on a namespace only it controls, or a global brand tired of defensive registrations across hundreds of extensions. If you are a founder of a 20-person startup, this is not for you, and no credible advisor would tell you otherwise. The fee alone rules it out, and the SEO case (next section) does not exist.

If you genuinely need help thinking through whether a brand TLD fits a larger digital strategy, that is a conversation worth having properly rather than reacting to a headline. Our team covers this kind of architecture work on the contact page, and you can see how we price larger engagements on the pricing page.

Does a new TLD help SEO?

Short version: no. Google answered this on the Search Central blog on 21 July 2015, and the answer has not changed. Their systems treat new gTLDs like .com and .org. Keywords in a TLD give no advantage and no disadvantage, and a .brand TLD gets no more weight than a .com. Region-looking extensions like .london or .bayern are treated as generic gTLDs, not as geotargeting signals.

That 2015 post also confirms that IDN TLDs such as .みんな can be crawled and indexed. Google treats the Punycode version as equivalent to the unencoded one. If you run an internationalised domain, you still use UTF-8 for the path and query string.

So what actually moves the needle? The same things that always did:

• Content that answers real queries. The TLD is not a ranking factor; the page is.
• Site performance. Core Web Vitals, fast rendering, clean markup. This is where build architecture matters, which is why we lean on frameworks like Astro and Next.js for genuinely fast sites.
• Links and authority. A new TLD starts with zero authority. A migration to one throws away whatever you have built.
• User trust. This is the one genuine argument for a brand TLD, and it is a branding argument, not an SEO one. Users may trust an email or link on a company's own extension more than one on a lookalike .com. That is perception, not ranking.

Ignore anyone who waves a survey at you claiming new extensions "improve SEO". Google's own documentation contradicts the claim, and Google is the one doing the ranking.

Developers: the Universal Acceptance problem

This part is for anyone who writes code. Universal Acceptance (UA) is the principle that every domain name and email address should work in every internet-enabled application. In practice, plenty of apps and forms still reject newer TLDs and email addresses on them, a problem that, per Identity Digital, has existed since TLDs expanded beyond .com in 2002. The 2026 round will add more long and unusual strings, and your validators need to cope.

The classic offender is a regex that assumes TLDs are two to four lowercase letters. That was never correct. It fails hard on extensions like .photography or internationalised strings, and you will find this kind of validator all over legacy codebases:

// WRONG: rejects long TLDs, IDNs, and anything over 4 chars
function isValidEmail(email) {
  const re = /^[^@\s]+@[^@\s]+\.[a-z]{2,4}$/i;
  return re.test(email);
}

isValidEmail('hello@agency.photography'); // false (wrong!)
isValidEmail('user@example.london');      // false (wrong!)

That {2,4} is the bug. It silently drops valid customers. The fix is to stop limiting TLD length and to normalise internationalised domains to Punycode before you check anything:

// BETTER: no length cap on the TLD, handles IDNs via URL/punycode
function isValidEmail(email) {
  if (typeof email !== 'string') return false;
  const at = email.lastIndexOf('@');
  if (at < 1 || at === email.length - 1) return false;

  const local = email.slice(0, at);
  const domain = email.slice(at + 1);

  // Normalise internationalised domains to ASCII (Punycode)
  let asciiDomain;
  try {
    asciiDomain = new URL(`http://${domain}`).hostname;
  } catch {
    return false;
  }

  // Must have at least one dot and a non-empty TLD label
  const labels = asciiDomain.split('.');
  if (labels.length < 2) return false;
  if (labels.some((l) => l.length === 0)) return false;

  // Local part: keep it permissive, let the mail server be authoritative
  return local.length > 0 && local.length <= 64;
}

isValidEmail('hello@agency.photography'); // true
isValidEmail('user@example.london');      // true

Two principles apply. First, do not cap TLD length. Second, the only system that truly knows whether an email is deliverable is the receiving mail server, so client-side validation should catch obvious typos, not gatekeep. Over-strict validation costs you real signups today, before a single 2026-round extension even exists. If you are building forms into a headless CMS stack, bake UA-aware validation in at the schema level so it is consistent everywhere.

Your 18-month checklist

You do not need to do much, but you do need to do the right few things at the right time. Here is what site owners should actually track between now and delegation.

• Do not buy speculative domains now. You cannot register any 2026-round extension yet. Anyone selling you one is selling vapour or an existing 2012-round domain dressed up as new.
• Watch the String Confirmation list on 17 November 2026. This is when the final list of strings and contention sets becomes definitive. If an extension relevant to your brand is applied for, this is where you find out for certain.
• Register with the Trademark Clearinghouse if you hold marks. This is the mechanism that gives trademark owners sunrise access and infringement notifications when new registries launch. Get your marks in before any extension you care about reaches its launch phase.
• Plan defensive registration timing, do not act early. Defensive registrations happen during each registry's sunrise period, which is years away for 2026-round strings. Note the extensions to defend; do not spend anything yet.
• Audit your own validators for Universal Acceptance. This is the one genuinely actionable developer task today. Fix the email and domain validation so you stop rejecting valid addresses.
• Ignore SEO pitches tied to new TLDs. Google treats them like .com. Invest that budget in content and performance instead.

The 2026 round is a slow-moving infrastructure event, not a land grab you need to join this quarter. Watch the String Confirmation list and fix your validators. Then get on with building things that rank on merit.

FAQ

When can I register a new domain extension from the 2026 round?

Early 2028 at the earliest. Delegation is estimated to start around 15.5 months after String Confirmation Day (17 November 2026), per the Applicant Guidebook. Public registration for any extension comes after delegation, once that registry runs its own sunrise and general availability phases.

Reveal Day on 7 October 2026 only made the applications public. It opened no registrations at all.

How many applications did ICANN receive in the 2026 round?

ICANN received 1,615 applications, revealed on 7 October 2026. That includes 333 brand applications, 16 community-based, 15 self-identified geographic names, 21 internationalised domain name applications and 9 variant applications. Of the total, 51 came through the Applicant Support Program.

North America led by region with 864. Europe followed with 506, then Asia/Australia/Pacific with 218, Africa with 16, and Latin America and the Caribbean with 11.

How much does it cost to apply for a new gTLD?

The expected evaluation fee is USD 227,000, per ICANN's cost FAQ. It is set on a cost-recovery basis, so the programme funds itself. That fee covers evaluation only. Registry infrastructure, legal costs, objection defence and ongoing operations are all excluded.

Applicants who withdraw by 27 November 2026 receive a 65% refund, which is $147,550, according to Identity Digital.

Do new domain extensions help SEO?

No. Google stated on its Search Central blog in July 2015 that new gTLDs are treated like .com and .org, and that keywords in a TLD give no ranking advantage or disadvantage. A .brand extension gets no more weight than a .com.

Content and site performance affect rankings, as do authority and user trust. A new TLD starts with zero authority, so migrating to one can set you back rather than help.

How is the 2026 round different from 2012?

The 2026 round runs on the new Applicant Guidebook, which the ICANN Board adopted at ICANN84 and which was published by 30 December 2025. One key change stands out: closed generic gTLDs are not permitted unless ICANN approves a methodology, following a Board decision in January 2024.

The 2012 round produced more than 1,200 new gTLDs, including .microsoft, .sky, .africa, .berlin, .bank and .eco. The 2026 round is the first major expansion since then.

What is Universal Acceptance and why does it matter for my website?

Universal Acceptance means every domain name and email address should work in every internet-enabled application. In practice, many forms and apps still reject newer TLDs and emails on them, a problem that has existed since TLDs expanded beyond .com in 2002, per Identity Digital.

For site owners, the practical risk is over-strict validation rejecting valid customer emails today. Fixing your validators to drop TLD length caps and handle Punycode is the one actionable task before any 2026 extension launches.

Should my small business apply for its own TLD?

Almost certainly not. The expected evaluation fee alone is USD 227,000, before infrastructure, legal and operational costs. Brand TLDs suit large organisations with a long-term digital identity strategy, which is why only 333 of the 1,615 applications were brand applications.

There is no SEO benefit to justify the cost for a small business, since Google treats these extensions like any other gTLD.

What should I do during the String Confirmation and objections window?

Watch the final list of strings and contention sets that ICANN publishes on String Confirmation Day, 17 November 2026. If an extension relevant to your brand appears, that is your cue to track it. The community input and objections window runs from 17 November 2026 to 16 March 2027.

If you hold trademarks, register them with the Trademark Clearinghouse so you get sunrise access and infringement notices when relevant registries eventually launch.