Summary

  • Fifty-six support approvals lower specified financial and capability barriers; they do not equal 56 accepted gTLD applications or delegated registries.
  • The useful measure is a funnel from initiation through submission, support qualification, evaluation, contention, contracting and delegation.

ICANN closed the 2026 Applicant Support Program with a number that sounds like an outcome: 56 entities qualified for assistance. The denominator matters. Seventy-eight organizations submitted support applications, while another 99 began the process but never submitted. Of the submitted group, three were found ineligible, four withdrew and 15 were terminated.

That is a real expansion of the group allowed to carry support into the new-gTLD round. It is not the same thing as 56 new registries. Applicant Support is a gate before the main application, and ICANN’s own program page says qualification for assistance does not qualify anyone for a gTLD.

The program lowers several different costs

The support package is not a single discount. Qualified organizations can receive capacity development, access to independent pro bono providers, program resources and an Applicant Counselor. Financial support includes a 75–85 percent reduction in the main evaluation fee. A supported applicant may also receive a bid credit if its string enters contention, and reduced base registry fees if it eventually prevails, contracts and reaches delegation.

These benefits activate at different points. Counseling and technical orientation can help an organization prepare. The evaluation-fee reduction affects entry into the main round. A bid credit matters only if competing applications form a contention set. Reduced registry fees matter only after the applicant has survived evaluation and reached operation.

That sequencing prevents a common analytical mistake. It is not accurate to say that ICANN removed “the cost barrier” as though every applicant faced one price at one moment. The program reduces named costs and supplies named forms of expertise. It does not eliminate the time, governance capacity, technical responsibility, objection risk or long-term operating burden attached to running a registry.

The first drop-off happened before support evaluation

The final statistics show 99 organizations that initiated the process without submitting a support application. The public record does not say why any individual stopped. It would be unsafe to attribute the gap to documentation, awareness, deadlines, eligibility or finance without applicant-level evidence.

The gap still belongs in the measurement frame. A program designed to widen participation should be examined from the first credible expression of interest, not only from complete files that reach an evaluator. The submission boundary is distinct from the approval boundary, just as support approval is distinct from the main-round evaluation.

This distinction also protects the approved figure from being overread. Fifty-six out of 78 submitted applications describes the decision set that reached support evaluation. Fifty-six out of 177 initiated processes describes a different part of the participation funnel. Neither ratio alone proves whether outreach succeeded or which barrier was decisive.

Pro bono help is access, not institutional endorsement

ICANN’s terms place another boundary around professional assistance. Pro bono providers are independent; ICANN does not endorse or contract them. ICANN may make supported applicants aware of available services, but the relationship does not convert outside advice into an ICANN guarantee.

That matters because technical and legal support can improve an application without transferring responsibility for it. The applicant still chooses a string, supplies the main application, selects or becomes an evaluated registry service provider, answers evaluation questions and carries the consequences of its commitments.

The official success measure lies further downstream

ICANN’s 26 August announcement points to a future measure: supported applicants should account for at least 10, or 0.5 percent, of successfully delegated new gTLDs. The announcement says 56 approvals may surpass that goal. “May” is doing necessary work. At that point, ICANN had not reported 56 main-round applications, 56 successful evaluations or any new delegations from the group. The final round denominator was still waiting for Reveal Day.

The delegation metric is stricter than an approval count because it preserves the gates in between. A supported entity must still file a main-round application, pass evaluations, address public input and any objection, resolve contention if necessary, contract with ICANN, meet technical conditions and enter the root.

Count the gates, not just the recipients

The 56 approvals are best understood as a capacity decision. ICANN has identified organizations eligible for a package that changes specific costs and access to expertise. That is consequential, especially for applicants that otherwise could not reach the starting line.

The next accountability question is not whether 56 sounds high. It is how many supported organizations move through each remaining gate, where they stop, and whether the support package addresses the cost at that point. A credible inclusion record should publish a bounded funnel: initiated, submitted, support-qualified, main-round applied, evaluated, through objections and contention, contracted and delegated.

Only then can the program distinguish entry assistance from durable participation in the root.

Primary sources