Account

What new tool do you want?

Web & SEO

Email List Cleaner & Validator

Clean an email list in seconds — remove duplicates and invalid addresses, fix typos like gmial.com, and optionally drop role (info@, noreply@) and disposable addresses. Paste any list; nothing is uploaded.

How to use

  1. 1Paste your list — one per line, comma-separated, or copied from a CSV or email client.
  2. 2Pick the cleanups you want.
  3. 3Copy or download the clean list — switch on “List removed addresses” to see what was dropped and why.

How it's calculated

Each address is checked against RFC 5322-style syntax (local part ≤ 64 characters, total ≤ 254, a real-looking domain and TLD). Duplicates are matched case-insensitively.

Frequently asked questions

Does it check that the mailbox exists?

No — that needs a live SMTP/MX check from a server. This tool catches the problems you can find offline: bad syntax, typos, duplicates, role and throwaway addresses. That alone usually removes most bounces.

Why remove role addresses?

Addresses like info@ or support@ are shared inboxes; they often don't opt in personally, get lower engagement, and some email platforms flag them.

Is my list private?

Yes. Everything runs in your browser — the list is never sent anywhere.

Why deduplication has to happen after case normalization, not before

[email protected] and [email protected] are the same mailbox to any mail server, but they're different strings until something normalizes the case — which is why the cleaner lowercases each address for its internal duplicate-matching key regardless of whether the 'Lowercase' output toggle is on, so a list mixing cases still gets correctly deduplicated even if you want to preserve original capitalization in the final output. Without that separate internal normalization, a list with inconsistent capitalization would pass straight through with duplicates intact.

Worked example: Email List Cleaner & Validator

A list of four lines — [email protected], [email protected] repeated on a comma-separated line with [email protected] and a bracketed [email protected], then not-an-email, then [email protected] — with every cleanup option on produces exactly two surviving addresses: [email protected] (the duplicate removed, case normalized) and [email protected] (the gmial.com typo corrected to gmail.com). The removed section lists all three rejections with their specific reason: [email protected] as disposable, not-an-email as invalid syntax, and [email protected] as a role address — not just a single 'invalid' bucket, which matters for understanding why your list shrank.

Why typo correction only catches domains, not usernames

The typo dictionary maps misspelled domains like gmial.com and hotmial.com to their correct versions, fixing a specific, extremely common class of data-entry error (adjacent-key typos typed quickly) — but it makes no attempt to guess at or correct typos in the username portion before the @ sign, since there's no reference list of 'correct' usernames to check against the way there is for a small set of major mailbox providers. A mistyped username still passes through unless it happens to also fail basic syntax validation.

What a clean list doesn't guarantee about deliverability

Passing every check here — valid syntax, no duplicates, no obvious typos, not a role or disposable address — still doesn't confirm the mailbox actually exists and accepts mail, since that requires a live SMTP or MX-record check against a real mail server, something that can only happen server-side, not in a browser. What this cleaning step does accomplish is removing the problems that are knowable without contacting any server at all, which in practice eliminates a large share of eventual bounces before you ever send.

Related tools

More: Web & SEO