Email Validator

Paste a list of addresses and see which ones are malformed and why. Each failure says what is actually wrong — two @ signs, a missing dot in the domain, a space in the middle — rather than just marking it red, because the reason is the part you need to fix the record. Common provider typos get a suggestion: gmial.com, hotmial.com, yaho.com and their relatives are close enough to the real thing to be caught confidently, and the matching is deliberately capped at one edit so your own company domain is not 'corrected' into something else. One thing to be clear about: this checks the shape of an address, not its existence. No browser can verify that someone is behind an address — that needs a mail server, and ultimately a sent message. A green tick here means well-formed.

What gets rejected

InputReason
no-at-signMissing @
a@@b.comMore than one @
user@localhostDomain has no dot
[email protected]Two dots in a row
us [email protected]Space inside the address
[email protected]Domain label starts with a hyphen

When to use it

  1. Clean a mailing list before importing it, catching typos that would bounce.
  2. Check a column of addresses exported from a spreadsheet or a form.
  3. Find the malformed rows in a signup export and see what is wrong with each.
  4. Test the addresses your own validation regex accepts or rejects.
  5. Spot a misspelt provider domain before sending to it.

How to Use

  1. Paste your addresses, one per line or comma-separated.
  2. Read the per-address result and the reason for each failure.
  3. Copy the full report with the copy button.

Features

  1. Bulk check, one address per line
  2. A specific reason for every failure
  3. Typo suggestions for common providers
  4. Valid count at a glance
  5. Accepts newline, comma or semicolon separators
  6. 100% client-side — nothing uploaded

FAQs

Is my list uploaded anywhere?

No. Every address is checked in your browser and nothing is transmitted. That is the reason to use this rather than a service that asks you to paste a customer list into a server.

Does a valid result mean the address exists?

No, and no tool that runs in a browser can tell you that. Checking existence needs a DNS MX lookup and a conversation with the receiving mail server, which a web page cannot make. Valid here means the address is correctly formed. Only sending mail proves delivery.

Why was my unusual but legal address rejected?

The full RFC 5322 grammar allows quoted local parts with spaces, comments in parentheses and bracketed IP literals. Almost no mail provider accepts them and almost no signup form allows them, so they are rejected here too. If you have a genuinely exotic address that a provider accepts, this will be a false negative.

How are typo suggestions chosen?

The domain is compared against the providers that make up the bulk of real addresses, using edit distance with a tight cap — one edit for short domains. That catches gmial and gmai1 while leaving an unrelated company domain alone. An uncapped comparison would confidently suggest nonsense.

What separators can I use?

New lines, commas or semicolons, so a pasted column from a spreadsheet and a pasted To: field both work. Surrounding spaces are trimmed.

Technical Details

The honest version of email validation is that the full grammar in RFC 5322 permits things nobody wants to accept — quoted local parts containing spaces, nested comments, bare IP literals in brackets — and the regexes that claim to implement it are thousands of characters long and still wrong. So this does not try. It checks the rules that actually catch mistakes: exactly one @ sign, a local part that is present and no longer than 64 characters, a domain that is present, no longer than 255, has at least one dot, no label that is empty or starts or ends with a hyphen, and a final label that looks like a TLD rather than a number. Leading and trailing whitespace is trimmed rather than rejected, because it is a paste artefact, not the user's intent. Internal whitespace is rejected, because it never is. Consecutive dots are rejected in both halves. Beyond syntax, a typo check compares the domain against the twenty or so providers that make up most real addresses using a Levenshtein distance capped at one edit for short domains, which is what turns gmial.com into a suggestion of gmail.com without also suggesting gmail.com for someone's legitimate company domain. The cap matters: uncapped nearest-neighbour matching produces confident nonsense. What no browser can do is check whether an address exists — that needs an MX lookup and, really, a sent message, neither of which is available from a page. A valid result here means the address is well-formed, not that anyone is behind it.

Developer Tools

Developer Tools

  • User Agent Parser
  • Chmod Calculator
  • HTML to Markdown
  • Markdown Table Generator
  • JavaScript Beautifier
  • GraphQL Formatter
  • Prettier Playground
  • XML Formatter