Most of the internet's first users wrote in English, so the Domain Name System was built for them: letters A–Z, digits 0–9, and a hyphen. That worked fine in 1985. It works less well today, when most internet users don't write in Latin script at all. A shopkeeper in Cairo, a student in Chengdu, or a startup founder in Moscow shouldn't have to transliterate their name into English to own a piece of the web.
Internationalized Domain Names — IDNs — fix that. They let you register and use domain names in Chinese characters, Arabic script, Cyrillic, Devanagari, Hangul, accented Latin letters, and dozens of other scripts. Behind the scenes, nothing about DNS changed: every IDN is still stored as plain ASCII. The trick is an encoding called Punycode, plus rules that decide which characters are allowed and how browsers should display them.
What Is an Internationalized Domain Name?
An IDN is any domain name that contains at least one label written in non-ASCII characters. münchen.de, café.com, 例子.测试, and президент.рф are all IDNs. A domain written entirely in plain ASCII — nomlen.com, for example — is not an IDN, even if the website's content is in another language.
Every IDN has two forms, and the distinction matters:
- The U-label (Unicode label): the human-readable form — münchen.de. This is what you type and what your browser shows you.
- The A-label (ASCII label): the encoded form DNS actually stores and looks up — xn--mnchen-3ya.de. Every A-label begins with the prefix
xn--, which tells software "this is a Punycode-encoded label, decode it for display."
DNS itself never sees a single non-ASCII byte. Your browser converts the Unicode form to the ASCII form before any lookup happens, and converts it back for display. That is the whole point of the IDNA design (Internationalized Domain Names in Applications): the infrastructure stays untouched, and only the applications at the edges — browsers, registrars, mail clients — need to understand Unicode.
Punycode: The Trick That Makes It Work
Punycode, defined in RFC 3492 (2003), squeezes any Unicode label into the letters, digits, and hyphens DNS allows. It is deterministic and reversible: every valid Unicode label maps to exactly one Punycode string, and every Punycode string decodes to exactly one Unicode label. Here are real conversions — you can reproduce them with any Punycode converter:
What you type (U-label) | What DNS stores (A-label) | Script |
|---|---|---|
münchen.de | xn--mnchen-3ya.de | Latin (German) |
bücher.de | xn--bcher-kva.de | Latin (German) |
café.com | xn--caf-dma.com | Latin (French) |
例子.测试 | xn--fsqu00a.xn--0zwm56d | Chinese |
президент.рф | xn--d1abbgf6aiiy.xn--p1ai | Cyrillic (Russian) |
Two practical consequences follow. First, the 63-character limit on a DNS label applies to the encoded form, so a long non-ASCII name can hit the limit sooner than its Unicode form suggests. Second, the xn-- form is what appears in WHOIS records, DNS tools, and SSL certificates — so if you ever need to look up or troubleshoot an IDN, search for its Punycode form. You can check ownership of either form with a WHOIS lookup; most lookup tools accept Unicode input and convert it automatically.
The Standards Behind IDNs
IDNs are governed by a small stack of IETF standards, and knowing which one applies explains most of the quirks you'll run into. IDNA2003 (RFCs 3490–3492, 2003) was the original framework, built around a preparation step called Nameprep that normalized Unicode input before encoding. IDNA2008 (RFCs 5890–5895, 2010) is the current standard: it defines categories of what is permitted and what is not, and disallowed many symbols IDNA2003 had permitted. Some characters changed status between the two — the German ß (eszett) is the famous example — which is why older and newer software can disagree about the same name. UTS #46 is the compatibility layer most browsers actually implement, accepting names valid under either standard. UTS #39 covers the security side: rules for detecting confusable characters and mixed-script labels.
On top of the IETF standards, ICANN publishes IDN Guidelines that registries must follow, and each registry maintains its own language table: the exact list of characters it permits for a given language. A character allowed in .de may not be allowed in .com, and a registry can refuse a name that mixes scripts even if the standard would permit it.
A Short History: From 1987 Proposal to Global Rollout
IDNs took more than two decades to go from idea to infrastructure. Martin Dürst proposed them in December 1987; the first implementation followed in 1990. On 10 November 2000, Verisign — operator of the .com and .net registries — opened its multilingual testbed, which held over 700,000 registrations in Chinese, Japanese, and Korean within two months. The IETF published IDNA2003 in 2003, ICANN approved migrating the testbed registrations to the standard on 18 February 2004, and IDNA2008 replaced IDNA2003 in 2010 — the same year the first fully non-Latin top-level domains went live. The EAI email standards (RFCs 6530–6533) followed in February 2012, and Gmail began recognizing non-Latin email addresses in August 2014.
The pattern is worth noting: the technical problem was solved in the early 2000s, but adoption — by browsers, email providers, and everyday software — has taken another fifteen years and is still incomplete.
The First Non-Latin Top-Level Domains
Until 2010, every top-level domain in the world was ASCII. On 16 November 2009, ICANN opened its Fast Track process for countries to apply for IDN country-code TLDs in their own scripts. The first four passed evaluation in January 2010, and on 5 May 2010 the first three went live — all in Arabic: Egypt (.مصر), Saudi Arabia (.السعودية), and the United Arab Emirates (.امارات). Russia's Cyrillic .рф launched on 13 May 2010, and five Chinese-character TLDs were approved by the ICANN board on 25 June 2010.
As of August 2018, 59 IDN ccTLDs had been approved and at least 47 were in use. The largest were .рф with over 900,000 domains, .台灣 with around 500,000, and .中国 with over 200,000. India joined the list when its Devanagari .भारत ("Bharat") was approved on 25 January 2011, alongside versions in Bengali, Gujarati, Punjabi, Tamil, Telugu, and Urdu. If you're choosing between a country-code and a generic extension, our ccTLD vs gTLD guide explains the trade-offs that apply to IDN versions too.
IDN ccTLD | Country / territory | Script | A-label (DNS form) |
|---|---|---|---|
.рф | Russia | Cyrillic | xn--p1ai |
.中国 | China | Chinese (simplified) | xn--fiqs8s |
.台灣 | Taiwan | Chinese (traditional) | xn--kpry57d |
.香港 | Hong Kong | Chinese | xn--j6w193g |
.مصر | Egypt | Arabic | xn--wgbh1c |
.السعودية | Saudi Arabia | Arabic | xn--mgberp4a5d4ar |
.امارات | United Arab Emirates | Arabic | xn--mgbaam7a8h |
.भारत | India | Devanagari | xn--h2brj9c |
How to Register an IDN
You don't need an IDN top-level domain to use an IDN. Most of the big generic TLDs — .com, .net, .org, .info, and many country codes including .de, .eu, and .in — accept non-ASCII characters at the second level. Registering one works like this:
- Check whether the TLD allows IDNs — and your script. Support varies by registry and by language. The registry's IDN language table is the authority; a good registrar shows it before you pay.
- Pick one script and stick to it. Registries generally forbid mixing scripts inside a single label, and browsers will display mixed-script names as raw Punycode anyway.
- Search in Unicode, not Punycode. Type the name as your audience will type it. A capable registrar converts it automatically — Namecheap converts IDN registrations to Punycode on its own and validates names against IDNA2008, and Porkbun lets you pick the IDN language for the TLD before checking availability. Check a name in its native script on Nomlen's all-TLD search or the full TLD list.
- Watch the price. IDNs usually cost the same as the ASCII equivalent in the same TLD — there is no IDN surcharge at most registrars — but renewal prices follow the TLD, not the script.
- Register the ASCII variant too. If your brand works in both forms — münchen.de and muenchen.de — owning both stops someone else from squatting the transliteration.
- Test before you announce it. Load the site in Chrome, Firefox, and Safari, on desktop and mobile. Send a test email to and from the address. Paste the URL into WhatsApp, X, and LinkedIn and see what the link preview shows.
The Homoglyph Problem: When "apple.com" Isn't apple.com
IDNs have one serious security flaw, and it comes from Unicode itself: some characters in different scripts look identical. Cyrillic а (U+0430) renders exactly like Latin a (U+0061) in virtually every font. An attacker who registers a domain with lookalike characters gets a real DNS record, a real TLS certificate, and a domain that reads as the genuine brand in the address bar.
The canonical demonstration came in April 2017, when researcher Xudong Zheng registered xn--80ak6aa92e.com — "apple.com" written entirely in Cyrillic — and showed Chrome (up to version 57) and Firefox (up to version 53) displaying it as apple.com, complete with a valid Let's Encrypt certificate. Chrome fixed that specific case in version 58, but the underlying problem is permanent: the characters are different code points that happen to look the same.
Browsers defend you with mixed-script detection (a label mixing Latin and Cyrillic is shown as Punycode), whole-script confusable checks, and locale awareness. The defenses are heuristic, not airtight: a 2021 USENIX study of 1,855 real-world homograph IDNs found Chrome displayed Punycode for 64.1% of them — but Safari for only 9.7% and Firefox for only 6.1%. And in October 2026, researchers at Have I Been Squatted reported new edge cases that bypass Chrome's checks, including a lookalike of apple.com that rendered in Unicode in Chrome 154 on macOS. The practical advice hasn't changed since 2017: on any login or payment page, check for the xn-- prefix, and treat a domain that looks right but feels slightly off as hostile until proven otherwise.
For domain owners, the defensive move is the same as for any brand risk: register the obvious lookalike variants of your own name — including the Cyrillic and Greek lookalikes of a Latin brand — so nobody else can. Our brand-protection guide covers which variants are actually worth the money.
IDNs and Email — and the Universal Acceptance Gap
A domain name is only half the story. Email addresses have a local part (before the @) as well as a domain part, and the local part was ASCII-only until the EAI standards (RFCs 6530–6533, February 2012) added the SMTPUTF8 extension, which lets mail servers exchange non-ASCII addresses end to end. Gmail has recognized non-Latin email addresses since August 2014 — you can send to and receive from them — but many providers, forms, and validation scripts still reject anything outside ASCII. Before you put an IDN email address on a business card, send test messages through the providers your customers actually use, and keep an ASCII address as the fallback.
The same gap shows up everywhere else. Linkifiers that only recognize ASCII domains, validation regexes that reject non-Latin characters, apps that break on a Unicode URL — this is what ICANN's Universal Acceptance Steering Group (UASG) calls the Universal Acceptance problem. Governments are pushing hardest: India's National Internet Exchange (NIXI) offers Indian-language domain names in all 22 scheduled languages, and in April 2025 the Indian government began experimenting with Hindi URLs for the Ministry of Home Affairs — the English URL continues to work alongside the Hindi one. An IDN is a genuine asset for reaching a non-English audience, but budget for testing: your audience's software may be years behind your registrar.
IDN vs ASCII: Which Should You Register?
Factor | IDN (e.g. münchen.de) | ASCII (e.g. muenchen.de) |
|---|---|---|
Audience fit | Best when your audience reads and types in that script daily | Best for international or mixed-language audiences |
Memorability | Higher locally — it's the name as people actually write it | Higher globally — no keyboard or script barrier |
SEO | No ranking penalty; matches native-language queries | No advantage or penalty either way |
Email | Works only where the provider supports EAI/SMTPUTF8 | Works everywhere |
Phishing risk | Higher — lookalike variants are cheap to register | Lower — fewer confusable characters |
Price | Usually the same as the ASCII equivalent in the same TLD | Same |
The honest answer for most businesses: register both. Use the ASCII domain as your canonical address — the one on invoices, email, and ads — and use the IDN as a localized front door that redirects to it. That way you get the trust and memorability of a native-script name without betting your email deliverability and link-sharing on software you don't control.
Before You Buy: A 7-Point IDN Checklist
- One script per label. Never mix scripts inside a single label — registries may refuse it and browsers will show Punycode.
- Check the registry's language table for your TLD before falling in love with a name.
- Verify the Punycode form and search WHOIS for it — that's the form the internet actually stores.
- Buy the transliteration and the obvious lookalikes (including cross-script confusables) for any brand that matters.
- Test rendering in Chrome, Firefox, and Safari, on desktop and mobile, before launch.
- Test email end to end with the providers your customers use — and keep an ASCII fallback address.
- Keep the ASCII domain canonical. Redirect the IDN to it, and use the ASCII form anywhere a machine might need to parse the address.
FAQs
What is an internationalized domain name (IDN)?
An IDN is a domain name containing non-ASCII characters — Chinese, Arabic, Cyrillic, Devanagari, accented Latin letters, and other scripts. DNS still stores it as ASCII using Punycode; for example, münchen.de is stored as xn--mnchen-3ya.de. The Unicode form is what users see, the ASCII form is what the internet resolves.
What is Punycode and what does xn-- mean?
Punycode (RFC 3492, 2003) converts a Unicode domain label into ASCII letters, digits, and hyphens. The prefix xn-- marks a label as Punycode-encoded, so software knows to decode it back to Unicode for display. Every IDN's stored form starts with xn--.
Which top-level domains support IDN registration?
Most major TLDs do, including .com, .net, .org, .info, .de, .eu, and .in, plus dedicated IDN country-code TLDs such as Russia's .рф, China's .中国, and India's .भारत. Support depends on the registry and the script — always check the registry's IDN language table for your specific TLD and language.
Can I use emojis in a domain name?
Under IDNA2008, emoji code points are disallowed, so most registries refuse them. Namecheap states explicitly that emojis cannot be used as IDNs. A few TLDs allow them — Porkbun supports emoji IDNs on .fm, radio.fm, radio.am, and .ws — but they are an edge case, not a branding strategy.
Do IDNs hurt SEO?
No. Search engines treat IDNs and ASCII domains the same for ranking. An IDN can even help for native-language queries, since it matches the query's script exactly. What matters is content, links, and relevance — the same as any domain.
Are IDNs safe? What is a homoglyph attack?
IDNs themselves are safe, but Unicode contains lookalike characters across scripts — Cyrillic а looks identical to Latin a. Attackers register lookalike domains for phishing. Browsers defend by showing suspicious names as raw Punycode, but the defenses are heuristic: a 2021 USENIX study found Chrome showed Punycode for only 64.1% of 1,855 real homograph IDNs tested. Always check for the xn-- prefix on sensitive pages.
Can I have an email address with non-English characters?
Yes, in principle: the EAI standards (RFCs 6530–6533, 2012) define the SMTPUTF8 extension for non-ASCII addresses, and Gmail has recognized them since August 2014. In practice, support is uneven across providers and web forms, so test with your recipients' providers and keep an ASCII address as a fallback.
Should I register an IDN or an ASCII domain?
If your audience reads and types in a non-Latin script, register the IDN — and the ASCII transliteration too. Use the ASCII domain as your canonical address for email, invoices, and advertising, and let the IDN redirect to it. That gives you local trust and memorability without betting deliverability on software you don't control.




