Email Validator
Check email address syntax in bulk, with warnings for role accounts and likely domain typos.
4 valid · 2 invalid · 6 checked
| Address | Local | Domain | Notes | |
|---|---|---|---|---|
| user@example.com | user | example.com | ||
| first.last+tag@sub.example.co.uk | first.last+tag | sub.example.co.uk | ||
| admin@example.com | admin | example.com | This is a role account rather than a personal mailbox. | |
| me@gmial.com | me | gmial.com | Did you mean me@gmail.com? | |
| not-an-email | not-an-email | — | Not a valid email address format. | |
| user@example | user | example | Not a valid email address format. |
- This checks syntax. Only sending a message proves an address actually receives mail.
- The pattern is deliberately pragmatic rather than fully RFC 5322-compliant — the complete grammar allows addresses no real mail provider accepts, and stricter patterns reject valid ones.
- Role accounts like
admin@andinfo@are flagged because they often should not receive marketing mail. - Everything runs locally, so a customer list can be checked without it leaving your machine.
Your Data Never Leaves Your Device
Every tool runs entirely in your browser. Nothing you type is uploaded, stored, or logged on our servers.
The Email Validator checks a list of addresses one per line and reports which are syntactically valid, splitting each into its local part and domain. Beyond pass or fail it flags two things worth knowing about: role accounts such as admin@ and info@, which belong to a function rather than a person and often should not receive marketing mail, and likely domain typos like gmial.com or a top-level domain ending in .con.
The pattern is deliberately pragmatic rather than fully RFC 5322-compliant. The complete grammar permits quoted strings, comments, and IP-literal domains that essentially no mail provider accepts, while the strictest regexes found in the wild reject perfectly ordinary addresses — plus-addressing being the usual casualty. What this cannot do is confirm delivery: only an MX lookup and a real send prove a mailbox exists. Since everything runs locally, a real customer list can be checked without it leaving your machine.
FAQ
No. It validates syntax only. Confirming deliverability needs an MX lookup and ultimately a real send — no client-side tool can tell you whether a mailbox exists.
Deliberately. The full grammar permits quoted strings, comments, and IP-literal domains that essentially no mail provider accepts, and the strictest regexes reject perfectly ordinary addresses. This matches what providers accept in practice.
Yes. Addresses like user+tag@example.com are valid and widely used for filtering. Any system rejecting them is wrong, and this validator accepts them.
A shared mailbox like admin@, info@, or support@ that belongs to a function rather than a person. They are flagged because sending marketing mail to them tends to generate complaints and hurt sender reputation.
Common misspellings of major providers — gmial.com, yaho.com, outlok.com — are matched against a list, and top-level domains ending .con or .cmo are flagged as likely .com typos.
Yes. Paste one address per line and each is checked separately, with a count of valid and invalid, and a button to copy just the valid ones. Nothing leaves your browser, so a real customer list is safe to check.