Convert a domain name between Unicode and ASCII Punycode. Runs in your browser.
Runs in your browser — your input is processed on this device and never uploaded.
Enter a Unicode domain for ASCII conversion or an ASCII/Punycode domain for Unicode conversion.
Results appear here.
Punycode is how internationalized domain names fit into DNS, which only accepts ASCII labels. A Unicode label is rewritten with an xn-- prefix so resolvers can store it. This tool runs IDNA processing on a complete host name, not on a single label in isolation.
münchen.example into ASCII with Punycode labels. To Unicode turns an ASCII domain that already contains xn-- labels back into Unicode.DNS was built for ASCII. People still want names in their own scripts, so the system keeps the old protocol and hides the Unicode in a reversible ASCII form. Browsers show you the pretty name. Certificates, logs, and a lot of tooling still show the xn-- form.
Converting both ways is how you check that the name you typed is the name the resolver will see. Guessing from the pretty form is how lookalike names slip through.
URL Encoder and Decoder percent-encodes paths and query strings. That is a different grammar and will not produce a valid IDN.
Typing the Unicode name into a browser and copying whatever the address bar shows works for a quick check, and it hides the conversion. Use this page when you need the ASCII form itself, for a certificate, a zone file, or a log line.
A successful conversion does not prove you own the domain, and it does not protect against lookalike characters in another alphabet.
Enter a host name only. A full URL with a scheme, port, path, query, or fragment is the wrong input.
Encoded labels always start with xn--. If you do not see that prefix after To ASCII/Punycode, the name was already pure ASCII.
IDNA processing applies Unicode normalization and some rejection rules before Punycode runs. Two strings that look the same on screen can still fail or encode differently once those rules apply.