Summary

  • ICANN says it received more than 1,600 primary applications when the 2026 new-gTLD submission window closed on 12 August; more than 1,100 of those applications also carried a replacement-string option.
  • The organisation has not yet confirmed the final application total because full evaluation-fee payment remains part of acceptance, and invoices follow applicant due diligence rather than appearing automatically.
  • Even the paid application count will not be the final string count. Reveal Day opens a 14-day replacement period, after which String Confirmation Day publishes the names that are final for the evaluation process.

The headline is a snapshot, not an inventory

The first number from ICANN’s 2026 new generic top-level domain round is large and newsworthy: more than 1,600 primary applications. It is also easy to misread. At the close of the 15-week window, ICANN described a submission population, not a settled inventory of strings and certainly not a list of future delegations.

That distinction matters because the process now contains three different public counts. The first is the primary applications recorded at the deadline. The second will be the applications that survive payment and administrative checks and are disclosed to the public. The third will be the final applied-for strings after applicants have had the one opportunity the rules give them to switch to a replacement.

As of 22 August 2026, only the first count has been announced, and even that count remains provisional. ICANN’s 13 August notice said the final number of applications could not be confirmed until the full gTLD evaluation fee had been received. The fee is US$227,000 for an ordinary application, subject to approved Applicant Support reductions. An application is not marked paid until the full amount due is received.

Payment timing is less mechanical than the first deadline suggested. On 7 August, ICANN changed the rule so that payment is due by whichever date is later: 19 August at 23:59 UTC, or seven calendar days after the invoice is issued. Invoices are not generated immediately upon submission. ICANN first performs due diligence on the applicant. That means a reader cannot infer from the passing of 19 August that every submitted application has already become a paid application or disappeared from the round.

ICANN said Reveal Day would follow administrative checks and occur no later than about nine weeks after the submission window closed, absent extraordinary circumstances. On that day, the organisation will publish the public portions of the applications and their applied-for strings. Disclosure will make the queue visible, but it will not yet freeze the names.

Why 1,100 alternatives are not 1,100 extra applications

The second number needs even more discipline. More than 1,100 of the primary applications included a replacement string. Under the Applicant Guidebook, a replacement is a pre-filed alternative within the same application. It is not a second application, a second evaluation fee or a second entitlement to a top-level domain.

After Reveal Day, eligible applicants receive 14 calendar days to decide whether to keep the original string or activate the replacement. The election is irreversible. If an applicant does nothing, the replacement option is forfeited and the original remains. When String Confirmation Day arrives, ICANN will publish the updated list showing the final confirmed string for each application and revised contention sets.

The architecture was designed to let applicants react to the disclosed field without reopening the submission window. It also creates a temporary layer of optionality that headline arithmetic cannot resolve. Adding 1,600 primary applications to 1,100 replacement options would be wrong: the options are mutually exclusive alternatives inside existing applications. Treating 1,600 as the final string list would also be premature: some applications may not complete payment or administration, and many applicants may change the label attached to the application.

Replacement does not guarantee escape from contention. The rules prevent an applicant from selecting a replacement identical to another submitted original or replacement string. Yet a chosen alternative can still become part of a contention set through singular/plural analysis, string-similarity review or a successful string-confusion objection. The final list is therefore a governance checkpoint, not a prediction that each name will be delegated.

A public ledger should name the state of the count

Lu Heng’s notes offer a useful test without requiring a verdict on the merits of expanding the namespace. A coordinating institution earns trust by keeping its public record accurate and by limiting its claims to what the record actually establishes. A registry record describes the state of a process; it should not manufacture certainty that the process has not reached.

Applied here, the narrow governance obligation is count discipline. ICANN need not pretend that the submission total is already stable, nor should observers collapse options, applications, evaluated strings and future delegations into one number. Each represents a different decision state, controlled by different actors and subject to different failure points.

The applicant controls whether to pay and, where eligible, whether to switch strings. ICANN controls due diligence, invoice issuance, administrative review and publication of the authoritative lists. Evaluation panels, objection mechanisms and contention procedures will later determine which applications advance. The root-zone process comes later still. Calling all of these stages “new domains” erases the very controls the programme was built to apply.

A better public dashboard would preserve the original announcement while adding dated counters as the round moves: submitted primary applications; invoices issued; fully paid applications; administratively complete applications; applications with replacement options; replacements activated; final confirmed strings; contention sets; withdrawals; evaluation outcomes; and delegations. These categories should not be combined merely because they share one programme.

The immediate news is not that ICANN has chosen 1,600 new top-level domains. It is that more than 1,600 applicants entered a governed sequence, and most arrived with an alternative label in reserve. The next authoritative fact will be the accepted application population. The decisive naming fact will come only on String Confirmation Day.

Sources