Summary

  • ICANN confirmed that 1,616 paid applications are proceeding in the 2026 New gTLD Program round, down from 1,663 submissions. That number records process admission, not root-zone delegation.
  • Reveal Day on 7 October will publish applicants, strings, public application material and initial contention sets. Replacement, confirmation, objections, evaluation, contention resolution, contracting and delegation still follow.
  • Leaders should maintain separate counts for applications, surviving strings, contracts, delegations and actual use. Combining them creates an imaginary namespace and poor investment, policy and operating decisions.

Imagine a board dashboard with a single line: “1,616 new top-level domains.” It is concise, memorable and wrong.

On 22 September, ICANN confirmed that 1,616 paid applications would proceed from the 1,663 submissions recorded when the window closed. The fee receipt matters because an unpaid application normally cannot continue. But it closes only one question: which submissions paid their way into the process. It says nothing yet about which strings survive, which applicants qualify, which disputes are resolved, which contracts are signed or which labels enter the DNS root.

That distinction will become harder to preserve after Reveal Day on 7 October at 18:00 UTC. Public data creates the feeling of a market suddenly arriving. Applicant names, primary strings, variants or replacements, public application sections and contention sets will become searchable. The release will produce real information and real strategic pressure. It will not produce 1,616 operating registries.

Reveal Day changes information, not the root

The 2026 Round program page places disclosure inside a longer applicant journey. Before the reveal, ICANN performs administrative checks, verifies fees and groups identical strings. On the day itself, public portions of applications are opened to scrutiny and exact-string contention becomes visible. This is an important governance event because rivals, governments, communities, rights holders and infrastructure providers can finally see what was claimed.

The result is best described as an inventory of applications that passed an administrative threshold. It is not a product catalogue. ICANN itself says the public Applicant Support System draws data from TAMS and was still being tested, and it cautions against treating non-ICANN lists as authoritative. Even the official public inventory will still describe requested futures.

The current Applicant Guidebook page points to the binding process document, and the frozen current Guidebook PDF shows why no one number can summarize the round. Reveal is followed by a 14-day replacement period, scheduled for 8–21 October. String Confirmation Day is scheduled for 17 November. Only then does the inventory of continuing strings become firmer.

That still is not delegation. The applicant journey proceeds through community input, objections, string evaluation, applicant and application evaluation, contention resolution, contracting, onboarding and delegation. Each stage can change the denominator.

A public comment is neither a vote nor a verdict

From 17 November through 16 March 2027, the scheduled community-input process gives the public ways to submit relevant information. Other channels include GAC early warnings or advice, singular/plural concerns and formal objections. These mechanisms matter. Evidence may expose a geographic conflict, a community claim, rights harm, string confusion or an applicant weakness.

But input should retain its assigned force. A comment is evidence for evaluators, not a plebiscite. Attendance is not authority. A warning is not automatically a rejection, just as the absence of a warning is not approval by every government. Lu Heng's critique of the multi-stakeholder mirage provides a useful discipline: participation is real, while mandate must still be demonstrated. The lesson is not to dismiss participation; it is to stop promoting a bounded process role into general sovereignty.

The same discipline applies to contention. The contention-resolution page explains that applicants seeking identical or confusingly similar strings may need private resolution, community priority evaluation or an auction mechanism. Reveal Day exposes the collision. It does not select the winner.

Payment is admission, evaluation is judgment

The standard application fee is USD 227,000 under the Guidebook's detailed conditions. That price makes the proceeding count commercially interesting, but not substantively predictive. The pre-evaluation stage checks administrative completeness before the more consequential evaluations. The preparation guidance makes clear that applicants have to marshal financial, operational, technical and organizational capacity.

Later evaluation can examine the string, background, finances, operations, registry-service-provider arrangements and conditional requirements. A successful applicant may then enter the Base Registry Agreement. Contracting changes legal authority and obligations. It still does not place the string in the root.

Onboarding, testing and a delegation request follow. Root stability can constrain the rate at which delegations occur. The Guidebook also records a less comfortable boundary: approval, an executed agreement and root delegation do not guarantee immediate or comprehensive Internet functionality. Browsers, mail systems, identity systems, validators and enterprise filters may not recognize new endings. ICANN cannot command every application to accept them.

That is the final gap between a delegated string and a usable namespace. Registrations, renewals, meaningful sites, mail delivery and user recognition are market and implementation receipts, not properties bestowed by the application counter.

Temporary delegation is not a launch

The terminology can itself mislead. ICANN's explanation of temporary delegation describes a time-limited, ICANN-controlled mechanism for collecting DNS data during name-collision assessment. It is not the applicant operating a permanent registry. A monitoring system that counts temporary delegations as launches would confuse an evaluation instrument with commercial operation.

Lu Heng's essay on reality layers names the larger problem. A disclosed application has symbolic and strategic reality. A contract has legal reality. A root entry has technical reality. Resolver and application acceptance have operational reality. Registration and use have market reality. These layers interact, but none can honestly stand in for the others.

His account of a minimum initial specification adds the adoption boundary: publication and procedural legitimacy do not compel implementation. The 2026 round can create options. It cannot, by announcement, create software support or user demand.

Use five ledgers, not one headline

Executives should require five live ledgers. The first counts paid applications and the entities behind them. The second counts confirmed strings after replacement and maps each contention set. The third records evaluation, objections and contention outcomes. The fourth records signed agreements, onboarding and root delegations. The fifth measures acceptance: resolver behavior, application support, registrations, renewals and real use.

The gaps are management information. A large fall between application and confirmation may show portfolio optionality. A long delay between confirmation and contract may expose evaluation or contention risk. A long delay between delegation and meaningful use may show Universal Acceptance or demand failure. Compressing the ledgers destroys those signals.

Reveal Day deserves attention because it turns private ambition into public, challengeable claims. The disciplined response is not to understate that event. It is to describe exactly what became true: the world could inspect 1,616 paid applications. The root had not gained 1,616 TLDs.

Sources