top of page

Beyond the 21 IDN Applications: Universal Acceptance, AI and the Challenge of Meaningful Linguistic Inclusion

2 days ago
17 min read

What ICANN’s 2026 New gTLD Round Reveals About the Future of a Multilingual Internet

By: Alfredo Calderón-Serrano

A domain name can be technically valid and still fail the people who depend on it.

Imagine registering a domain name in your own language, only to find that a website builder rejects it, an online registration form marks it as invalid, or an email service cannot process it properly. The domain works in the Domain Name System (DNS), yet everyday applications still prevent you from using it.

This illustrates one of the most important challenges facing Internationalized Domain Names (IDNs): making multilingual names available does not automatically make them usable.

The challenge has become particularly relevant following ICANN’s October 7, 2026, announcement of applications for the next round of new generic top-level domains (gTLDs). Of the 1,615 applications reported, only 21 involved IDNs, approximately 1.3% of the total.

These preliminary figures raise questions about the future of linguistic diversity on the Internet. They also invite a broader examination of the relationship between multilingual naming, Universal Acceptance (UA), artificial intelligence (AI), and meaningful digital participation.

The Governmental Advisory Committee (GAC) sharpened these concerns at ICANN87 in Bali, Indonesia. Its October 26 communiqué warned that the limited number of IDN applications could undermine expectations for greater linguistic and geographic diversity.

But the implications extend beyond application statistics.

These concerns establish the report’s central premise: meaningful linguistic inclusion depends not only on making multilingual names available, but also on understanding who can participate and whether those names can be used reliably. The first step is to examine what the preliminary application figures do—and do not—show.

1. Understanding the Preliminary Count: What Do the 21 Applications Tell Us?

ICANN’s Reveal Day announcement provided an initial picture of participation in the 2026 round.

Indicator

Preliminary number

Total new gTLD applications

1,615

IDN applications

21

Community-based applications

16

Applications submitted by Applicant Support Program participants

51

Applications originating from Latin America and the Caribbean

11

Source: ICANN, October 7, 2026. These categories are not mutually exclusive.

The 21 IDN applications represent approximately 1.3% of the reported total. That is a modest proportion for a program intended, in part, to expand linguistic diversity in the global naming system.

However, these numbers require careful interpretation.

ICANN identified its Reveal Day statistics as preliminary and based on primary-string application data. ICANN expected to confirm final application numbers and categories after String Confirmation Day on November 17, 2026.

A separate analysis published by Stéphane Bortzmeyer on October 8 identified 27 IDN entries in a broader dataset containing original applications and replacement strings. His analysis reported 2,783 records when replacements were included and 1,614 applications when they were excluded.

This creates an important methodological distinction.

An application with a replacement string may appear in more than one record without representing two independent applications. Associated variants also require separate classification.

An application that includes a replacement string may generate multiple records without constituting separate applications. Associated variants must also be classified independently. Therefore, the 27 IDN entries identified in the independent analysis are not directly comparable to ICANN’s preliminary count of 21 applications proposing IDNs as their primary strings, as the two figures reflect different counting methods. Before drawing application-specific conclusions, researchers need to compile a verified application-by-application inventory using application identifiers, primary strings, replacements, variants, and the corresponding snapshot dates.

What the available strings suggest

The independent dataset identifies a striking concentration of IDN entries using Han characters, along with one accented Latin-script entry, .québec.

Several strings relate to commercial activities, digital identity, or familiar technology concepts.

General category

Examples of visible strings

Artificial intelligence and automation

人工智能, 数字人, 智能体, 机器人

Online presence and addressing

中文网, 在线, 地址, 官网, 网络

Commercial identity and verification

名片, 品牌, 商标, 防伪

Commerce and services

购物, 酒店, 钱包, 餐厅

Commercial or product-associated terms

抖音, 海信, 海尔, 海尔兄弟, 瑞幸, 瑞幸咖啡

Context-dependent terms

番茄, 红果

Japanese corporate terminology

株式会社

Accented Latin-script name

québec

These groupings reflect only the strings’ wording, not verified application categories, ownership, registration policies, or intended communities.

Han characters do not necessarily indicate that a name targets Chinese-speaking users. The Japanese term 株式会社 shows why scripts and languages must be assessed separately.

Even so, the visible concentration warrants attention.

Although ICANN’s 2026 program permits IDN applications in 27 scripts spanning hundreds of languages, the preliminary portfolio does not reflect comparable diversity.

What the figures cannot establish

The absence of certain languages does not necessarily indicate limited community interest. Participation may depend on:

  • financial barriers and market considerations;

  • technical demands and institutional capacity; and

  • awareness of the application process.

Determining the relative influence of these factors requires evidence beyond the submitted applications.

Figure 1. The IDN gap in ICANN’s 2026 new gTLD round. Preliminary figures reveal a significant disparity between overall applications and applications for internationalized domain names, raising questions about linguistic diversity, equitable participation, and applicant support. Sources: ICANN (2026); GAC Bali Communiqué (2026).

2. Why the Bali GAC Communiqué Matters

The preliminary figures establish the scale of the gap; the GAC’s October 26, 2026, Bali Communiqué explains why that gap matters from a public-interest perspective.

In its Human Rights and International Law Working Group report, the GAC expressed concern that the preliminary IDN figures might fall short of the linguistic and geographic diversity anticipated by the ICANN community.

The significance of this concern lies in the distinction between expanding the domain-name market and expanding meaningful participation in the Internet.

Both objectives can coexist, but they are not interchangeable.

A commercially successful new domain extension may contribute to the DNS ecosystem without necessarily expanding opportunities for underserved language communities. Conversely, a relatively small community-oriented initiative may have substantial cultural, educational, or social significance even if its registration volume remains modest.

The central question is therefore:

Does the 2026 round create meaningful opportunities for different language communities, or does it primarily expand options for applicants already equipped to participate?

The communiqué does not conclude that any of the 21 applications is deficient or illegitimate. Nor does it recommend their rejection. Instead, it points toward a broader assessment of the conditions that enable or discourage participation.

Applicant support and the projects that never reached submission

One of the GAC’s concerns involves the Applicant Support Program (ASP).

The communiqué calls for a lessons-learned evaluation of the differences between applications initiated, approved for support, and ultimately submitted. It encourages structured exit surveys and interviews, with initial findings ideally available before ICANN88.

For IDN policy, this raises questions that cannot be answered by examining the 21 submitted applications alone.

Researchers should investigate whether prospective multilingual applicants considered applying but ultimately withdrew, never completed the process, or decided not to proceed.

Potential barriers include application costs, access to legal and technical expertise, organizational capacity, financial uncertainty, and the availability of appropriate support.

These possibilities should be studied rather than assumed.

The GAC also encourages continued guidance and practical assistance during later stages of the application process, including legal costs associated with objections and expenses arising from string contention.

This is particularly important for applicants with limited resources. Participation does not end when an application is submitted. Applicants must also be able to navigate the subsequent evaluation and contracting process.

A meaningful inclusion strategy must therefore consider both entry into the process and the ability to remain in it.

3. Universal Acceptance: The Difference Between a Valid Name and a Usable Identity

The Bali discussion shifts attention from who entered the application process to whether the resulting multilingual names can be used in practice. Universal Acceptance provides the framework for that next question.

UA requires applications and services to accept, validate, store, process, and display valid domain names and email addresses correctly.

Each function is necessary. Failure at any stage can disrupt an otherwise legitimate activity.

UA function

Potential problem

Consequence for the user

Acceptance

A form or API permits only basic ASCII characters.

The user cannot enter a domain or email address in its normal written form.

Validation

Software uses outdated TLD lists or inappropriate character restrictions.

A valid name is incorrectly rejected.

Storage

An application mishandles Unicode or stores inconsistent representations.

Information may be corrupted or become difficult to retrieve.

Processing

Software converts or compares domain representations incorrectly.

Links, account lookups, and integrations may fail.

Display

An interface cannot render the name correctly or unnecessarily displays its encoded form.

Users may have difficulty recognizing or consistently using their digital identity.

These are established categories of potential UA failure, not measured findings for the preliminary set of 21 IDN applications.

Why DNS resolution alone is insufficient

An IDN has two complementary representations:

  • U-label: the Unicode form that people read and use.

  • A-label: the ASCII-compatible form used in DNS operations.

Both serve valid technical purposes, but correct DNS resolution does not ensure compatibility elsewhere. A domain may resolve through its A-label while a registration form rejects its U-label, or a customer-management system stores the name incorrectly and later prevents account access.

Using the encoded A-label may address some compatibility issues, but applications must still handle the user-facing U-label correctly. DNS interoperability therefore does not guarantee interoperability across the broader application ecosystem.

Email compatibility requires separate testing

A working website under an IDN does not guarantee that email addresses using the same domain will function across services. Two scenarios require distinct evaluation:

  • ASCII mailbox with an internationalized domain: The domain still requires correct IDN handling.

  • Internationalized mailbox and domain: Non-ASCII characters in the mailbox name introduce additional Email Address Internationalization (EAI) requirements. Converting the domain to its A-label does not convert the mailbox name to ASCII.

A complete assessment must therefore distinguish among website compatibility, email-domain compatibility, and support for fully internationalized email addresses. Reducing these capabilities to a single yes-or-no measure would obscure important technical differences.

4. What Universal Acceptance Means for Applicants

The preceding technical distinctions become operational and commercial concerns for applicants. Registry approval confirms neither ecosystem readiness nor seamless use, and even technically sound registries may face failures in third-party services beyond their control, including:

  • hosting platforms and website builders;

  • identity systems, government portals, and email providers; and

  • customer databases and commercial applications.

These incompatibilities can affect registration decisions, support needs, active use, and renewals. A registrant may purchase a valid multilingual domain only to have an essential platform reject it—and may blame the domain provider even when a separate software service caused the failure.

These are plausible commercial risks, not demonstrated outcomes for the preliminary set of 21 IDN applications.

UA priorities vary by registry model

The importance and form of these risks depend on how a registry is designed and whom it serves.

Registry model

Principal UA concern

Open registration

Compatibility across a broad range of independent services

Corporate or brand-controlled namespace

Readiness of internal systems, suppliers, and customer-facing platforms

Community-oriented namespace

Support in essential educational, governmental, and communications services

Identity or authentication namespace

Consistent handling and recognizable presentation of digital identities

AI-related namespace

Compatibility with AI development tools, website builders, and deployed applications

Assessment focus

An open registry serving many independent registrants generally faces greater deployment complexity than a brand-controlled namespace operating a limited set of sites. However, neither model is automatically UA-ready.

A sound evaluation should examine each applicant’s operating model, intended users, technical dependencies, and implementation arrangements.

5. Artificial Intelligence and Linguistic Inclusion

Those ecosystem dependencies are increasingly shaped by artificial intelligence. AI assistants can lower barriers by helping users build websites, generate software, manage information, and navigate digital systems, but they can also reproduce existing limitations in the handling of multilingual Internet identifiers.

Evidence and limits

ICANN’s 2026 Annual Strategy Review recorded stakeholder observations that some AI website-building tools do not properly accept IDNs and called for further investigation into AI’s effects on Universal Acceptance.

These observations identify a legitimate concern, but they do not establish ecosystem-wide failure rates or show that AI caused the low number of IDN applications.

How AI can hinder or improve compatibility

  • Risk: An AI-assisted website builder may generate a form with outdated validation rules that accepts conventional ASCII domains but rejects valid internationalized names.

  • Risk: A coding assistant may reproduce the same flaw if developers do not review and test its output against UA requirements.

  • Opportunity: AI can help identify incompatibilities, generate multilingual test cases, and support implementation of existing standards.

The underlying requirement is unchanged: software that rejects a valid multilingual domain remains incompatible, whether written by a human or generated by AI.

AI’s contribution will therefore depend on how these tools are designed, evaluated, tested, and used.

Linguistic inclusion requires more than compatible domain names

Identifier compatibility is only one dimension of linguistic inclusion: current AI systems also provide uneven support across the world’s languages.

Evidence of unequal language support

UNESCO’s Coalition for Linguistic Diversity in Artificial Intelligence highlights the limited representation of many languages in training resources, evaluation benchmarks, and deployed technologies. The United Nations Development Programme (UNDP) similarly notes that models often perform less effectively in low-resource languages because relevant digital content and training data are scarce.

Two distinct inclusion challenges

  • Identifier compatibility: Can a multilingual domain function across the Internet’s technical and application layers?

  • Language capability: Can AI systems understand, generate, and process information effectively in the language associated with that domain?

These capabilities are independent. A service may support an IDN yet produce poor AI-generated content in its intended language. Conversely, an AI system may communicate fluently in that language while its website builder rejects the corresponding internationalized domain.

A genuinely multilingual Internet requires coordinated progress in naming infrastructure, software compatibility, language technologies, and community capacity.

Four pathways through which AI may affect IDN adoption

Because meaningful inclusion depends on both identifier compatibility and language capability, AI’s influence must be examined across the full path from development to adoption. Four pathways illustrate where these opportunities and risks may arise.

Area

Potential opportunity

Potential risk

AI-assisted programming

Faster development and testing of multilingual applications

Generated code may reproduce incorrect validation practices

AI website builders

Lower technical barriers for local-language publishers and businesses

Unsupported IDNs may prevent users from establishing their preferred online identity

AI-powered information services

More accessible discovery and use of multilingual content

Weak language performance may reduce reliability and usefulness

Community language technologies

Better translation, educational resources, and language preservation tools

Limited datasets and insufficient community participation may reinforce existing inequalities

Research implications

These pathways provide a framework for further study; their effects on IDN registration, adoption, and renewal have not yet been measured.

The presence of AI-related strings such as 人工智能, 智能体, 数字人, and 机器人 makes this relationship especially relevant. Researchers should examine whether software tools and platforms associated with AI reliably support these multilingual namespaces.

That analysis should assess two issues separately: the technical handling of domain identifiers and the AI system’s ability to understand and use the relevant language.

Figure 2. From technical availability to meaningful usability. A valid internationalized domain name may still encounter barriers in registration systems, email services, website builders, and AI-generated applications. Universal Acceptance requires consistent handling of multilingual identifiers throughout the digital ecosystem. Sources: ICANN Universal Acceptance guidance; UASG technical documentation.

6. Cultural Context and Public-Interest Safeguards

Technical compatibility and language capability are necessary, but they do not resolve questions of meaning, trust, or public authority. The GAC’s Bali Communiqué therefore emphasizes that Safeguard Assessments should also reflect the relevant linguistic and cultural context.

Assess meaning in context

A literal English translation may not capture the expectations a term carries within its intended community. For example, wording associated with an official institution may imply different levels of authority depending on local administrative practices and social conventions.

A responsible review should examine:

  • the expression’s meaning in its linguistic and cultural context;

  • the applicant’s proposed use and registration policies;

  • claims or signals of authority, trust, accreditation, or verification; and

  • evidence from application materials and relevant cultural expertise.

Safeguards and enforceable commitments

The communiqué also highlights consumer protection, DNS abuse, and applications connected to government functions, public services, and regulated sectors. A Safeguard Assessment does not automatically prevent an application from proceeding, but it may lead to Public Interest Commitments incorporated into an enforceable registry agreement.

Do not infer formal status from the string alone

An IDN should not be classified as a Community Application simply because it uses a culturally meaningful expression. Researchers must distinguish among:

  • the label’s linguistic or cultural association;

  • the application’s formal category;

  • the applicant’s relationship with the relevant community; and

  • the supporting documentation required by the program.

Keeping these distinctions clear is essential to a credible public-interest review.

7. A Three-Stage Framework for Evaluating the Preliminary Set of 21 IDN Applications

The preceding sections identify the technical, linguistic, and public-interest questions at stake. A defensible evaluation can bring them together in three stages: compile a verified application-by-application inventory, assess likely dependencies before delegation, and test complete user journeys once names become operational.

The independent dataset is a useful starting point, but it cannot replace a verified application-by-application inventory.

Stage 1: Compile the verified application inventory

Document each application using consistent fields so that primary strings, replacements, variants, and formal categories are not conflated.

Field

Purpose

Application ID

Identifies the individual application

Original and selected primary strings

Tracks the effect of the replacement process

U-label and A-label

Records the exact technical identifier

Associated variants

Prevents variants from being mistaken for independent applications

Applicant and jurisdiction

Establishes the legal entity and its location

Script and declared language

Avoids confusing writing systems with linguistic communities

Application category

Distinguishes formal designations from assumptions about intended use

Registration policy and target users

Clarifies whom the namespace is intended to serve

Applicant Support Program participation

Helps identify the role of financial and technical assistance

Status and snapshot date

Preserves the context of preliminary and subsequent application records

Only after this reconciliation should the study report definitive distributions by script, language, applicant location, or intended registry model.

Stage 2: Assess dependencies before delegation

Pre-delegation review can identify many compatibility risks without requiring the proposed TLD to be operational.

Researchers should identify the services most important to intended registrants and test representative valid IDNs with similar script characteristics across:

  • website builders and registration forms;

  • identity and account-management platforms;

  • email-related software; and

  • other applications central to the intended user community.

The review should also examine applicants’ arrangements for support, escalation, and remediation.

An undelegated TLD should not be expected to pass live DNS-resolution or email-delivery tests; those tests become meaningful only after the required infrastructure is operational.

Stage 3: Test complete user journeys after launch

Once operational names are available, testing should follow realistic user journeys rather than isolated technical functions.

A representative test should include the following steps:

  1. Entering the domain in its normal Unicode representation.

  2. Creating an account using the intended domain or email identity.

  3. Storing and retrieving account information without altering the identifier.

  4. Generating and following links.

  5. Completing email verification and account recovery, where applicable.

  6. Confirming appropriate handling of U-label and A-label representations.

  7. Repeating the process across relevant AI-assisted and conventional software platforms.

Document each failure in enough detail to reproduce it, identify the responsible component, and distinguish registry defects from failures in third-party services.

For example, a rejection by a commercial website builder or government portal should not be attributed to the registry unless the evidence supports that conclusion.

This discipline is essential to technical accuracy and fair policy analysis.

8. Measuring Meaningful Use, Not Just Technical Availability

The three-stage framework explains how to evaluate applications; the next step is to define what successful outcomes should look like. Traditional measures such as application counts, delegation totals, and registration volumes capture expansion of the DNS, but not necessarily meaningful use.

They do not, by themselves, establish that a namespace is meeting the needs of its intended users.

A more complete assessment should examine several connected dimensions.

Dimension

Central question

Availability

Can the applicant establish and operate the proposed multilingual namespace?

Accessibility and usability

Can people use names under that namespace in the services they depend on?

Public-sector readiness

Do essential government systems accept valid internationalized domains and email addresses?

Community participation

Are intended language communities meaningfully involved and served?

Sustainable adoption

Can registrants maintain and use these identities without recurring barriers?

Consumer protection

Are the relevant risks understood and addressed through appropriate safeguards?

These dimensions would provide a more informative picture than application statistics alone.

They would also help distinguish obstacles caused by technical incompatibility from those associated with cost, market demand, institutional capacity, or awareness.

For example, low registration activity could reflect limited demand, inadequate promotion, difficulty connecting domains to essential services, or a combination of factors.

Without comparative evidence, attributing that outcome to any single explanation would be premature.

9. A Research Agenda for ICANN and the Broader Community

These broader measures point directly to a research agenda. The Bali discussions provide an opportunity to organize a systematic examination of linguistic inclusion in the 2026 round.

Five complementary areas deserve priority.

First, compile the verified application inventory. Establish a verified inventory of the preliminary set of 21 primary-string IDN applications, preserving the distinctions between primary strings, replacement records, variants, and variant-only applications.

Second, investigate participation barriers. Examine the experiences of submitted, withdrawn, and non-proceeding applicants, particularly those considering multilingual or underserved-community projects. The ASP evaluation requested by the GAC could provide valuable evidence.

Third, measure Universal Acceptance readiness. Conduct reproducible testing across browsers, website builders, account-registration systems, email services, public-sector platforms, and AI-assisted applications.

Fourth, evaluate community benefit and adoption. Combine technical assessments with user interviews and longitudinal measures of active use, renewals, costs, institutional support, and trust.

Fifth, review public-interest protections. Examine application narratives, registration requirements, cultural and linguistic implications, consumer safeguards, and enforceable commitments.

These are proposed research priorities derived from the concerns raised in Bali. They are not requirements formally prescribed by the GAC.

A practical role for governments and educational institutions

These proposed priorities require participation beyond ICANN’s research and policy processes. The communiqué therefore encourages GAC members to promote Universal Acceptance within national digital strategies and public-sector services.

This offers a practical opportunity for collaboration.

Governments can examine whether their digital portals accept valid multilingual domains and email addresses. Universities can incorporate UA requirements into software-development curricula and applied research. Technology companies can strengthen compatibility testing, while language communities can contribute cultural expertise and real-world user perspectives.

AI developers and providers of coding tools should also be part of these conversations.

Their products increasingly shape the software used by businesses, educational institutions, and public agencies. Ensuring that generated applications respect established identifier standards is therefore a practical contribution to digital inclusion.

At the same time, the institutional boundaries must remain clear.

ICANN’s role is not to become a general regulator of artificial intelligence. Its responsibility concerns the stable, secure, and interoperable operation of the Internet’s unique identifier systems.

Within that mission, however, studying how AI affects the handling and usability of those identifiers is both relevant and justified.

10. What Bali Ultimately Tells Us

Taken together, the evidence, evaluation framework, and research priorities lead to a broader lesson from ICANN87: linguistic inclusion cannot be reduced to the number of domain extensions available in different scripts.

The preliminary count of 21 IDN applications raises legitimate questions about the extent of participation in the 2026 round. The GAC’s concern deserves careful investigation, particularly in relation to applicant support, regional representation, Universal Acceptance, and community participation.

Yet the small number does not prove that the submitted applications are deficient, nor does it establish why other language communities did not participate.

The distinction matters.

A credible policy response should begin with verified application data and proceed toward evidence about the barriers facing prospective applicants and the real experiences of multilingual Internet users.

That response should not focus exclusively on the new gTLD program. The Bali Communiqué also recognizes complementary approaches to linguistic inclusion, including Indonesia’s local-language and non-Latin-script initiatives under its national country-code top-level domain. The new gTLD program is therefore one important avenue for inclusion, but not the only one.

These complementary national initiatives broaden the policy landscape, while artificial intelligence expands the range of technologies that can either support or obstruct them.

As AI-generated software and AI-mediated services become more common, the ability to use multilingual identifiers consistently will depend increasingly on decisions made outside the traditional DNS industry.

A valid internationalized domain must work not only in DNS infrastructure, but also in the tools people use to establish businesses, access public services, communicate, learn, and participate online.

Universal Acceptance therefore connects the report’s central concerns: participation, technical usability, linguistic capability, and public-interest safeguards. This synthesis provides the basis for judging success in ICANN’s 2026 new gTLD round.

Conclusion: From Multilingual Names to Meaningful Participation

Against that standard, expanding choice is necessary—but it is only one measure of success.

More domain extensions can widen choice; broader regional and linguistic participation can make the naming system more representative; and internationalized identifiers can give communities a digital presence in their own scripts.

None of these gains, however, is sufficient on its own.

The Internet becomes meaningfully more inclusive only when people can use their preferred digital identities without avoidable technical, linguistic, or institutional barriers.

Achieving that goal requires reliable naming infrastructure, compatible software, culturally informed safeguards, sustained community capacity, and cooperation across the wider technology ecosystem.

Artificial intelligence may advance this effort or create new obstacles. Its effects should be judged through evidence, practical testing, and accountability—not assumptions about either its promise or its risks.

The central lesson from Bali, then, is not simply that the preliminary count of 21 IDN applications warrants concern.

Multilingual naming policies should be evaluated not simply by the introduction of new identifiers, but by how effectively those identifiers serve users, function reliably, and create lasting opportunities for meaningful participation.

More multilingual domain names are an essential beginning.

The true measure of a multilingual Internet is not how many names it offers, but how fully and reliably people can use them to participate.

References and Supporting Sources

  1. Governmental Advisory Committee. (2026, October 26). ICANN87 Bali Communiqué. ICANN. https://gac.icann.org/advice/communiques/public/ICANN87%20Bali%20Communique.pdf

  2. Internet Corporation for Assigned Names and Numbers. (2026, October 7). ICANN reveals 2026 round applications for new generic top-level domains. https://www.icann.org/en/announcements/details/icann-reveals-2026-round-applications-for-new-generic-top-level-domains-07-10-2026-en

  3. Bortzmeyer, S. (2026, October 8). La liste des candidatures pour des TLD. https://www.bortzmeyer.org/candidatures-tlds.html

  4. Internet Corporation for Assigned Names and Numbers. (2026). 2026 annual strategy review report. https://www.icann.org/en/system/files/files/annual-strategy-review-report-2026-31jul26-en.pdf

  5. Internet Corporation for Assigned Names and Numbers. (2026). IDN implementation and UA adoption report 2026. https://www.icann.org/en/system/files/files/idn-implementation-ua-adoption-report-2026-01sep26-en.pdf

  6. Internet Corporation for Assigned Names and Numbers. (2026, September 22). New ICANN report highlights global progress on IDNs and Universal Acceptance. https://www.icann.org/en/announcements/details/new-icann-report-highlights-global-progress-on-idns-and-universal-acceptance-22-09-2026-en

  7. Internet Corporation for Assigned Names and Numbers. (2016). Universal Acceptance quick guide. https://www.icann.org/en/system/files/files/ua-quick-guide-02mar16-en.pdf

  8. Universal Acceptance Steering Group. (2018). Universal Acceptance: A technical perspective. https://uasg.tech/wp-content/uploads/2018/02/UASG019A-Universal-Acceptance-A-Technical-Perspective.pdf

  9. Universal Acceptance Steering Group. (2018). Email Address Internationalization: A technical perspective. https://uasg.tech/wp-content/uploads/2018/02/UASG019B-Email-Address-Internationalization-A-technical-perspective.pdf

  10. Internet Corporation for Assigned Names and Numbers. (2026). Guidelines for advancing Universal Acceptance adoption. https://www.icann.org/en/system/files/files/guidelines-advancing-ua-adoption-20aug26-en.pdf

  11. Internet Corporation for Assigned Names and Numbers. (n.d.). Universal Acceptance readiness evaluations. https://www.icann.org/ua-evaluations-en

  12. Internet Corporation for Assigned Names and Numbers. (n.d.). New gTLD Program: Applications. https://newgtldprogram-aps.icann.org/applications

  13. UNESCO. (n.d.). Coalition for linguistic diversity in artificial intelligence. https://www.unesco.org/ethics-ai/en/coalition-linguistic-diversity-artificial-intelligence

  14. UNESCO. (n.d.). Global roadmap for multilingualism in the digital era. https://www.unesco.org/en/global-roadmap-multilingualism

  15. United Nations Development Programme. (n.d.). Building safer AI for all languages: A collective pathway to inclusive human development. https://www.undp.org/digital/blog/building-safer-ai-all-languages-collective-pathway-inclusive-human-development

  16. Internet Corporation for Assigned Names and Numbers. (n.d.). In which scripts can IDN gTLDs be applied for? https://newgtldprogram.icann.org/en/application-rounds/round2/2026-round-general/application-types/faqs/idn-variant-strings/in-which-scripts-can-idn-gtlds-be-applied-for

Recent Posts

See All
bottom of page