Summary

  • ICANN received more than 1,600 primary applications in its 2026 new-gTLD round, more than 1,100 of them with replacement-string applications, but says the final application total cannot be confirmed until evaluation fees are received.
  • The payment date is not identical for everyone: ICANN must receive the full fee by 23:59 UTC on 19 August or seven days after the invoice was sent, whichever is later.

The first demand number from ICANN’s 2026 new-gTLD round is large and deliberately provisional. More than 1,600 primary applications had arrived when the 15-week submission window closed on 12 August. More than 1,100 included applications for replacement strings. Yet ICANN put a qualification beside the headline: the final total cannot be confirmed until the evaluation fee has been received.

That qualification moves the story from forms to money. For a standard application, the evaluation fee is USD 227,000. It funds the required evaluation process and later program work; conditional reviews can cost extra. Qualified participants in the Applicant Support Program receive a 75–85% reduction, while variant-string rules create other exceptions. The submission count therefore cannot be multiplied by USD 227,000 to produce a credible revenue figure or a measure of capital already committed.

The immediate gate is payment receipt. ICANN’s current rule says the full amount must arrive by the later of two dates: 23:59 UTC on 19 August, or 23:59 UTC seven days after the invoice was sent. An invoice sent on 14 August, for example, carries a 21 August deadline. The 19 August date is the baseline for the round, not a universal last moment for every applicant.

That exception exists because invoices do not appear automatically when an applicant presses submit. ICANN first performs due diligence. It then generates an invoice, sends it to the billing contact and notifies the applicant in the TLD Application Management System, or TAMS. A late invoice would otherwise consume part of the applicant’s payment window before the applicant even received the demand.

The mechanics make receipt—not merely initiation—the relevant fact. ICANN records the date on which payment arrives and updates TAMS after processing. Its fee FAQ says the application is marked Paid when the invoice has been paid in full. Applicants must also absorb bank, transaction and currency-conversion fees so that ICANN receives the required US-dollar amount. Accepted routes include wire transfer, ACH and international SWIFT; checks, cash and credit cards are excluded.

This is a control point with a narrow purpose. The Applicant Guidebook says an application that is not paid within the applicable window generally will not be processed further and will be canceled. The later-of-two-dates adjustment changes the clock for invoices issued after the application window; it does not remove the payment condition.

Payment also does not approve a string. It admits an application to the next part of a much longer process. ICANN must verify fees, conduct the Administrative Check and prepare identical strings for possible contention sets. Applicant and application evaluations, public comments, objections, contention resolution, contracting and eventual delegation remain separate stages.

The next public milestone is therefore not a root-zone change. ICANN says the administrative review is expected to take about eight weeks, subject to volume. Its 13 August announcement says that, absent extraordinary circumstances, Reveal Day should occur no later than nine weeks after the submission window closed. ICANN expects to announce the Reveal Day date and later milestones in mid-September.

Reveal Day is when the public-facing portions of applications that passed the Administrative Check are due to become visible, including the strings applied for and possible contention relationships. Until then, the more-than-1,600 figure is useful as an upper signal of filed interest, but not as a verified inventory of paid applications, distinct future TLDs or eventual delegations.

This distinction matters to registry service providers, financiers, advisers, governments and brand owners trying to estimate the round’s real operating load. A submitted form can indicate intent. A reconciled fee demonstrates that the applicant crossed a costly admission threshold. Neither proves technical readiness, commercial demand or approval.

The clean reading on 19 August is consequently modest. ICANN has recorded a busy filing window, with most applications arriving in the final days. It has not yet published the final paid field. The evidence needed next is an official count after payment reconciliation, followed by the mid-September timetable and Reveal Day—not a multiplication exercise built on a provisional headline.

Sources