Free tool · 01 / FIND
Email list cleaner.Duplicates, typos and dead domains out, no signup.
Removes duplicates and bad addresses, fixes typos, and flags role and personal emails.
Runs in your browser. Nothing you type is sent to us.
7 of 10 kept. Removed 1 duplicate, 2 invalid. Flagged: fixed 2 typos, 1 role address, 1 personal.
| You pasted | Result | Why | Note |
|---|---|---|---|
| PRIYA@northwind.example | removed | duplicate | Same as entry 1. |
| info@acme.example | info@acme.example | role | |
| sam.lee@gmial.com | sam.lee@gmail.com | fixed, personal | Fixed gmial.com to gmail.com. |
| jo@example.con | jo@example.com | fixed | Fixed example.con to example.com. |
| alex@@acme.example | removed | invalid | More than one @. |
| not-an-email | removed | invalid | Not an email address. |
An example: a made-up list. The cleaning runs in your browser; the domain check sends domains only to our server, which doesn't keep them.
A clean list is half the job. Valley finds the right people, researches each one and writes to them. See how Valley does it ↗
NEXT STEP
Fed up with lists that bounce.Valley finds, researches and writes to them.
Book a demo ↗$500 a month for your first seat, $200 for each seat after that.
The rules
What does an email list cleaner remove?Each check, and the rule it rests on.
It removes duplicates and addresses that can't be valid: a part before the @ over 64 characters, a domain over 255, an address over 254, or characters an address can't have. It fixes common typos, flags role and personal addresses, and can drop domains that take no mail.
| Check | Example | What happens | Rule |
|---|---|---|---|
| Duplicates | PRIYA@acme.com and priya@acme.com | Removed; the first is kept | Matched ignoring case. RFC 5321 lets servers treat Smith and smith as different users, but discourages relying on it. |
| Invalid syntax | alex@@acme.com | Removed | One @, and only the characters an address may have unquoted |
| Too long | 65 characters before the @ | Removed | 64 before the @ and 255 after (RFC 5321), 254 in all (RFC 3696 erratum 1690) |
| Typos | gmial.com, acme.con | Fixed, or flagged | Our list; .con, .cmo and .comm aren't top-level domains (IANA) |
| Role addresses | info@, sales@, support@ | Flagged, or removed | RFC 2142's 15 names, plus shared inboxes on our own list |
| Personal addresses | gmail.com, outlook.com | Flagged, or removed | Our list of personal providers |
| Domains that take no mail | A domain that doesn't exist, or a null MX | Removed, after the optional check | MX, then the address record as an implicit MX (RFC 5321 §5.1); null MX (RFC 7505) |
From RFC 5321: Simple Mail Transfer Protocol ↗ · RFC 3696 erratum 1690 (verified): the 254-character address limit ↗ · RFC 2142: Mailbox Names for Common Services, Roles and Functions ↗ · RFC 7505: A "Null MX" No Service Resource Record ↗ · IANA: list of top-level domains (version 2026111900) ↗, read 19 Nov 2026
How it works
How this tool works.And what it can't see.
Paste up to 20,000 lines in any shape: one address per line, several separated by commas or semicolons, or Name <email>. Lines with no address are listed as invalid. The cleaning runs in your browser.
Each address is checked against RFC 5321's limits and characters, typos are fixed (you can switch that off), duplicates are removed ignoring case, and role and personal addresses are flagged; tick a box to remove them instead. The table lists every change and why.
The optional check sends each domain, never an address, to our server, which asks DNS whether it has mail servers: an MX record, or an address record that RFC 5321 treats as an implicit MX. Domains that don't exist or publish RFC 7505's null MX can't take mail and are removed. Up to 300 domains a run; nothing is kept. It never contacts a mailbox, so it can't tell you whether a person's inbox exists.
Built by Valley.
Sources
- RFC 5321: Simple Mail Transfer Protocol ↗read 19 Nov 2026
- RFC 3696 erratum 1690 (verified): the 254-character address limit ↗read 19 Nov 2026
- RFC 2142: Mailbox Names for Common Services, Roles and Functions ↗read 19 Nov 2026
- RFC 7505: A "Null MX" No Service Resource Record ↗read 19 Nov 2026
- IANA: list of top-level domains (version 2026111900) ↗read 19 Nov 2026
List hygiene
Send only to addresses that can arrive.A clean list before every campaign.
Every address that can't receive mail is a bounce. Most of them can be caught before you send, without paying per address.
- 01
What can be checked without sending
The format and the domain. RFC 5321 caps the part before the @ at 64 octets and the domain at 255, and RFC 3696's verified erratum puts the useful limit for a whole address at 254 characters. A domain can receive mail if it has an MX record, or, with none, an address record, which RFC 5321 treats as an implicit MX. A domain that publishes RFC 7505's null MX is saying it accepts no mail at all.
From RFC 5321: Simple Mail Transfer Protocol ↗ · RFC 3696 erratum 1690 (verified): the 254-character address limit ↗ · RFC 7505: A "Null MX" No Service Resource Record ↗, read 19 Nov 2026
- 02
Role addresses
RFC 2142 names mailboxes for roles rather than people, from info, marketing, sales and support to abuse, postmaster and webmaster, and says they must be recognised whatever their case. They reach a team or a ticket queue, not a person, so in outreach they're usually worth flagging.
From RFC 2142: Mailbox Names for Common Services, Roles and Functions ↗, read 19 Nov 2026
- 03
What it can't tell you
Whether a particular mailbox exists. That takes contacting the mail server, which this tool never does. A clean format and a domain that takes mail mean the address can arrive, not that someone reads it.
A clean list gets delivered. Who's on it decides whether anyone replies. See how Valley does it ↗
From RFC 5321: Simple Mail Transfer Protocol ↗, read 19 Nov 2026
Questions
Questions people ask.
- How do I clean an email list for free?
- Paste it here. Duplicates and invalid addresses are removed, typos fixed, and role and personal addresses flagged, in your browser. An optional check confirms each domain takes mail.
- How do I remove duplicate emails from a list?
- Paste the list; duplicates are removed ignoring case, keeping the first. RFC 5321 discourages relying on case differences in addresses.
- What is a role-based email address?
- A mailbox for a role, not a person, such as info@, sales@ or support@. RFC 2142 defines 15 of these names.
- How long can an email address be?
- 254 characters in all, with at most 64 before the @ and 255 after, per RFC 5321 and RFC 3696's verified erratum.
- Does this verify that an email address exists?
- No. It checks the format and whether the domain can take mail. It never contacts a mailbox, so it can't confirm a person's inbox exists.
- What is a null MX record?
- A single MX record pointing to "." with preference 0, defined in RFC 7505, meaning the domain accepts no email.
- Is my list uploaded anywhere?
- No. The cleaning runs in your browser. The optional domain check sends domains only, never addresses, and our server doesn't keep them.
Keep going
Try one of these next.
- Compare two listsData and prospectingFinds what's in both lists, only in one, or duplicated, by line, email or company domain.Open the tool
- Email extractorData and prospectingPulls every email address out of pasted text, drops duplicates and flags the risky ones.Open the tool
- MX lookupEmail outreachShows a domain's MX records and who handles its email, for one domain or 500 at once.Open the tool
- Email permutatorData and prospectingLists every likely work email for a name and company, and checks the domain takes mail.Open the tool
- Buying committee mapData and prospectingMaps who's in a B2B deal for what you sell, with titles and a LinkedIn search per role.Open the tool