Skip to content

Email Verification False Positives: Why They Happen

Why email verification false positives and false negatives happen, from catch-all servers to greylisting, and how to handle risky results.

Abedrahim B Nov 15, 2026 5 min read 1,239 words
Email Verification False Positives: Why They Happen

Email verification false positives are results that get a mailbox wrong. Sometimes a verifier says an address is valid, and it later bounces. Sometimes it says an address is invalid, and the person was real all along. No tool can be right every time, because a verifier works by asking a mail server, and the server does not always tell the truth. This guide explains why these mistakes happen, how to spot them and how to protect your sending when a result is uncertain.

Email verification false positives explained
Email verification false positives explained

TL;DR#

  • A verifier asks the mail server about a mailbox. Some servers give vague or false answers.
  • The main causes are catch-all domains, greylisting, rate limits and blocked checks.
  • Treat "risky", "unknown" and "accept-all" as separate groups, not as valid.
  • Send small batches to uncertain addresses and watch the bounces.

What does a false positive mean here?#

The term has two sides, and people use it in both ways.

  • A false "valid". The tool says the address is good, but the mail bounces. This hurts your sender reputation.
  • A false "invalid". The tool says the address is bad, but the mailbox exists. This loses you a real lead.

Both cases come from the same limit. A verifier cannot see inside the mail server. It can only read the replies that the server chooses to give.

How email verification works#

A typical check runs in steps:

  1. Syntax check. Is the address written in a valid format?
  2. Domain check. Does the domain exist, and does it have mail servers (MX records)?
  3. Mailbox check. The tool opens an SMTP conversation with the server and asks whether it would accept mail for that address, without sending a message.
  4. Extra signals. The tool may check for disposable domains, role addresses and known risky patterns.

The SMTP rules are set out in RFC 5321. Servers are free to answer in different ways, and many do. That is where the errors come from.

Why email verification false positives happen#

Catch-all (accept-all) domains#

Some servers accept mail for any address at the domain, real or not. The check gets a "yes" for every name. The tool cannot tell a real mailbox from an invented one. It may mark the address as "accept-all" or, if the tool is weak, as valid.

Mail to a fake address on such a domain may be accepted first and bounced later. Learn more in our guide to catch-all email verification, and use a catch-all verifier when you need a deeper look.

Greylisting#

Some servers reject the first attempt from an unknown sender, then accept a retry after a delay. A check that does not retry may read the first refusal as "invalid". See how it works in our post on email greylisting.

Rate limits and blocked checks#

Large mail providers and security gateways limit how many checks they allow from one source. Some block them entirely. The tool may time out or get a generic refusal. A weak tool may then mark a real address as invalid.

Security gateways#

Many firms route mail through a filter before it reaches the real mail server. The filter answers the check, not the mailbox. It may say "yes" to everything, or "no" to everything, whatever the real state is.

Stale data#

A mailbox can be valid at the time of the check, and gone a week later, because the person left the company. The result was right when it ran, but the data aged. This is why lists should be re-verified before each major campaign.

Mailbox full or temporary issues#

A full mailbox or a server fault can look like a bad address on one check and a good one on the next.

How to spot email verification false positives#

Look for these signs:

  • A whole domain returns "valid" for every address, including obvious fakes. That points to a catch-all setup.
  • The same address changes result between two runs.
  • A tool returns many "unknown" results for one company.
  • Bounces come in from addresses the tool rated as safe.

Test a verifier with a few made-up addresses on a domain you know. A reliable tool should flag a catch-all domain instead of calling the fake address valid.

What to do with each result type#

Result What it usually means Suggested action
Valid The server accepted the mailbox Send
Invalid The server said the mailbox does not exist Remove
Accept-all The domain accepts everything Send in small batches, watch bounces
Unknown The check was blocked or timed out Retry later, or use another source
Risky or role-based The address may be shared or low quality Review by hand

Do not merge the middle groups into "valid". Keep them apart so that you can handle each one on purpose.

How to reduce the damage from email verification false positives#

  1. Keep a separate list for uncertain addresses. Send to it in small batches.
  2. Watch bounces and complaints. Stop sending to any domain that bounces often.
  3. Use more than one signal. Combine verification with other evidence, such as a public source for the address.
  4. Re-verify before big sends. Do not rely on a check that is months old.
  5. Retry "unknown" results. A second pass may clear a temporary block.
  6. Keep bounce rates low. Providers watch them closely. Review the sender rules from the mailbox providers you send to.

To run these checks, use the Tomba Email Verifier for single addresses, and the bulk tools for lists. The free email checker is useful for a quick look.

Choosing a verifier you can trust#

When you compare tools, ask these questions:

  • Does it separate valid, invalid, accept-all and unknown results?
  • Does it retry for greylisting?
  • Does it flag disposable and role-based addresses?
  • Does it show how fresh the result is?
  • Can you test it with your own sample list?

Run a sample of your own list through two tools and compare the results to your real bounces. Your own data is a better test than any claim on a website.

Common mistakes with email verification false positives#

  • Treating accept-all as valid. It is a risk group, not a pass.
  • Deleting every "unknown". Some are real people.
  • Verifying once and never again. Data decays.
  • Ignoring bounce data. Your own bounces show what the tool missed.

FAQ#

Are email verification false positives common?#

They happen, mostly on catch-all, greylisted and filtered domains. The share varies by list and by tool, so measure it on your own data.

Can any tool give 100 percent accuracy?#

No. A verifier relies on what the mail server says, and servers can be vague or wrong.

What is the difference between a false positive and a false negative?#

A false positive marks a bad address as good. A false negative marks a good address as bad. People often use "false positive" for both.

Should I send to accept-all addresses?#

You can, with care. Send small batches, watch the bounces and stop if they rise.

Final thoughts#

Email verification false positives come from the way mail servers answer, not only from the tool. Learn the causes of email verification false positives, keep uncertain results in their own group and test in small batches. Re-check data often and use your bounce rate as the final judge. To verify addresses before you send, try the Tomba Email Verifier.

// start free

See who Tomba finds at any company

Type a company's domain to see its people, their roles and verified work emails, each with the pages it was found on. Free account, no card.

Free plan · No credit card required · GDPR & CCPA

Share
0 clapsEnjoyed it? Give a clap.
Abedrahim B

// about the author

Abedrahim B

CEO

Was this helpful?