IDN Conversion Instructions
- Enter your Unicode domain or Punycode (xn--) label into the input field.
- Choose "Unicode → Punycode" or "Punycode → Unicode" to process.
- Review the converted DNS label structure in the output panel.
- Copy the resulting string for use in your registrar or configuration files.
Punycode Encoder / Decoder provides the bridge between human-readable Unicode domains (münchen.de, 例え.jp, 🍕.ws) and the ASCII-only world of DNS. This tool converts in both directions using the browser's native URL parser, which implements the IDNA 2008 / RFC 3492 algorithm - so the output matches what every modern browser actually resolves.
DNS Label Encoding Logic
Encoding is per label: each dot-separated chunk is examined, and only those containing non-ASCII code points get the "xn--" prefix and ASCII-Compatible Encoding (ACE). Decoding reverses the process. Pure-ASCII labels pass through unchanged. The encoding is bit-exact and round-trippable, so any string you encode and then decode returns to its original form. This IDN converter ensures your internationalized domain names are compatible with legacy server infrastructure.
- IDNA 2008 / RFC 3492 via the browser's native URL parser
- Per-label encoding preserves complex dot structure
- Round-trip safe for any Unicode input or emoji domain
- Decodes any "xn--" label back to its original script
Frequently Asked Questions
What is Punycode?
Punycode (RFC 3492) is the encoding that lets DNS - which only allows ASCII letters, digits, and hyphens - represent labels containing arbitrary Unicode. Each non-ASCII label is rewritten with the prefix "xn--" followed by an ASCII-Compatible Encoding of the original characters.
Why does "münchen.de" become "xn--mnchen-3ya.de"?
The "ü" cannot live in a DNS label, so it is moved to the end as a numeric reference (3ya) while the basic ASCII letters stay in place. The "xn--" prefix tells software the label is encoded and needs decoding before display.
Are emoji domains supported?
Yes - emoji are just Unicode code points, so they encode the same way. ".ws", ".to", and a handful of other registries actually allow emoji second-level domains; most do not.
Why is Punycode considered a phishing risk?
Lookalike Unicode characters (Cyrillic "а" vs Latin "a") can produce domains that read identically to a human but resolve to a different server - the so-called IDN homograph attack. Modern browsers display the raw "xn--" form for mixed-script domains to mitigate this.
Explore the full suite of ENCODERS tools and 290+ other free utilities at Chunky Munster. For reliable domain name management, bookmark this Punycode Encoder / Decoder.