Free · live registry data · no login

Punycode Converter

Convert between Unicode and xn-- names.

How it works

Convert between Unicode domain names and xn-- Punycode

Paste an internationalised domain like münchen.de, 例子.测试 or an xn-- name and get the other form instantly, label by label, using a complete RFC 3492 implementation that runs in your browser. The result shows each label's conversion, which scripts it uses, whether it mixes scripts in a way that browsers flag as spoofing, and whether the ASCII name actually exists in DNS. Useful for registering, debugging email on IDN domains and spotting lookalike attacks.

Results appear here after you click Convert.

How this works

1
Split into labels
Each dot-separated label is converted on its own, since Punycode works per label, not per domain.
2
Run RFC 3492
Our own Punycode encoder/decoder maps Unicode code points to the xn-- ASCII form and back, then round-trips to verify.
3
Check scripts and DNS
We detect mixed-script labels that browsers block and query NS records to see whether the ASCII name exists.

Frequently asked questions

What is Punycode and why do domains start with xn--?: DNS only understands ASCII letters, digits and hyphens, so internationalised domain names (IDNs) with accents, Cyrillic, Arabic or Chinese characters are encoded into an ASCII form prefixed with xn--. Punycode (RFC 3492) is the algorithm that does this; browsers decode it back for display.
How do I register a domain with special characters like ü or ñ?: Choose an extension that supports IDNs (.de, .com, .net, .org, .ng's parent registries and many ccTLDs do), convert the name to xn-- form with this tool and search for that ASCII string. Registries store the xn-- version; your registrar may show the Unicode name alongside it.
Why does my browser show xn-- instead of the Unicode name?: Browsers only display the Unicode form when all characters in a label come from one script that is allowed for that TLD. Mixed-script or confusable names, such as a Cyrillic 'а' inside 'apple', are shown as xn-- on purpose to prevent phishing.
Does email work on an internationalised domain?: The domain part can work if you configure MX records with the xn-- form, but many mail servers and clients still cannot handle Unicode in addresses (SMTPUTF8/EAI). For reliable business email, pair your IDN with an ASCII domain and use that for mail.
Is Punycode the same as URL encoding?: No. URL (percent) encoding escapes bytes in paths and query strings as %XX. Punycode only applies to the hostname and produces plain letters and digits so the name is valid in DNS. A URL with an IDN host can use both at once.

Every MailShrine domain includes WHOIS privacy, transfer lock, Anycast DNS with DNSSEC and two business mailboxes.