Paste or pick your regex
Type a regex pattern into the input, or pick one of the built-in presets (Simple, Standard, HTML5, RFC 5322) to load a known-good pattern.
An email regex validator is a tool that tests a regular expression against a list of email addresses and shows which ones pass and which fail. Paste your regex, drop in some test emails, and get instant results - no signup, no upload.
Built for developers writing form validation, signup flows, or data cleaning scripts. Pick a pre-built pattern (Simple, Standard, HTML5, or full RFC 5322), tweak it, and watch the matches update live.
Load a known-good pattern, or write your own below.
HTML5 input pattern: The exact pattern the WHATWG HTML5 spec uses for <input type="email">. Pragmatic, not strict RFC 5322 - it permits most real addresses, enforces label length limits, and rejects leading/trailing hyphens in domain labels.
JavaScript-flavored regex. Slashes are added automatically.
Regex compiled successfully
One per line. Whitespace-only lines are ignored.
Live as you type. No data leaves your browser.
| Result | |
|---|---|
| simple@example.com | Pass |
| first.last@example.com | Pass |
| user+tag@gmail.com | Pass |
| user.name+filter@sub.example.co.uk | Pass |
| "quoted local"@example.com | Fail |
| admin@mail-server.io | Pass |
| support@xn--bcher-kva.example | Pass |
| hello@localhost | Pass |
| user@[192.168.1.1] | Fail |
| user@[IPv6:2001:db8::1] | Fail |
| 名字@example.com | Fail |
| plainaddress | Fail |
| @no-local.com | Fail |
| no-at-sign.com | Fail |
| double..dot@example.com | Pass |
| trailing.dot.@example.com | Pass |
| .leading.dot@example.com | Pass |
| spaces in@example.com | Fail |
| user@no_underscores_in_domain.com | Fail |
| user@-leadinghyphen.com | Fail |
| user@trailinghyphen-.com | Fail |
| user@example.c | Pass |
| user@example | Pass |
| user@example.com | Pass |
| user @example.com | Fail |
Type a regex pattern into the input, or pick one of the built-in presets (Simple, Standard, HTML5, RFC 5322) to load a known-good pattern.
Paste one email address per line into the test inputs textarea. The default sample includes valid, invalid, and tricky edge cases.
Each address is matched against your regex live. Read the pass/fail badges and the summary to see which addresses your pattern accepts and which it rejects.
An email regex validator is a tool that tests a regular expression against a list of email addresses and reports which addresses match and which do not. It is used to verify that an email validation pattern accepts the addresses it should and rejects the ones it should not before shipping the regex into a form, API, or database constraint.
There is no single best regex - it depends on how strict you need to be. For most web forms, the HTML5 input pattern is the right balance: it accepts virtually every real-world address and matches the behavior of <input type="email"> in modern browsers. Use the simple pattern for quick sanity checks, and only reach for full RFC 5322 if you actually need to accept quoted local parts and IP-literal domains.
No. The HTML5 spec deliberately uses a willful violation of RFC 5322 to keep the pattern short and pragmatic. It rejects valid but exotic addresses like quoted local parts ("foo bar"@example.com) and IP-literal domains (user@[192.168.1.1]), but in exchange it matches what users and developers actually expect.
Plain ASCII regex patterns will reject internationalized email addresses like 名字@example.com or user@münchen.de. To accept them, you need a Unicode-aware pattern using \p{L} character classes with the u flag, or you can validate the punycode form (xn--...) of the domain. Most production systems normalize to punycode before validation.
No. Regex can only confirm that an address looks syntactically plausible - it cannot tell you the domain exists, the mailbox is real, or that mail will be delivered. For real validation, combine a permissive regex with an MX record lookup and, where appropriate, an SMTP check or a confirmation email.
Trace the delivery path of any email, inspect SPF/DKIM/DMARC results, and find hop-by-hop delays.
Paste an email list and remove duplicates instantly. Normalizes case, whitespace, and Gmail aliases.
Validate your SPF record for syntax errors, DNS lookup limits, deprecated mechanisms, and best practices.
Get an instant A+ to F letter grade for your domain's SPF, DKIM, DMARC, BIMI, MX, and TLS-RPT setup.
MailParse turns inbound MIME emails into structured JSON and delivers it via webhook or REST polling - skip the parser, ship the feature.