Why Two Email Verifiers Give Different Results on the Same List, and Which to Trust
Two email verifiers disagree on the same list because they handle the hard cases differently: catch-all domains, servers that defer or refuse the check, and addresses that could not be confirmed. Neither tool is lying. They are making different calls on rows where the mail server did not give a clear answer.
The six reasons
| Reason | What differs |
|---|---|
| Unconfirmed addresses | One tool labels them valid, another risky or unknown |
| Catch-all domains | Valid, risky or its own category; see what is a catch-all domain |
| Deferred or refused checks | Some retry, some give up, some count a deferral as a pass |
| Timing | A mailbox can be created or closed between two runs; see how often to verify |
| Checking server's reputation | Some servers refuse a source they do not know, and each tool checks from its own addresses |
| Disposable and role lists | Each tool keeps its own lists |
The first line is the one that moves the headline number most.
What SimpleVerifier does
SimpleVerifier's rule is that anything the mailbox probe could not confirm is returned as risky, never as valid. Each row carries a status (valid, risky or invalid), a send advice and a reason. The columns are explained in how to read a verification report, and server would not confirm covers the retry group.
A tool that follows the opposite rule shows a larger valid count. That count is not wrong on the day, but it is the one that turns into bounces.
A bigger valid count is not a better result
If one tool says 9,000 of 10,000 are valid and another says 7,500, the first may simply have put 1,500 unconfirmed rows in the valid pile. What matters is how many of the valid group bounce.
How to settle it
- Run the same sample through both. Bench test email verifiers fairly gives a protocol.
- List the rows where they disagree.
- Take 100 to 200 addresses each tool called valid, from the rows where they differ if you can.
- Send from a warmed inbox, not your main domain.
- Count hard bounces after a couple of days. Calculate your email bounce rate shows how to read it.
The tool with fewer bounces in its valid group made the better call for your list.
What to do with the disagreeing rows
Treat a row as risky if either tool does. Send the rows both call valid first, and put the rest in a small second batch.
Next step
Run 100 free checks on a sample you have already run elsewhere, with a Google sign-in and no card, and compare the rows. See pricing: Starter is $9 a month for 2,500 emails, one-time packs start at $15 for 10,000 checks, and Pro is $39 a month.
Common questions
Why do two email verifiers give different results on the same list?
They handle the hard cases differently. Catch-all domains, servers that defer or refuse the check, and addresses they cannot confirm are labelled differently, and each tool runs the check from its own servers at its own time.
Which verifier is right?
The one whose valid group bounces least when you send. Take 100 to 200 addresses that each tool called valid, send from a warmed inbox and count hard bounces.
What does SimpleVerifier do with addresses it cannot confirm?
It returns them as risky with a reason, such as accepts all addresses or server would not confirm. It does not return them as valid.
Is a higher valid count better?
Not by itself. A tool that calls unconfirmed addresses valid shows a bigger valid count and a higher bounce rate when you send.
Should I run my list through both?
To compare, yes, on a sample. For production, pick one and keep it, so that results are comparable from month to month.
Check your list before you send
Real mailbox checks over SMTP, and nothing is sent to the address. Sign in with Google and your first 100 email checks are free, no card. Plans for bigger lists are on the pricing page.