Guide

Why “verified” email finders often aren’t

Domain-level checks and mailbox-level checks get marketed identically. They aren't the same thing.

Plenty of tools verify that a domain exists and accepts mail, then label the whole result “verified” — when only the naming pattern was ever actually checked, not the specific mailbox. A domain accepting mail says nothing about whether jane.doe@company.com specifically exists there. See how real verification works for the distinction.

Catch-all domains make the gap obvious

A catch-all domain accepts every address sent to it, real or not — so a tool that only confirms the domain accepts mail will confidently hand you a result for a mailbox that may not exist at all. The honest response, once a domain is detected as catch-all, is to flag it as unconfirmed and hand back the best pattern guess with its confidence stated — not to present a guess as a hit. That flagging step is more work than just returning a plausible-looking address, which is exactly why some tools skip it. The mechanism is written out in catch-all emails explained.

What to actually check before trusting a “verified” badge

Ask what specifically was confirmed: an SMTP handshake against the individual mailbox, or just that the domain has a working mail server. Ask what happens on catch-all domains — a tool that never mentions catch-alls at all is a signal it doesn’t distinguish them from a real hit. And ask whether a miss costs you anything: if every result is billed the same whether or not it was actually confirmed, there’s no incentive built into the pricing to tell the difference.

A test you can run this afternoon

Pick a vendor that says "verified." Ask their tool (or their support) to check a local-part that cannot be a person at a domain you know receives mail — something like zzzzz@company.com on a company that is not a catch-all.

If they return invalid / not found, they are at least attempting mailbox-level checks.
If they return verified or a high confidence, they checked the domain (or they hit a catch-all and did not say so).
If they have no way to answer, they do not distinguish.

Then run the same pair through our verifier. We will tell you catch-all vs not found vs verified. Catch-all is free. Not found is free.

Do not use a real employee's name as the "impossible" local-part. Use nonsense. Jane Doe examples on this site are fictional.

Why the marketing lands this way

"Verified" is a short word that buyers already want. Domain checks are cheap — one DNS lookup. Mailbox checks cost connections, handle greylisting, and produce unsatisfying answers (catch-all). A vendor that bills every row has a financial reason to print a green badge.

Our billing does the opposite: you pay for a confirmed mailbox. Lying about catch-alls would cost us support tickets and would not make us more money. Pricing is public.

Confidence scores

A 94 on a catch-all domain is a pattern match. Pattern matches are useful as hypotheses. They are not SMTP. If a UI cannot show you catch-all as a first-class status, the score is doing the hiding.

Chrome extensions

LinkedIn overlays that stamp "verified" on a profile almost never disclose the check. Many are domain-level or waterfall caches. If you cannot export a status of catch-all, assume you do not have one.

What we will not claim

We will not quote a made-up accuracy percentage against Hunter, Apollo, or anyone else. Coverage and accuracy need a labelled corpus. Until we publish original research with a sample size we can defend, compare vendors on what they check, what they charge for, and whether credits expire — see the comparison.

See the difference on a real domain

If it comes back verified, the mail server accepted the mailbox. Catch-all is labelled catch-all, and you are not charged for it.

Try it — no account needed

Real lookup against the live mail server — not a sample.