Convert & Validate Domain Names
Enter a Unicode domain (such as caffè.it or 東京.jp) or an ASCII Punycode string (xn--mnchen-3ya.de) to convert and check RFC compliance.
How IDNs & Punycode Work
Because core DNS servers natively understand only ASCII characters (a–z, 0–9, and hyphens), Internationalized Domain Names (IDNs) are translated into xn-- labels using Punycode (RFC 3492). Review all rules in Domain Naming Rules or browse country extensions in the Domain Directory.
Human Display vs. DNS
Browsers show münchen.de or caffè.it in the address bar, while DNS zones, SSL certificates, and server configs use xn--mnchen-3ya.de and xn--caff-8oa.it.
RFC Length Limits
A single domain label can be 1 to 63 characters (after Punycode conversion), and the full domain name must not exceed 253 ASCII characters.
Hyphen & TLD Rules
Labels cannot start or end with a hyphen (-), and the top-level domain cannot be purely numeric.
Frequently Asked Questions
Punycode (RFC 3492) is a standard encoding algorithm that represents Unicode strings (such as accented European letters, Cyrillic, Arabic, or Kanji) using only ASCII letters, digits, and hyphens prefixed with xn--.
The foundational DNS specifications (RFC 1035 / RFC 1123) only support 7-bit ASCII hostnames. Punycode preserves full backward compatibility across global routers, mail servers, and legacy resolvers.
Each label between dots must be 1–63 characters, total domain length cannot exceed 253 ASCII characters, only a-z, 0-9, and hyphens are valid in ASCII labels, and labels cannot start or end with a hyphen.
It is a spoofing technique where visually similar Unicode characters from different scripts (e.g. Cyrillic 'а' vs Latin 'a') mimic a trusted brand. Modern browsers reveal the raw xn-- Punycode form when mixed scripts look suspicious.