Punycode is an encoding that represents Unicode characters using only ASCII. It's used for internationalized domain names because the DNS system only supports ASCII.

Does it follow the RFC 3492 standard?

Yes. It implements the standard Bootstring algorithm, verified against known test vectors.

Is the domain I enter sent to a server?

No. Encoding and decoding happen entirely in your browser.

Why does my Korean domain look odd?

The address bar shows Unicode, but DNS queries go out as Punycode — some environments display the xn-- form directly.

Is each subdomain converted separately?

Yes — each dot-separated label converts independently, so only non-ASCII labels become Punycode.

🔤 Punycode Converter

Convert internationalized domains to Punycode (xn--), or decode Punycode back to the original string.

Input (domain or string)

Result will appear here

How to use

Enter an internationalized domain or string.
Click "→ Punycode" or "→ Original string".
Copy the result to use it.

🎯 Use Cases

Find the real DNS registration name of an IDN domain (e.g. 한글.com)
Decode an xn-- domain shown in an email or browser address bar
Preview the Punycode form before buying an IDN domain

Example

Input

한글.com

Output

xn--bj0bj06e.com

Clicking "→ Punycode" converts the Korean domain "한글.com" into "xn--bj0bj06e.com", the ASCII form actually registered in DNS. Entering that value and clicking "→ Original string" decodes it back to "한글.com".

Punycode and internationalized domains

DNS only handles ASCII, so non-Latin domains are encoded as Punycode starting with xn--.

Concept	Details
Punycode	Encodes Unicode strings into ASCII — the result starts with `xn--`
Example	`한국.kr` → `xn--3e0b707e.kr`
Purpose	Internationalized domain names (IDN) — registration and DNS use the Punycode form
Decoding	Turns the xn-- ASCII form back into the original Unicode

FAQ

What is Punycode?: Punycode is an encoding that represents Unicode characters using only ASCII. It's used for internationalized domain names because the DNS system only supports ASCII.
Does it follow the RFC 3492 standard?: Yes. It implements the standard Bootstring algorithm, verified against known test vectors.
Is the domain I enter sent to a server?: No. Encoding and decoding happen entirely in your browser.
Why does my Korean domain look odd?: The address bar shows Unicode, but DNS queries go out as Punycode — some environments display the xn-- form directly.
Is each subdomain converted separately?: Yes — each dot-separated label converts independently, so only non-ASCII labels become Punycode.