Bulk Email Verification: How to Verify 10,000 Emails Fast
How bulk email verification works under the hood, what to expect from a 10,000-row CSV, and how to read the results without losing valid addresses in the noise.
Bulk email verification turns a list of unknown-quality addresses into a clean, sendable file. Done right, it cuts bounce rates from 20-40% down to under 2%. Done wrong, it strips out the good addresses along with the bad. Here's what to expect from a real bulk run.
How bulk verification actually works
Under the hood, a bulk verifier does five things per address, in this order:
- Syntax check. Drop anything that's not a valid email format.
- MX lookup. Drop anything whose domain has no mail servers.
- Disposable check. Flag known temp providers.
- SMTP handshake. Connect to the recipient server and run an
RCPT TOcommand — without actually sending a message. The server's response tells the verifier whether the mailbox exists. - Catch-all detection. If the server accepts any address (including obvious fakes), flag the original as "risky" rather than valid.
Good bulk verifiers parallelise steps 4-5 heavily — you're effectively running 10-50 simultaneous SMTP sessions against thousands of domains. That's why a 10,000-row CSV typically finishes in 5-20 minutes instead of hours.
What results to expect
For a freshly scraped list, typical breakdown:
| Verdict | % of list | What it means |
|---|---|---|
| Valid | 50-65% | Mailbox confirmed. Safe to send. |
| Invalid | 20-35% | Mailbox doesn't exist. Remove. |
| Risky / catch-all | 5-15% | Can't confirm. Send carefully or rescue. |
| Role | 2-8% | info@, support@, etc. Decide by use case. |
| Disposable | 0-5% | Temp provider. Drop unless free trials are your thing. |
For a list you bought, expect more like 30% valid. For an opt-in list from your own forms, 80%+ valid is normal — anything lower suggests bot signups or honeypot abuse.
Reading the results
Don't just filter to "Valid" and delete the rest. A more nuanced approach:
- Send to Valid immediately. That's the bulk of your reach.
- Rescue Risky with a second-pass verifier. Tools like our Verify Plus catch 20-40% of catch-alls that a single pass marks risky.
- Keep Role for B2B context.
legal@,procurement@,purchasing@are real targets in account-based outreach. - Discard Invalid and Disposable permanently. Don't let them creep back in.
What makes verifiers slow or wrong
Three common failure modes:
- Greylisting. Some servers temporarily defer the first connection from an unknown sender. Cheap verifiers don't retry; good ones retry on a 1-2 minute delay.
- Rate-limiting by major providers. Google and Microsoft throttle SMTP probes. Verifiers that don't rotate IPs hit rate limits quickly, then start returning false "invalid" results.
- Stale results. Some verifiers cache results for months. A "valid" result from 6 months ago means nothing today.
Our bulk verifier handles all three: real-time SMTP (no cached results), rotation across multiple verification providers, and automatic refunds when results don't come back confident. Upload your CSV, get a clean file back — and only pay for addresses we're sure about.
Related posts
MX Lookup Explained: What MX Records Tell You About Email Deliverability
MX records control where email for a domain gets delivered. Learn how to read them, what priority means, and how to diagnose deliverability issues with a free MX lookup.
SPF, DKIM, DMARC: The 3-Record Setup That Stops Your Emails Landing in Spam
Gmail and Outlook now require SPF, DKIM, and DMARC for bulk senders. Here's what each record does, how to set them up, and how to verify they're actually working.
Catch-All Emails: What They Are and How to Verify Them Safely
Catch-all domains accept mail to any address — so SMTP verification can't prove a mailbox exists. Here's why catch-alls are risky, and how to verify them without burning your sender reputation.