Summary

  • The 7 October snapshot reports 1,615 applications and 481 applicants, while unique strings, variants, contention sets and processing-stage totals remain unavailable.
  • Application comments can inform defined evaluations; objections, GAC warnings and GAC advice follow different rules and confer different kinds of influence.

A count needs a unit

A public count looks definitive because it is exact. But “1,615 applications” answers only one question: how many application records ICANN’s 7 October snapshot counted. It is not the number of applicants, unique strings, successful evaluations, registry contracts or new top-level domains that will enter the root.

The dashboard makes the distinction visible. It lists 481 applicants beside 1,615 applications. Its regional table counts applicants: 198 are assigned to North America, 111 to Europe, 156 to Asia, Australia and the Pacific, seven to Africa, and nine to Latin America and the Caribbean. ICANN’s separate Reveal Day announcement reports applications by region: 864, 506, 218, 16 and 11 respectively. Comparing the two tables as if they measured the same thing would turn a distribution of applications into a false map of applicant locations—or of future users.

There is also a small but unresolved version change. On 22 September ICANN said that 1,663 applications had been submitted and 1,616 had received the payment required to proceed. The 7 October snapshot shows 1,615. The published material reviewed here does not explain the one-record difference. It is a reason to keep dates and denominators attached to every figure, not a basis for guessing that an application was withdrawn, rejected or removed.

Why records do not equal future domains

An application can include one gTLD and one or more allocatable variant strings. It may also identify a replacement string, a fallback the applicant can choose during the current 8–21 October replacement window. Before String Confirmation Day, a selected replacement can appear as a second record on the applications tab; the statistics summary still counts it as one application. An unused replacement becomes “Deactivated” after confirmation. A record, a primary string, a variant and a fallback are therefore not interchangeable units.

The live statistics page reports 1,615 active applications, but zero contracted and zero delegated. It also leaves total unique strings, total variants, applications in contention, contention sets and processing-stage counts blank. Those blanks matter more than the apparent precision of the top-line number. The round is still at publication and string selection, not at an outcome that can be counted as a future namespace.

The categories in the announcement require similar care. It lists 333 brand applications, 16 community-based applications, 15 self-identified geographic-name applications, 21 applications for internationalized domain names and 51 applications from Applicant Support Program applicants. ICANN says application types are not mutually exclusive, so the categories can overlap. “Community-based” is an application classification; it does not show that a community authorized the applicant to speak for it. A self-identified geographic label is not itself evidence of local consent.

Input is not a ballot

The next public phase begins on 17 November, when the final applied-for strings and updated contention sets are due. The Community Input and Objections Period is scheduled to run through 16 March 2027. Application comments are the broadest route for people to flag relevant information, but their effect is specific: a commenter must identify the application, string and evaluation or process; disclose affiliation and relationships; and connect the submission to established criteria. The guidebook says evaluators may consider relevant comments, and that applicants can respond. It does not make comments a vote on whether a string should exist.

An objection is a separate proceeding, decided by an expert panel under a defined ground and standing rules. A community objection, for example, requires a standing institution and well-substantiated opposition from a significant portion of the community the string targets. A GAC member early warning is a notice of concern, not an order that directly changes an application. GAC consensus advice is a distinct submission to the ICANN Board. Treating these as interchangeable would obscure who can act, what evidence each channel accepts and which body makes the decision.

Heng Lu’s Note 73 is useful here only as an editorial lens: participation can contribute evidence or warning without becoming authority to bind everyone affected. It is not evidence about this round. The same distinction applies to the application tally. It records filed intent under program rules; it does not establish public demand, community consent or a final delegation decision.

For now, the reliable description is bounded: 1,615 applications appeared in the 7 October snapshot, and the next records will revise the set of strings and expose where contention and public input matter. The useful question is not how many domains the headline promises, but which stage a record has reached, which string it concerns, and what decision mechanism remains open.

Sources