International Email Verification — Full Guide with Unicode and IDN | Proofy

International email addresses — those containing non-ASCII characters in either the local part or the domain — are increasingly common as global commerce shifts away from English-only systems. Verifying them well requires a different toolkit than standard Latin addresses. A validator that doesn't natively understand RFC 6531 (SMTPUTF8) or RFC 5891 (IDNA) will either reject legitimate international addresses outright or pass them through unchecked, both of which damage deliverability.

This guide explains how international email actually works under the hood, why verification needs special handling, and what to look for in a validator that handles global lists correctly.

How International Email Addresses Work

Before 2009, email addresses were restricted to the ASCII character set — Latin letters, digits, and a handful of symbols. Anyone whose name used Cyrillic, Chinese, Arabic, Hindi, or any other non-Latin script had to transliterate. A user named Petr Ivanov could only register as petr.ivanov@domain.com.

IETF standards introduced in 2010–2012 changed that. RFC 5891 (Internationalized Domain Names) allows non-ASCII characters in the domain portion through Punycode encoding, and RFC 6531 (SMTPUTF8) allows non-ASCII characters in the local part of the address itself. Together they enable addresses like:

• петр.иванов@домен.ком — Cyrillic local part and domain
• 用户@例子.公司 — Chinese script throughout
• محمد@أمثلة.شركة — Arabic script throughout
• jürgen@müller.de — Latin with diacritics

These addresses are entirely valid under modern standards, provided the receiving server supports SMTPUTF8 — which most major providers (Gmail, Outlook, Yahoo, and major hosted email platforms) now do.

Why International Email Verification Is Harder

Three technical challenges make international addresses trickier to validate than Latin-only addresses:

• Domain encoding mismatches. An IDN domain has two forms: the human-readable Unicode form (домен.ком) and the Punycode form (xn--d1acufc.xn--j1aef). DNS lookups operate on Punycode, but users type Unicode. A verifier must convert between the two without losing accuracy.
• SMTPUTF8 support gaps. Not every mail server on the receiving path supports UTF-8 envelopes. Some legacy systems silently downgrade or reject international addresses. A verifier needs to check whether the destination server actually advertises SMTPUTF8 capability before treating the address as deliverable.
• Normalization edge cases. Unicode has multiple ways to represent the same visual character — for example, the letter ñ can be encoded as a single code point (U+00F1) or as n plus a combining tilde (U+006E + U+0303). Verifiers must normalize before comparing addresses, or two valid-looking addresses can fail to match the same mailbox.

The combined effect: a validator that treats an international address as ordinary ASCII will return wrong results in a meaningful share of cases — either false negatives (rejecting valid addresses) or false positives (passing addresses the destination won't actually accept).

How to Validate International Email Addresses Correctly

A complete international verification pass runs through the same four steps as standard validation, with extra care at each:

1. Syntax check against RFC 5321/5322 plus RFC 6531 (allow UTF-8 in local part) and RFC 5891 (Punycode in domain).
2. Domain normalization — convert Unicode domain to Punycode for DNS, but preserve the original Unicode form for display.
3. MX record lookup on the Punycode domain to confirm the mail server exists.
4. SMTP probe that advertises SMTPUTF8 in the EHLO and uses MAIL FROM with the SMTPUTF8 extension when checking the inbox. If the server doesn't support SMTPUTF8, the address isn't deliverable even if all earlier checks pass.

For large lists, the same workflow runs in bulk through a service designed for international handling. Proofy's bulk email verification service handles mixed ASCII and internationalized addresses without preprocessing, including Punycode normalization and SMTPUTF8 capability detection on the destination server.

API-Based Verification for International Programs

If you're collecting international addresses through web forms, in-product signups, or third-party integrations, real-time verification at the point of entry catches problems before they reach your list. The email verifier exposes the same international handling logic that bulk verification uses, returning a deliverability assessment in under 200ms per address. The benefit: invalid international addresses (typos, dead domains, unsupported scripts on the destination) get flagged at signup, never entering your list at all.

What Clean International Lists Actually Buy You

The benefits of catching invalid international addresses early are the same as for any list, but the cost of getting it wrong is higher:

• Higher delivery rates — typically 97–99% for verified lists versus 85–90% for unverified international lists.
• Protected sender reputation — international hard bounces hit the same reputation score as ASCII bounces, but they also expose your program to country-specific reputation tracking that some ISPs run separately.
• Better engagement signal — clean lists mean opens and clicks come from real recipients, which improves ESP-level engagement scoring.
• Regulatory compliance — GDPR (EU), Russia's Federal Law 152-FZ, and several Asian data-protection regimes all penalize mishandling of personal data, including sending to addresses that should have been validated and removed.
• Cleaner analytics — false bounces inflate negative metrics and obscure the actual performance of campaigns.

Common Mistakes with International Email Verification

• Assuming a regex covers it. A standard email regex written for ASCII will reject most valid international addresses. The full RFC 6531-compliant pattern is dramatically more permissive and rarely written from scratch correctly.
• Skipping SMTPUTF8 capability detection. A receiving server can have a valid MX record but reject UTF-8 envelopes. Without checking, you'll mark unreachable mailboxes as deliverable.
• Storing Unicode without normalization. If your database holds both café@example.com (precomposed ñ-style) and café@example.com (decomposed combining mark), the two won't match on lookup. Always normalize to NFC on save.
• Treating Punycode and Unicode as different addresses. петр.иванов@домен.ком and петр.иванов@xn--d1acufc.xn--j1aef are the same address. Deduplicate after normalization, not before.
• Using a verifier that doesn't disclose international handling. Some validators silently downgrade or skip international addresses, returning "unknown" or "valid" without actually checking. Always confirm the verifier documents IDN and SMTPUTF8 support before trusting it on global lists.

FAQ

Are international email addresses safe to use in production?

Yes for receiving — major mailbox providers (Gmail, Outlook, Yahoo, Apple, Yandex, Mail.ru) all accept international addresses. For sending campaigns to them, support is also widespread among major ESPs. Smaller or self-hosted destinations are the variable; always verify before bulk sending.

What is Punycode and why does it matter?

Punycode is an ASCII-compatible encoding for internationalized domain names. The Unicode domain домен.ком becomes xn--d1acufc.xn--j1aef in Punycode. DNS only understands ASCII, so DNS lookups always operate on Punycode — but users see the Unicode form. Verifiers must convert in both directions correctly.

Can I send marketing email to international addresses under GDPR?

Yes, with the same consent requirements as ASCII addresses. The encoding of the address has no bearing on GDPR's consent, transparency, and opt-out rules — what matters is whether you have a lawful basis for the contact and a clear unsubscribe mechanism.

Does free email verification work for international addresses?

It depends on the provider. Some free-tier verifiers handle IDN and SMTPUTF8 correctly; others quietly skip non-ASCII addresses. Test with a known-valid international address before relying on any free-tier verifier for a real list. For ongoing list hygiene, see also how to get email addresses cleanly and how to tell if an email is fake.

How many international addresses do typical lists contain?

For globally distributed B2C lists, 5–25% of addresses can be international depending on audience. For B2B lists targeting EU, Russian, or Asian markets, the share is often higher. Even US-focused lists frequently contain 1–3% international addresses from immigrants, students, and remote workers.

What happens if I try to send to an SMTPUTF8 address from a non-SMTPUTF8 server?

The send fails. Older mail servers will return a 5xx error or silently downgrade and lose information. Modern ESPs (Mailchimp, SendGrid, Brevo, Postmark, Klaviyo) all support SMTPUTF8; if you're sending through a custom or older SMTP server, confirm the EHLO response advertises SMTPUTF8 before relying on international addresses. Once delivery is sorted, regular validation keeps the list clean over time.