Why "Contact Verified" Doesn't Always Mean What You Think

Bad contact data is expensive. A rep spends an hour building a list, half of it bounces and the campaign's sender reputation takes the hit before a single reply comes back. Nobody disputes that verification matters. What gets less scrutiny is the word itself: "verified" sounds like one consistent standard, and vendors let that assumption stand.

It isn't one standard. It's several, stacked on top of each other, and most verification tools are only doing some of them.

The levels underneath "verified"

Run through what a check can confirm, in order of how much it proves:

• Syntax check. Does the address follow the right format. Catches typos, nothing else.
• Domain and MX record check. Does the domain accept mail at all. Still says nothing about the specific mailbox.
• SMTP handshake. Does that mailbox exist right now. This is the check that confirms deliverability, and it's the one that's easiest to skip at scale because it's slower.
• Catch-all and role-account detection. Is the address a real person's inbox, a domain that accepts everything or a shared inbox like info@ or sales@.
• Batch versus fresh. Was this checked once against a list, or checked again right before the campaign sends. A contact can be valid in January and gone by March.
• Email only versus email plus employment. Does the check confirm the mailbox exists, or does it also confirm the person still works there. These are different questions, and most tools answer only the first one.

A vendor can genuinely run all six and still only publish one accuracy number for the whole stack. That number tells a buyer almost nothing about which of the six they're getting.

A short test for any vendor's claim

Before trusting an accuracy percentage, ask:

1. Is this a live SMTP check, or pattern matching against a database of previously seen addresses?
2. Does it separately flag catch-all domains and role accounts, or fold them into the same "valid" bucket?
3. Is verification run fresh at send-time, or against a cache that could be weeks old?
4. Does the number apply to the whole list, or is it the rate on the subset the tool was confident enough to score at all?
5. Does anything in the product confirm the person is still employed there, not just that the inbox exists?

None of this is a trick question for a vendor to fail. It's the difference between a tool built for high-volume list cleaning and one built for a B2B sales team that needs both a mailbox and a person to still be at that desk.

Running the test on three real tools

Here's what three verification vendors state about themselves, checked live against their own sites.

ZeroBounce claims "99.6% accuracy with real time email validation" and explicitly calls out catch-all handling: "Accurate CATCH-ALL validation included," with the ability to "validate all, including catch-all emails and addresses protected by SEGs." That's a real answer to question 2. Nothing on the page addresses employment status.

NeverBounce positions itself as a "Real-Time Email Verifier and Email List Cleaner" that will "deliver up to 99.9% of your emails with confidence," runs "instant bounce analysis," and offers automated, continuously synced list cleaning through a CRM connection. That's a real answer to question 3, on the automated-sync side. Employment status isn't part of the product.

Kickbox reports a case study result of "98.7% delivery rate," reducing one customer's bounce rate from 13% to 0.7%, and runs real-time checks at the point of signup to "block invalid emails and detect typos." That's a real, sourced number, tied to a specific customer, not a blanket claim. Employment status, again, isn't part of what's being checked.

None of these three is doing anything dishonest. Each is a genuinely capable email-verification tool, and each is answering some of the five questions well. What none of them answers is question 5, because none of them was built to. They check whether a mailbox exists. They weren't built to check whether the person behind it still works there.

Where that gap costs you

A mailbox can be perfectly deliverable and still belong to someone who left the company eight months ago. The email bounces zero percent of the time and still produces zero pipeline, because the message is landing in an inbox nobody with buying authority is reading anymore. Standard email verification will call that contact "valid." It is, technically. It's also useless for the goal, which is reaching a person who can say yes.

This is the specific reason AvairAI's own Contact Verification checks both halves before a campaign launches: email deliverability and current employment status, together. Each contact gets a GREEN, YELLOW or RED classification, so a rep sees exactly which risk they're looking at, not just a single pass or fail. That combination took bounce rates on AvairAI campaigns from roughly 30% down to under 2%. It's also the direct answer to question 5 that pure email-verification tools, by design, don't attempt.

If you're evaluating a vendor right now

Ask the five questions above, in that order, before the accuracy percentage. A vendor with a real, specific answer to each one, broken out rather than folded into a single number, is worth more trust than one that just repeats the headline claim. And if the goal is reaching people, not just inboxes, ask the employment question directly. Most tools will tell you, honestly, that it isn't something they check.

Quick answers

What does "verified" mean for an email address?

It depends on the vendor. At minimum it should mean a live check that the specific mailbox exists, not just that the domain accepts mail. It can also mean catch-all detection, role-account flagging and how recently the check was run. Ask which of these a vendor's number covers.

Is a 99% accuracy claim trustworthy?

It can be, but ask what the 99% is measuring. A high accuracy rate on syntax and domain checks is a different, much weaker claim than a high rate on live SMTP verification of individual mailboxes. The number alone doesn't tell you which one you're getting.

Does email verification confirm someone still works at a company?

No, not by itself. Standard email verification confirms a mailbox is deliverable, not that the person is still employed there. Confirming both requires a separate employment check alongside the email check.