Toolsky

Free Online Tools & Utilities for Every Task.

Unicode to Punycode

Convert Unicode to Punycode.

Someone in Munich wants to register münchen.de, and someone in Tokyo wants a domain in Japanese. The domain name system, however, was built in the 1980s around plain English letters, digits and hyphens. Punycode is the translation layer that reconciles those two facts: it rewrites a Unicode domain into an ASCII-only form that DNS can handle, marked with the tell-tale xn-- prefix. The Unicode to Punycode converter on ToolSky performs that translation instantly, so you can see, register, configure or troubleshoot the exact encoded form of any internationalised domain name.

Why Domains Need Punycode at All

An internationalised domain name, or IDN, lets people use addresses in their own scripts: Arabic, Chinese, Cyrillic, accented Latin and many more. People read and type the Unicode version, but underneath, DNS only accepts a restricted character set. Punycode, defined in RFC 3492, is the algorithm that squeezes a Unicode string into that restricted set. The result keeps any plain ASCII letters visible, encodes the special characters into a compact suffix, and gains the xn-- prefix so software knows the label is encoded rather than literal.

This is not an optional extra. When you buy an IDN, the registry records the punycode form. When you set up hosting, SSL certificates or email for it, the punycode form is usually what the control panel expects, even though your visitors will only ever see the Unicode version in their address bar.

What the Unicode to Punycode Converter Does

  • Takes a domain written in Unicode, with accents or a non-Latin script, and returns its exact punycode encoding.
  • Shows you the xn-- form that registries, DNS records and certificate tools actually store.
  • Handles individual labels and full domains, so you can check a name before registering it or configure services for one you already own.

Working in the opposite direction, the Punycode to Unicode converter decodes xn-- strings back into readable form, and the IDN Punycode Detector helps you examine domains you encounter out in the wild, which matters because lookalike characters in IDNs are a known phishing trick.

How to Convert a Unicode Domain to Punycode

  1. Type or paste the Unicode domain name, for example the name exactly as your audience would write it.
  2. Make sure you are converting the domain only, without http://, paths or page names, since punycode applies to domain labels, not whole URLs.
  3. Run the conversion.
  4. Read the encoded result, which will begin with xn-- for any label containing non-ASCII characters.
  5. Copy the punycode form into your registrar, DNS or hosting configuration wherever an ASCII domain is required.
  6. Optionally decode it back with a reverse converter to confirm the round trip returns your original name.

Two Familiar Domains, Encoded

The classic textbook example is the German word for books. The domain bücher.example, with its ü, encodes to xn--bcher-kva.example: the plain letters b, c, h, e and r stay visible, and the suffix after the hyphen carries the information needed to reconstruct the ü and its position. A real-world case is münchen.de, Munich's name in German, which becomes xn--mnchen-3ya.de. Type either form into a modern browser and you arrive at the same place, because the browser quietly performs this exact conversion before asking DNS for directions.

Where Punycode Conversions Trip People Up

The commonest error is pasting a whole URL into the converter. Punycode encodes domain labels one at a time; the slashes, page paths and query strings of a full web address are not part of the deal and need different treatment, namely ordinary URL encoding. The second error is forgetting that the conversion belongs to the domain you register and configure, while marketing materials should always show the friendly Unicode version your customers recognise.

Security deserves a mention too. Because some characters in different scripts look nearly identical to Latin letters, attackers have registered punycode domains that render as perfect imitations of famous brands. When a converted result looks like a well-known name but the underlying characters are not what they seem, treat the domain with suspicion. Owners of legitimate IDNs should also check every service in their stack, since an older mail server or monitoring tool may handle the xn-- form awkwardly.

Frequently Asked Questions About Punycode

What does the xn-- prefix mean?

It is a reserved marker announcing that the label which follows is punycode-encoded. Browsers and mail clients see the prefix, decode the rest, and display the Unicode name to the user.

Are the Unicode and punycode forms two different domains?

No. They are two spellings of one domain. The punycode form is what DNS and registries store; the Unicode form is what people read. Registering one gives you the other automatically.

Can I register a domain name in my own language?

In most cases, yes. Many country and generic top-level domains accept IDN registrations in relevant scripts. You register and pay for the name once; behind the scenes it is recorded in punycode.

Does punycode apply to the whole web address?

No, only to the domain labels that contain non-ASCII characters. Page paths in other languages are handled by percent-encoding in the URL, which is a separate mechanism.

Why does my hosting panel reject my Unicode domain?

Many control panels, certificate authorities and DNS tools expect the ASCII form. Convert the name here and paste the xn-- version into the panel, and it should be accepted.

Do email addresses work with punycode domains?

Generally yes, using the punycode form of the domain after the @ sign. Support varies among older mail systems, so test deliverability if the address is important.

Which scripts and languages does punycode support?

Effectively all of Unicode: accented Latin, Greek, Cyrillic, Arabic, Hebrew, Chinese, Japanese, Korean, Indic scripts and more can be encoded, which is the entire point of the system.

One Domain, Two Spellings

Your visitors will remember the name in their own language; your infrastructure will quietly use the encoded twin. Converting between the two on demand means you can register, configure and verify internationalised domains without ever guessing at the ASCII form your tools are asking for.