Separate the hostname
URLs, paths, user information and ports are not part of an IDN conversion.
Direct answer: An IDN converter shows the Unicode and ASCII Punycode forms of the same domain labels so DNS, certificate and display values can be compared exactly.
The server validates and converts the submitted labels locally; it does not send them to DNS, a registry or a registrar. Result responses are private, uncached and excluded from search indexing. Do not enter passwords or secrets. Read the lookup privacy policy.
What this idn and punycode converter tells you
The converter shows the Unicode and ASCII-compatible forms of an internationalized domain name. Use it to verify exactly what will be sent through DNS and registration systems and to spot labels that merely look familiar.
- The normalized Unicode presentation accepted by the converter
- The ASCII A-label form beginning with xn-- where conversion is required
- Whether the input fails domain-label and IDNA processing
After confirming the exact ASCII hostname, submit that form to the WHOIS lookup so registration evidence is requested for the intended name.
If you are checking whether the normalized name can be registered, continue with availability screening for the normalized domain and treat the result as evidence, not a purchase guarantee.
How the evidence is collected
Process label by label
Each non-ASCII label is mapped and encoded under IDNA rules; ordinary ASCII labels remain readable.
Compare both forms
Save Unicode for human review and ASCII for exact DNS, certificate and registration comparisons.
Read the fields without overclaiming
| Signal | What it can establish | What it does not prove |
|---|---|---|
| U-label | A valid Unicode form of an internationalized label. | A guarantee the label is visually unambiguous. |
| A-label | The ASCII-compatible encoded label used by DNS-facing systems. | Encryption or obfuscation. |
| xn-- prefix | A marker for a Punycode-encoded A-label. | Evidence of abuse by itself. |
| Script | A writing-system property of characters in the label. | Language or registrant identity. |
Two domains appear similar on screen
Convert both to ASCII and compare code points rather than appearance. Different scripts can contain confusable characters, while legitimate names also use IDNs. For a security decision, verify the expected ASCII hostname, certificate names and trusted navigation source.
Common mistakes
- Calling all Punycode malicious
- Converting an entire URL as if it were a hostname
- Comparing glyph appearance instead of code points
- Assuming every registry permits every valid IDNA label
IDN and Punycode Converter FAQ
Is Punycode the same as IDNA?
Punycode is the encoding used inside the broader IDNA processing framework for eligible non-ASCII labels.
Why can a valid conversion still be unavailable?
Registries apply their own language tables, reserved-name rules, eligibility policy and variant handling.
What should I paste into DNS tools?
The ASCII hostname is the least ambiguous interoperable form, while keeping the Unicode form helps human review.
Explore more idn and punycode converter and domain research questions