MAIL

Email Validator

Validate email address format

Validation
🔒 100% client-side — your data never leaves this page
Maintained by Evan•Updated: September 29, 2026•Reviewed: September 29, 2026
Page reading mode

The full guide also includes pitfalls, worked examples, snippets, FAQs, and related tools for checking results or troubleshooting.

About this tool

Check one email address per line and see a specific reason for each format failure. This checker supports unquoted ASCII local parts and ASCII DNS-style domain names. It checks dot placement, label boundaries and address lengths; it does not contact mail servers, query MX records, or confirm an inbox exists. Domain case is normalized, while the local part before @ is preserved by default. Optional deduplication uses that normalized address. Changing the input or options clears previous results. Email input is not saved to browser storage or included in this tool’s analytics.

Failure Clinic (Common Pitfalls)

A passing address still bounces

Cause: Syntax alone does not show whether a domain or inbox accepts mail.

Fix: Use the receiving system’s verification flow; do not interpret this local check as proof of deliverability.

Scenario Recipes

01

Check domain-case duplicates without merging local parts

Goal: Clean a small import sample while preserving potentially distinct recipients.

  1. Paste [email protected], [email protected], [email protected] and [email protected] on separate lines.
  2. Keep deduplication enabled and preserve local-part case. Run validation.
  3. The first two addresses are duplicates; lowercase alice remains separate. The last address fails because it has consecutive local-part dots.

Result: Two passing addresses, one failing address, and one removed duplicate. Copy only the list you intend to use.

Production Snippets

Frequently Asked Questions

Does valid mean that the mailbox exists?

No. It means the address matches this checker’s supported syntax. Domain registration, MX records, recipient status and delivery acceptance are not checked.

Which addresses are outside the supported syntax?

Quoted local parts, comments, domain-literal IP addresses, Unicode domain names and non-ASCII local parts are not supported. An already encoded ASCII Punycode label can pass syntax checks, but its encoding, registration and mail setup are not verified.

Why preserve the text before @?

Mail domains are case-insensitive, while local-part handling belongs to the destination mail system. Preserving its case avoids silently merging [email protected] and [email protected].

Can I check or copy a list?

Paste one address per line, run validation, then copy the passing or failing list. Passing addresses can be deduplicated using normalized domain case and preserved local-part case; failing rows remain visible for correction.

Why is [email protected] rejected?

An unquoted local part cannot begin or end with a dot, or contain consecutive dots. The checker also rejects DNS labels that begin or end with a hyphen.

Are email lists stored or sent to a server?

Validation is local and this tool does not persist email input or send it in analytics events. Copying writes the selected list to your device clipboard.

Keep browsing