How we compile these comparisons

Where the facts come from

Only from the company’s own published pages — their pricing page, their docs, their GDPR or privacy page. We do not use review sites, comparison directories, or aggregator listings, because those go stale silently and we cannot show you where the number came from.

Every cell in every table carries a link to the exact page we read and the date we read it. If you click through and see something different, the vendor changed it and we want to know.

What we compare, decided before we look

The fields are fixed in advance and identical for every service, so we cannot pick the measurements that happen to flatter us:

• How they sell it
• Smallest published tier
• Published price at 100,000
• Free credits
• Do credits expire?
• Published accuracy rate
• API
• Published data location

We include our own service in every table, on the same fields, from our own published pages. Where we do not publish something either, our row says so.

We never put two different measurements in one row

Some services publish an accuracy rate. Others publish a deliverability guarantee. Those sound similar and measure different things, so lining them up in a single “accuracy” column would be a misleading comparison built entirely out of true quotes. When services publish different measurements, they get different rows.

When we could not confirm something

We leave it blank and say which kind of blank it is, because those are very different situations and lumping them together would be unfair to the vendor:

• “Not found in the pages we reviewed” — we looked and did not see it. That does not mean the service lacks the feature or hides it; it may well be published somewhere we did not check.
• “Their page could not be read” — the page blocked us or rendered nothing readable. A technical failure on our side, not a judgement on theirs.
• “The page we cited is no longer available” — the source moved or was removed since we recorded it.

What we never do is fill the gap with an estimate, a figure from a review site, or a number we half-remember.

Prices go stale, so we expire them

We re-check every source link weekly and re-read pricing monthly. If a price has not been successfully re-verified in 45days, we stop showing it and tell you to check their page instead. Slower-moving facts — whether an API exists, what a GDPR page says — hold for 180 days. A promotional price is never shown as if it were the standing rate.

Which comparisons we publish

Holding the data for a comparison is not a reason to publish it. A page only goes up when people search for that specific comparison, when the services genuinely differ on several of the fixed fields, and when we verified enough of those fields for the table to be worth your time. Comparisons that stop earning their place come down.

We also drop services we cannot source. Kickbox isabsent from every table here for exactly that reason — not because of anything about the product.

Fairness and independence

Email List Validation is not affiliated with, endorsed by, or partnered with any of the companies named in these comparisons. We use their names only to identify their services. We publish their real strengths alongside ours, we do not run comparative benchmarks of our own and therefore never publish any, and we do not characterise anyone’s product as worse than ours — we show what each company publishes and let you decide.

Corrections

If you work at one of these companies, or you are a reader who spotted something out of date, tell us and we will correct it and re-date the page. We currently track 8 services; facts were last compiled on 2026-08-29.

Currently sourced: ZeroBounce, NeverBounce, Bouncer, Emailable, MillionVerifier, Clearout, DeBounce, Email List Validation.