EditSafely

IDN Encode a String

Encode an internationalized domain name to its ASCII (xn--) form. Runs entirely in your browser, so your data never leaves your device.

0 chars · 0 lines

Output

The result appears here as you type.

How to use IDN Encode a String

  1. 1. Paste the Unicode domain. Enter the internationalized domain name into the input pane, including any accented or non-Latin characters, such as münchen.de.
  2. 2. Read how encoding works. There are no settings; the tool applies RFC 3492 punycode encoding to convert the Unicode domain into its ASCII-compatible xn-- form.
  3. 3. Copy the ASCII domain. Copy the encoded xn-- domain from the output pane and use it wherever a system, like a DNS record or an old form field, only accepts ASCII domain names.

When to use IDN Encode a String

IDN Encode a String converts a domain name containing accented or non-Latin characters into the ASCII-safe xn-- form that DNS and older systems require. Use it whenever you have a real-world internationalized domain and need its punycode equivalent for a config file, registrar or API call.

  • Registering a domain with a domain registrar API. A registrar's API only accepts ASCII domain labels, but your client wants a domain with an umlaut. Encoding it to punycode first gives you the string the API expects.
  • Configuring a DNS record for a non-English brand name. You're setting up a DNS zone file for a domain that includes non-Latin characters and the zone file format only supports ASCII labels, so you need the punycode form.
  • Testing an old form that rejects Unicode input. A legacy signup form throws an error on any domain field with non-ASCII characters. Encoding the domain to its xn-- form first lets you get past that validation for testing.
  • Comparing a domain against a punycode blocklist. A security tool maintains a blocklist of domains in their ASCII-compatible form. Encoding a Unicode domain you're checking lets you compare it directly against that list.

Examples

Encode

Input

münchen.de

Output

xn--mnchen-3ya.de

About the IDN Encode a String tool

IDN Encode a String does its work locally, right in the browser. Encode an internationalized domain name to its ASCII (xn--) form. There is no upload step, no queue and no account, and your data never travels over the network.

It belongs to the String Tools collection on EditSafely, a set of 159 small, focused String utilities that share the same instant, private workspace.

There is nothing to configure. Provide the input and the result appears on its own. A worked example further down the page shows exactly what the tool produces for a real input.

Running locally also makes the tool fast and dependable: results appear as you type or drop a file, there is no server outage that can take it down mid-task, and confidential data can be processed without a second thought.

Frequently asked questions

Is IDN Encode a String free to use?

Yes, it is completely free. All 2,658 tools on EditSafely work without an account, a subscription or usage limits.

Is it safe to paste sensitive or confidential data?

Everything happens locally. Your browser downloads the tool's code once, then does all the processing itself; nothing you enter is transmitted, stored or logged. You can even go offline after the page loads and it will still work.

How much text can I process at once?

There is no fixed limit. Because the work happens on your own device rather than on a shared server, the practical ceiling is your machine's memory, which comfortably handles inputs far larger than typical online tools allow.

Do I need to sign up or install anything?

No. The tool works in any modern browser on desktop, tablet or phone. There is no account to create, no extension to add and no software to install.

How do I use the result?

The output panel has a one-click copy button, and you can keep refining the input while you work; the result updates in place as you type.