Punycode Converter Online — Convert Internationalized Domains to Punycode Free
CodexFuse Team · 2026-11-04T08:45:13.837Z · 9 min read min read
Convert internationalised domains to Punycode free: encode münchen.de to xn--mnchen-3ya.de, avoid DNS and email failures, and manage IDNs the easy way.
A punycode converter turns an internationalised domain name — one containing letters such as ü, é or ñ — into the ASCII-only form that the Domain Name System (DNS) can actually resolve. The converted form always starts with xn--, so münchen.de becomes xn--mnchen-3ya.de. Browsers show visitors the readable version, while DNS, certificates and mail servers work with the encoded version behind the scenes.
That gap between what people see and what machines read is where most international-domain problems start. A domain can look perfect in a browser and still fail in an email setup, a DNS record or a certificate request, simply because one system received the Unicode form and another expected Punycode.
What is a punycode converter?
A punycode converter is a free online utility that encodes a Unicode domain name into ASCII Punycode, or decodes Punycode back into its readable Unicode form. It follows the RFC 3492 encoding standard, handles each label of a multi-part domain separately, and leaves plain ASCII domains unchanged. It does not register domains, check availability or change DNS records.
Punycode exists because DNS was built for ASCII letters, digits and hyphens only. Internationalised Domain Names (IDNs) let businesses use their real language in a domain, but underneath, every IDN must still travel through that ASCII-only system. The xn-- prefix is the signal that a label is an encoded Unicode name.
That is why the same domain legitimately has two faces. Customers see münchen.de. The DNS zone, hosting panel and certificate authority see xn--mnchen-3ya.de. Neither is wrong — problems only appear when the wrong face is pasted into the wrong place.
Why do international domains need converting at all?
International domains need converting because DNS, the system that turns domain names into server addresses, only understands ASCII characters. A Unicode character such as ü has no meaning to DNS, so it must first be encoded into an ASCII string beginning with xn-- before a lookup, a mail route or a certificate request can succeed.
For a business trading under a name with an accented character, dropping the accent changes the brand and weakens local recognition. An IDN keeps the brand intact. The trade-off is operational: the business now has two representations of one domain, and every tool in the chain must be given the right one.
Email is the most common tripwire. A mailbox configured with the Unicode form may work in one client and bounce in another. DNS records are another: a CNAME or TXT record entered with the readable form, where the panel expects Punycode, will not resolve as intended.
Never paste a Unicode domain into a DNS record, certificate signing request or mail-server configuration without checking which form that system expects. When in doubt, convert it first and use the xn-- form — it is the form the infrastructure understands.
A worked example: a Munich bakery takes its name online
Lena runs a family bakery in Munich and wants her website to match her shopfront name. Treat this as a fictional scenario, but the conversion itself is exact. She opens the Punycode Converter, selects Unicode-to-Punycode mode, types münchen.de and clicks Convert.
The tool returns xn--mnchen-3ya.de. Lena copies that string — not the readable version — into three places: the DNS A record pointing at her hosting, the domain field of her SSL certificate request, and the domain setting of her business mailbox. Customers still see münchen.de in their browsers, but every system behind the scenes resolves the same encoded name.
She then verifies the reverse direction: decoding xn--mnchen-3ya.de returns münchen.de, confirming a clean round trip. And www.münchen.de converts label by label to www.xn--mnchen-3ya.de — the www label is already ASCII, so it passes through untouched.
| What Lena entered | What the converter returned | Where the encoded form belongs |
|---|---|---|
| münchen.de | xn--mnchen-3ya.de | DNS records, certificate requests, mail setup |
| www.münchen.de | www.xn--mnchen-3ya.de | Subdomain DNS entries and redirects |
| example.com (plain ASCII) | example.com (unchanged) | Anywhere — no conversion needed |
How do you convert a domain to Punycode without breaking it?
To convert a domain to Punycode safely, enter only the domain name itself, select the correct direction — Unicode to Punycode for encoding, Punycode to Unicode for decoding — click Convert, and copy the full result including the xn-- prefix, skipping any protocol or path.
The CodexFuse tool keeps the process to the three steps shown on its own page:
- Enter your domain name: type just the domain, such as
münchen.de, with no protocol or path attached. - Choose encode or decode mode: Unicode to Punycode when you need the DNS-ready form, Punycode to Unicode when you need to read an encoded name back.
- Click Convert and copy the result: copy the entire output string, including the
xn--prefix, into the system that needs it.
After converting, decode the result back before you use it anywhere important. If the round trip returns exactly what you typed, the conversion is sound. If it does not, you probably included a protocol, a path or a stray character.
Mistakes that break international domains
- Converting the whole URL: pasting
https://münchen.de/shopinstead of just the domain produces a meaningless result — convert the domain label only. - Dropping the xn-- prefix: the encoded label without its prefix is not a valid Punycode name and will not resolve.
- Mixing the two forms in one setup: using Unicode in DNS and Punycode in email creates mismatches that look like outages but are really inconsistent records.
- Forgetting subdomains: each label converts separately, so check
shop.münchen.deindividually rather than assuming the root conversion covers it.
If a domain stops resolving after a change, recheck the conversion first — before assuming the host is down. Re-decode the Punycode in your DNS zone and compare it character by character with the brand name. Related pre-launch checks, such as a domain age checker or a blacklist checker, belong in the same routine.
If international domains, email deliverability and DNS records are eating your week, move them to CodexFuse: one fully managed platform where hosting, business email and domain setup are handled for you, on pay-as-you-go credits with no subscription lock-in.
Get Started with CodexFuseWhat a punycode converter does not do
A converter does not register the domain, check availability, create DNS records, issue certificates or fix propagation delays — if DNS has not propagated yet, a correct conversion will still appear not to work for a while. It also does not warn you about lookalike-domain abuse: characters from different scripts can look identical, and a converter will happily encode a lookalike name. Consider registering the plain-ASCII variant too and redirecting it to the IDN, so customers who type the unaccented version still arrive.
For the wider domain routine around a new launch, see the domain management checklist and the guide to choosing a domain name before you commit to an IDN.
Running domains the managed way on CodexFuse
On CodexFuse, the pattern for a business like Lena's is straightforward: convert the IDN with the free Punycode Converter, then use the encoded form wherever the platform's domain, hosting or email setup asks for the DNS-ready name. Because CodexFuse is fully managed, the hosting, business email and security setup around that domain are handled rather than left as separate services to stitch together — and because it runs on credits, the business pays as it goes instead of committing to a subscription.
A practical decision rule: if your domain, email and website currently live with three different providers and every change means three support tickets, consolidation is worth more than any single tool. If you only need a single one-off conversion, the free tool alone is enough — use it, copy the result, and move on.
Frequently Asked Questions
What is Punycode?
Punycode is the RFC 3492 encoding that represents Unicode characters using only ASCII letters, digits and hyphens, so internationalised domain names work with DNS. Encoded labels begin with xn--, which tells systems that the label is an encoded Unicode name rather than a plain ASCII one.
How do I convert münchen.de to Punycode?
Select Unicode to Punycode mode in the converter, enter münchen.de and click Convert. The result is xn--mnchen-3ya.de — copy the full string, including the xn-- prefix, into your DNS record, certificate request or mail configuration.
Is the Punycode Converter free?
Yes. The tool is free to view with no signup required, and conversion runs locally in your browser, so nothing you type is uploaded to a server. A free CodexFuse account removes usage limits if you convert domains regularly.
Can I convert a domain back from Punycode?
Yes. Choose the Punycode-to-Unicode (decode) direction, paste the encoded name such as xn--mnchen-3ya.de, and the tool returns the readable form münchen.de. Decoding is the quickest way to verify a conversion before you publish it.
Do I need Punycode for a normal .com domain?
No. Plain ASCII domains pass through unchanged — the converter returns them exactly as entered. Punycode only matters when a domain label contains a character outside the ASCII set, such as ü, é, ñ or characters from non-Latin scripts.
Why does my international domain not resolve after I set it up?
Usually one of three causes: the wrong form was pasted into a DNS record, DNS has not finished propagating, or a subdomain label was never converted. Re-decode the Punycode in your zone, check each label, and allow propagation time before assuming a deeper fault.
Stop guessing which form your domain needs
Convert the domain once, verify the round trip, and paste the encoded form everywhere the infrastructure asks for it. That single habit prevents the most common international-domain failures. And if managing domains, hosting, email and security across separate providers is the real pain — not the conversion itself — move the whole setup to CodexFuse today: bring your domain, let the managed platform handle hosting, business email and protection on pay-as-you-go credits, and stop babysitting records across three dashboards.
