Email Address Validator
Check a list of email addresses for syntax errors, length limits, consecutive dots, typo'd free-mail domains, plus addressing and role accounts.
Free · No sign-up · Your inputs stay in your browser
Input
Validate email addresses
Output
6 of 8 valid
| Address | Verdict | Notes |
|---|---|---|
| [email protected] | valid | - |
| [email protected] | valid, check | plus-addressed: delivered to [email protected] at most providers |
| [email protected] | valid, check | did you mean @gmail.com? |
| "john doe"@example.org | valid, check | quoted local part: valid, but many sites reject it |
| [email protected] | invalid | dot at the start or end, or two in a row |
| [email protected] | valid, check | role address, often shared or unmonitored |
| [email protected] | valid | - |
| bad@domain | invalid | domain has no dot |
Checks the syntax the RFCs allow plus the things that matter in practice: lengths, dots, typo'd free-mail domains, plus addressing and role accounts. Syntax cannot tell you an address exists; the only real test is sending a confirmation link, which is also what consent records need. In Laravel, the email:rfc,dns rule adds an MX lookup.
Runs in this browser. Nothing you paste is sent to a server.
About this tool
Method, assumptions, practical next steps, and limits.
What syntax cannot tell you
A syntactically valid address may not exist, may belong to someone else or may accept everything. The only reliable test is sending a confirmation link, which is also the record a mailing list needs that the person agreed. Laravel's email:rfc,dns rule adds an MX lookup; the RFC 5321 size limits are the source of the length rules.
Don't over-validate
Rejecting a plus sign, a long top-level domain such as .technology or an apostrophe in a name locks out real users. Prefer a permissive check and a confirmation email.