Email Format Validator
Check an email address against the rules that actually matter, and see why.
Convert internationalised domain names to punycode and back.
The Punycode Converter encodes internationalised domain names to their xn-- form and decodes them back, label by label, so you can see exactly which parts were encoded and what an xn-- domain really says.
DNS only carries ASCII, so a domain containing accents, Cyrillic, Arabic or Chinese has to be encoded before it can be resolved. Punycode is that encoding: münchen.de becomes xn--mnchen-3ya.de, and every browser does the conversion silently before it makes a request.
Each label — each dot-separated part — is encoded on its own, and only the labels that need it get the xn-- prefix, which is why a mixed domain keeps its ASCII parts unchanged. Decoding matters for a different reason: an xn-- domain in a log, an email header or a certificate is unreadable until you convert it back, and homograph attacks rely on that. Seeing the real Unicode is how you spot a Cyrillic "а" pretending to be a Latin one.
Each dot-separated label is handled on its own, so ASCII parts such as "com" are left untouched exactly as a resolver does it.
Decoding an xn-- domain shows the real characters, which is how you catch a Cyrillic letter impersonating a Latin one.
The full encoder and decoder, not a lookup table, so any script converts correctly in both directions.
Every label is listed with its original and converted form, so a long domain is easy to check piece by piece.
The result is decoded back and compared, so you know the conversion was lossless.
Unicode to punycode, or punycode back to Unicode.
A full domain with dots; each label is converted separately.
Every label is listed so you can see which ones were encoded and which were left alone.
Take the converted domain to your clipboard.
It is the ACE prefix, which marks a label as punycode-encoded. Without it a resolver could not tell an encoded label from a domain that happens to look like one.
Because punycode works per label. An ASCII label such as "com" needs no encoding and is left exactly as it was.
Registering a domain that uses characters from another script to look identical to a real one — a Cyrillic "а" in place of a Latin "a". Decoding the punycode is how you see the difference.
On the domain half, yes — that is how internationalised email domains resolve. The part before the @ uses a different mechanism, SMTPUTF8, and is not punycode-encoded.
What people who use the Punycode Converter think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the Punycode Converter. It takes half a minute and no account.
Write the first reviewCheck an email address against the rules that actually matter, and see why.
Serialise a JSON object into a percent-encoded URL query string.
Convert tab-separated data — or a spreadsheet paste — straight into JSON.
Generate prefixed API keys in the format modern providers use.
Tidy a TOML file: consistent quoting, ordered tables, keys before headers.
Shape corners individually, including the elliptical slash syntax.
Check YAML parses and find the line where the indentation goes wrong.
Generate Nano IDs — shorter than a UUID, and URL-safe by design.