Summary

  • ICANN can count the applications submitted in its 2026 new-gTLD round before the public can see the strings, applicants or contention sets.
  • The application window closed on 12 August 2026 with more than 1,600 primary applications.

A number without a public list

The application window closed on 12 August 2026 with more than 1,600 primary applications. ICANN also said that more than 1,100 of those included applications for replacement strings. The two figures must not be added together as if they described separate populations. A replacement-string application is nested inside the primary-application process; it is an option for changing a string later, not another applicant arriving at the door.

The headline count is still provisional in another sense. ICANN said it could not confirm the final total until the applicable evaluation fees had been received. Submission therefore creates one record; fee completion determines whether an application proceeds into the next stage. A large number at the closing bell is not yet the final paid denominator.

Nor is it a list of distinct organizations. One entity may submit more than one primary application. Until ICANN publishes the public-facing records, the public cannot responsibly infer how many applicants, countries, communities, brands or generic terms sit behind the total.

Administrative Check is a gate, not an evaluation result

The 2026 Applicant Guidebook places an Administrative Check between the closing date and Reveal Day. During that interval ICANN performs administrative due diligence, verifies fee receipt, reviews the submitted set and groups identical strings into contention sets. The Guidebook estimates about eight weeks for the work, while allowing a revised timeline if volume prevents completion on schedule.

This gate matters because Reveal Day covers applications that passed the Administrative Check. It does not certify that an applicant will pass financial, technical, string, geographic-name, community or other substantive evaluations. It does not resolve objections or contention. It does not create a registry agreement, and it does not put a string in the DNS root.

That distinction protects both sides of the public argument. ICANN should not be judged as if it had already approved 1,600 new registries. Applicants should not be treated as winners—or as risks—before the relevant processes have begun.

Reveal Day discloses the field, but not its final shape

Absent extraordinary circumstances, ICANN expects Reveal Day no later than nine weeks after the application window closes. The public list should identify applications that passed the Administrative Check, the applied-for strings, relevant variant and replacement strings, public portions of the applications and contention sets formed around identical strings.

That disclosure is substantial. It lets communities, governments, competitors and technical observers see who is seeking which names and where claims collide. But it is still not the final string map. Eligible applicants then have a 14-day Replacement Period. String Confirmation Day comes later with an updated application list and updated contention sets.

Reveal Day is therefore best understood as the first public denominator: the moment a private submission inventory becomes a reviewable public field. It is neither the first count nor the last list.

Primary sources