Home › Blog › Build a Cheap Email Verification Waterfall
Build a Cheap Email Verification Waterfall (Without Paying Three Times per Lead)
One verifier is not enough, catch-alls and unknowns prove that weekly, but running every lead through three services triples your cost for nothing. The waterfall fixes both: a cheap bulk verifier first, a catch-all specialist only for the ambiguous remainder, and clear accept/reject rules at each stage. Here is the design we run at 2M leads a month.
Quick Answer: Cheap Bulk First, Specialist for the Remainder, Policy for the Rest
Stage 1: everything through a cheap bulk verifier (MillionVerifier/Reoon class), which settles the easy 65-85%. Stage 2: only unknowns and catch-alls go to a specialist (BounceBan/LeadMagic class). Stage 3: policy, specialist-validated catch-alls send in an isolated segment with a 3% stop rule; residual unknowns get dropped or risk-segmented, never blended. Clean the list before stage 1 so you never buy credits for rows you would delete.
The Design
0 CLEAN 10,000 → ~8,200 (CSV Cleaner: dupes,
roles, disposables, syntax) $0
1 BULK 8,200 @ ~$0.002 ~$16
→ valid 5,400 | invalid 1,100
→ catch-all/unknown 1,700
2 SPECIALIST 1,700 @ ~$0.01 ~$17
→ deliverable 900 | undeliverable 450
→ still-unknown 350
3 POLICY valid + deliverable → campaigns
(catch-alls isolated, 3% stop)
still-unknown → drop, or micro-segment
invalids → master DB as suppressed
Result: ~6,300 sendable, ~$33 total,
vs $80+ single-premium with worse catch-all truth.- •Track each vendor's honesty over time: log predicted status vs actual bounce outcome per campaign. A stage-1 vendor whose "valid" rows bounce above ~1% is misplaced in your waterfall; the data tells you, opinions do not (method in the accuracy shootout).
- •Catch-all policy is the heart of stage 3: the full doctrine, including why unresolved catch-alls never touch the main fleet, is in the catch-all playbook.
- •Verification is perishable: results age with employment churn, so the waterfall reruns on anything older than your reverification window (the decay data), and always at send time, not scrape time.
- •Automate the plumbing: both stages have APIs; an n8n flow moves files between them and merges results, turning the waterfall from a weekly chore into a pipeline your imports just pass through.
Why This Beats Both Extremes
Single-cheap-verifier operations eat the catch-all problem: their "unknown" pile either gets sent (bounces) or discarded (lost pipeline, often a third of enterprise-heavy lists where catch-alls concentrate). Single-premium operations pay top rate for the 70% of rows any service settles identically. The waterfall routes each row to the cheapest service capable of settling it, which is just correct engineering applied to list quality, and the same shape scales from a founder verifying 500 leads in two browser tabs to our automated 2M-a-month pipeline.
Frequently Asked Questions
What is an email verification waterfall?
A staged pipeline where each verification service only sees the leads the previous stage could not settle. Stage 1: a cheap bulk verifier processes everything and confidently settles most rows as valid or invalid. Stage 2: only the unknowns and catch-alls, typically 15-35% of a B2B list, go to a specialist service built for exactly those cases (BounceBan and LeadMagic-style tools). Stage 3 is your policy layer: what to do with rows that remain ambiguous after both. You get near-best-case accuracy at a fraction of running everything through premium services.
Why does one verifier miss things?
Different verifiers use different infrastructure and heuristics: some servers block one vendor's probes but not another's, catch-all domains accept everything at SMTP so standard checks cannot distinguish real from fake mailboxes, and greylisting produces unknowns that a retry from different infrastructure resolves. This is why two services genuinely disagree (our verifier accuracy comparison shows how much) and why the disagreement is concentrated exactly in the rows that cause bounces: the ambiguous ones.
Which service goes first in the waterfall?
Cheapest per credit with solid accuracy on the easy majority: MillionVerifier and Reoon are the community workhorses at fractions of a cent per check. The specialist slot goes to a catch-all resolver (BounceBan, LeadMagic) that costs more per check but only sees the hard slice. Ordering rule: success rate times price, the cheap service must settle enough rows to justify its place, and the expensive one must only ever see what the cheap one could not do. Never put the premium service first; that is the pay-three-times mistake in one step.
What do I do with rows that are still unknown after the waterfall?
Policy, not hope: catch-alls that a specialist marked deliverable get sent, but inside an isolated segment with the stricter 3% bounce stop. Still-unknown rows either get dropped (right call for cheap plentiful data) or risk-segmented at low volume if the account is valuable enough to justify it. What never happens: unknowns blended into the main campaign, because that is how a clean fleet inherits a dirty list's bounce rate.
How much does a waterfall actually save?
Worked example on 10,000 leads: everything through a premium service at ~$0.008 = $80. Waterfall: 10,000 through a bulk verifier at ~$0.002 = $20, then ~25% (2,500 ambiguous) through the specialist at ~$0.01 = $25, total $45 for accuracy the single premium pass cannot match on catch-alls. At our monthly volumes the same math saves thousands while lowering bounce rates, the rare optimization that improves quality and cost together.
Get FREE .com Domains
Prewarmed Inboxes So You Can Send Cold Emails Today
Get Prewarmed & Fresh InboxesPrewarmed & Fresh Inboxes
Google, Microsoft 365 and Azure inboxes with free prewarmed domains and DNS configured before you log in. Prewarmed inboxes send the day they land; every order is delivered within 48 to 72 hours.
Get Prewarmed & Fresh Inboxes