How to use
- Choose a direction. Unicode domain to Punycode turns
한글.comintoxn--bj0bj06e.com; Punycode to Unicode domain does the reverse. - Paste one domain or URL per line. The result appears right below, and with more than one line a table pairs each input with its result.
- If you paste a URL such as
https://도메인.한국/경로?q=1, only the host is converted. Path, query, port and user info stay untouched. - Use Move result to input and flip direction to round-trip a value and check it.
Why punycode exists
DNS was designed for lowercase English letters, digits and hyphens. A domain with Korean, Chinese or accented letters (an IDN, internationalized domain name) is stored and looked up in an ASCII form called punycode (RFC 3492). The browser address bar may show 한글.com, but the actual request, the TLS certificate, mail server settings and DNS records use xn--bj0bj06e.com.
Each label (the parts between dots) is converted separately. Labels with only ASCII characters stay as they are; labels with other characters get the xn-- prefix followed by the punycode string.
| Domain | Result |
|---|---|
| 한글.com | xn–bj0bj06e.com |
| 도메인.한국 | xn–hq1bm8jm9l.xn–3e0b707e |
| bücher.de | xn–bcher-kva.de |
| münchen | xn–mnchen-3ya |
| 例え | xn–r8jz45g |
| naver.한국 | naver.xn–3e0b707e |
Rules and limits
- Input is normalized to Unicode NFC and lowercased first, so
BÜCHER.deandbücher.degive the same result. - Fullwidth (
.) and ideographic (。) full stops count as dots. A trailing dot is kept. - After conversion a label may not exceed 63 characters and the whole domain 253. The tool tells you which line is the problem. Korean syllables take two or three characters each in punycode, so long Korean labels hit 63 faster than you might expect.
- The tool implements the RFC 3492 encode and decode algorithm. It does not enforce registry policies such as allowed scripts or blocking look-alike characters (IDNA validation), so check with your registrar whether a name can actually be registered.
Frequently asked questions
Why does a Korean domain show up as xn– somewhere?
DNS and certificates only handle ASCII, so IDNs are stored as punycode. The browser converts them back for display, but config files and DNS records often need the xn– form.
Can I decode an xn– string?
Yes. Pick Punycode to Unicode domain and enter xn--bj0bj06e.com to get 한글.com. Invalid punycode is reported as an error.
Does it convert non-ASCII in the path or in an email address?
No, only the domain (host). Non-ASCII characters in a URL path need percent-encoding; use the URL Encoder for that.
Why is a double dot an error?
Empty labels are not allowed in a domain name. It is most likely a typo.
To inspect individual code points use the Unicode Converter, and for page tags that go with your domain see the Meta Tag Generator. Text you enter is processed in your browser and never sent to a server.