Summary

  • ICANN’s 151 delegated IDN top-level domains, covering 37 languages and 23 scripts, and roughly 4.3 million second-level IDN registrations measure namespace availability and registered inventory.
  • Universal Acceptance is a different result: a valid domain or internationalized email address must survive acceptance, validation, storage, processing, display and exchange across the user’s actual path.

The most revealing number in ICANN’s IDN Implementation and UA Adoption Report 2026 is not 4.3 million. It is 20.6 percent.

The larger figure counts internationalized domain names registered at the second level worldwide. The smaller figure is the share of 923 automatically accessible websites in ICANN’s 2026 test that accepted internationalized email addresses. They do not contradict each other. They belong to different layers.

A registration says that a label was admitted under a registry’s rules and entered into a namespace. It does not say that a retailer’s account form will accept the corresponding address, that an identity provider will normalize it correctly, that a database will preserve it, that a password-reset service will send to it, or that a downstream mail filter will deliver the message. The distance between those statements is the Universal Acceptance problem.

Four inventories, none of them a completed journey

ICANN reports 151 delegated IDN TLDs as of June 2026: 61 country-code TLDs and 90 generic TLDs. Together they represent 37 languages and 23 scripts. It also cites about 4.3 million second-level IDN registrations worldwide, roughly 71 percent under a ccTLD or IDN ccTLD.

Those are consequential facts. Delegation creates a place in the root. Label Generation Rules and registry tables define which labels may be valid. Registration places a particular label in that system. DNS resolution can then make the name reachable.

None of the four proves that an application accepts the identifier as input. A DNS answer cannot certify an account form. A registry row cannot attest to a payment gateway. A valid label cannot prove that a customer-support tool renders right-to-left text correctly. Supply of identifiers is necessary for multilingual use, but it is not evidence of completed demand.

The report itself preserves that distinction. Its executive summary says broader use depends on applications, devices and systems correctly accepting, validating, storing, processing and displaying valid names and addresses. It says progress continues, but gaps remain.

The report contains better denominators than the headline

The website survey tested a bounded population. Automation could access 923 global and country-specific sites; sites requiring human interaction such as CAPTCHA could be absent. Within that reachable set, 20.6 percent accepted internationalized email addresses. The result is useful, but it is an input-acceptance observation. It does not establish successful registration, login, recovery, notification, reply or purchase.

The mail-server series is bounded differently. ICANN tested MX servers associated with second-level domains in gTLD zone files and reports the share supporting Email Address Internationalization rising from about 20 percent in 2022 to 29 percent in 2026. That measures a mail-infrastructure capability among tested servers. It cannot see every form, mailbox policy, relay, spam system, client or recovery vendor around them.

Even apparently stronger organizational figures need labels. Twenty-nine of 30 evaluated registry service provider applicants had attested that they were UA-ready by 8 July 2026; the report also says UA readiness was not a requirement. An attestation is evidence of a claim by the applicant. It is not an independent journey test.

A decision-grade chain needs separate receipts

Operators should record at least nine transitions: the TLD is delegated; the label is valid; the name is registered; DNS resolves; the application accepts the value; validation and normalization are correct; storage and retrieval preserve it; identity and email workflows complete; the user finishes the intended task.

Each transition needs a timestamp, test corpus, system and dependency versions, expected result, observed result and failure owner. A single “UA-ready” field erases the point at which responsibility changes. A registrar may control registration. A SaaS vendor may control account validation. An identity provider may control recovery. A mail host and several filters may control delivery. The user experiences one journey; the evidence belongs to several operators.

ICANN’s 33 UA Day events in 2026, held across 30 countries and territories in 15 languages, are valuable activity records. Seventeen focused on adoption or demonstration. They should remain what they are: evidence that capacity was built and bounded work occurred. They are not a denominator for the world’s applications, and they do not convert 4.3 million registrations into 4.3 million completed user journeys.

The report’s conclusion is appropriately narrower than the celebratory headline. Technical and policy foundations have advanced. The remaining challenge is to make names and addresses work consistently across everyday systems. Registration counts the identifiers that could be used. Universal Acceptance measures whether people can actually use them.

Sources