What the 2026 new gTLD round means for domain buyers

The ICANN New gTLD Program 2026 Round is not a retail sale of second level names. It is a multi year process for organizations that want to operate an entirely new top level ending in the DNS root. If you buy domains for a website, campaign, or product, you are watching that process from the outside. Purchase decisions for these proposed strings belong in the future, after an ending passes evaluation and eventually opens for public registration.

The application window closed on 12 August 2026 with more than 1,600 primary applications. Many of those filings also included a replacement string, a secondary choice applicants can switch to if their first string lands in contention. That volume sets the stage for the next milestones: Reveal Day, string confirmation, prioritization, objections, and evaluation work that continues through 2027.

The future calendar buyers should watch

ICANN said Reveal Day should occur no later than nine weeks after the window closed, absent extraordinary circumstances, and that it would announce the date and later milestones separately. On Reveal Day, ICANN publishes the applications that passed its administrative check, including the proposed strings and public application details. Until that publication occurs, a responsible buyer should not treat rumored strings as confirmed products.

After Reveal Day comes a short replacement period. Applicants who prepared a secondary string can switch into it if their primary choice is contested, provided the swap does not create new contention. String Confirmation Day then locks the final list. Later steps include community comments, objections, string similarity work, and formal evaluation. Delegation of a successful string, and any later public sunrise or general availability for second level names, sits further downstream.

What this round will not do for retail buyers

It will not create a sudden catalog of new endings you can register next week. Operating a top level domain requires capital, legal review, technical evaluation, and time. Even after Reveal Day, many strings will sit in contention or evaluation for a long stretch. Second level names under those future endings become interesting only after delegation and a public launch schedule.

It also will not replace the need for today’s brand defense. If a company applies for a string that matches your trademark, Reveal Day is your early warning. That is a legal and brand monitoring problem first. It is not a reason to delay registering the .com, country code, or category domain your customers already use.

How to prepare while you wait for 2027 launches

Build a watch list of words that would matter to your customers: the brand, product families, industry terms, cities, communities, and meaningful versions in other scripts. After Reveal Day, compare that list with the published applications. This is monitoring, not a shopping list. An applied for string may change, face objections, enter contention, fail evaluation, remain private to one brand, or never offer public second level registrations.

Treat public availability as a later possibility rather than a promised 2027 product. Each successful registry will set its own launch plan after contracting and delegation. Some registries may serve a closed organization. Others may run a trademark Sunrise, an early access phase, and general availability. Pricing, premium name rules, reserved names, eligibility, and registrar support can differ. None of those retail details can be known from an application count alone.

A registration readiness plan for domain buyers

Separate the extension from the name before the dot

The applicant seeks the right to operate what comes after the dot. A customer later seeks a second level name before that ending. For a fictional future extension called .example, an applicant might operate .example, while a customer might later register mybrand.example. These are different contracts, prices, responsibilities, and timelines. Most readers of this guide are preparing for the second transaction, not applying to run registry infrastructure.

1. Create a brand name inventory. List the company name, major products, common abbreviations, local spellings, and terms customers use when searching.
2. Rank the business risk. Mark which words could confuse customers, create impersonation risk, or open a useful category if they become future extensions.
3. Monitor official milestones. Review Reveal Day, String Confirmation Day, evaluation status, contention, contracting, and delegation rather than relying on promotional forecasts.
4. Prepare a second level shortlist. For each relevant future extension, write three short names and one acceptable fallback before registration pressure begins.
5. Set a total cost ceiling. Budget for application phase pricing, premium tiers, renewal, trademark validation, and possible early access fees before choosing a launch phase.
6. Wait for a verified sales channel. Register only when the extension, launch phase, eligibility, price, and registrar support are confirmed on a real product page.

Understand Sunrise, early access, and general availability

A registry that opens to the public may use several launch phases. Sunrise usually gives eligible trademark holders an early chance to request matching names, often through validated trademark data. An early access phase may let buyers register before general availability at an additional cost that can decline over time. General availability opens registration under the published policy, but premium and reserved names may still carry different prices or remain unavailable. Not every registry uses every phase, so never copy one launch calendar onto another extension.

Treat pre-registration as an expression of interest

A pre-registration service cannot guarantee a domain before registry rules, launch dates, registrar connections, and competing requests are known. If SoxDomains later offers an alert or preorder, the page must explain whether payment is taken, when an attempt occurs, how competing orders are handled, and what happens after failure. Until those terms exist, keep your shortlist and budget ready without treating a form or email alert as ownership.

When SoxDomains should link a future extension

An internal link should appear only when it helps the reader complete a real next step. For a future extension, that means SoxDomains has added the exact TLD to its catalog, mapped the canonical product route, confirmed registrar support, and identified the current launch state. Before those checks pass, the article should describe the process without a buy button. After they pass, the link should state whether the page offers an alert, Sunrise request, early access order, or general registration.

A productive plan does not depend on an uncertain extension

Keep building the brand, product, and naming system while the round advances. Decide how a future domain would be used, which existing site it would support, who would own renewals, and what customer problem it would solve. If the extension never launches publicly, the work still improves naming discipline. If it does launch, your team can act from a prepared brief instead of buying under deadline pressure.

Assign one person to review the round each month and record only changes confirmed by ICANN or the relevant future registry. The log should capture the milestone, publication date, effect on your shortlist, and next review date. This small routine prevents an old prediction from turning into a purchasing assumption and gives the team a clean handoff when responsibility changes.

Do not confuse publication of an application with approval. Keep every candidate marked as unconfirmed until the relevant stage changes in the official program record. Explore domain registration at SoxDomains