We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
We use cookies.This website uses essential cookies to operate core features. With your consent, we also use analytics cookies to understand traffic and improve the service. For more details, see our .
Was this tool helpful to use?
Your feedback helps us make it better
An online converter for Internationalized Domain Names (IDNs) and ASCII formats, designed to process non-ASCII characters like Chinese domains.
Overview
Understand what the tool solves, how it works, and the boundaries of its data.
Punycode is a reversible way to represent Unicode text with ASCII characters. For internationalized domain names, it is applied label by label: the part before and after each dot is handled separately. A label containing non-ASCII characters receives the xn-- ACE prefix; an ordinary ASCII label remains as written. For example, bücher.example becomes xn--bcher-kva.example. The dot and the ASCII word example are preserved.
The algorithm is specified in RFC 3492. Punycode is only one part of internationalized domain-name handling; it does not by itself decide whether a label is eligible under IDNA rules.
Enter a single label or a dotted domain name, not a complete web address. Common Unicode full-stop characters are normalized to a dot, and a final dot representing the DNS root is retained. Each label is then encoded or decoded independently. ASCII labels that do not begin with the Punycode prefix are left unchanged in decode mode.
The input must not contain a URL scheme, slash, port, path, query, fragment, email separator, whitespace or an empty label between dots. Remove https:// and any path before converting. A trailing root dot is allowed, but consecutive dots create an empty label and are rejected.
Guide
Follow the workflow and verify inputs and outputs with practical examples.
Use Encode for Unicode domain text that you need to represent with ASCII. Use Decode for a Punycode label beginning with xn--. Direction is selected explicitly; it is not inferred from the input.
Keep dot-separated labels intact, including an optional final root dot. Strip a scheme, port, path and query string from copied browser addresses.
Check that non-ASCII labels gain their own xn-- prefix when encoded, while ASCII labels and separators stay in place. Copy the result you need.
Use cases
See how the tool fits into real work and everyday tasks.
Developers can inspect a Unicode spelling beside its ASCII-compatible form when checking configuration, logs or documentation.
When a system asks for an ASCII domain form, convert the domain text and then verify it against that system’s domain rules.
Q&A
Find concise answers to common questions and confusing cases.
xn--?Encoding is applied separately to each dot-delimited label. A label containing non-ASCII characters is prefixed; a plain ASCII label is preserved.
No. Remove the scheme, port, path and query first. This converter accepts a domain name or one label, not the rest of a URL.
No. It only recovers text from a Punycode label. It does not check registration, DNS, site identity, visual lookalikes or the full IDNA eligibility rules.
Notes
Review scope, result limitations, and important precautions before use.
A valid Punycode output is not proof that a domain can be registered, resolves in DNS, or will be displayed consistently by browsers. IDNA also includes higher-level processing and eligibility rules beyond the Bootstring algorithm. Check a candidate name with the registrar, DNS operator or application where you plan to use it. For an unfamiliar link, compare its source and spelling before opening it; conversion is not a phishing or trust check.
Related
Discover related tools, collections, and available API capabilities.