Email Verification Before Sending: Checks, Bounce Rate, Limits

Email verification checks whether an address can receive mail before you send. The cheap checks are syntax, MX lookup and disposable or role-address lists; the harder ones are catch-all detection and an SMTP probe. Run it to keep bounces near 2%, because repeated hard bounces damage sender reputation.

Why bounces hurt more than they seem

Every hard bounce tells a mailbox provider that you send to addresses you have not checked. A few are normal. A steady stream looks like a purchased or scraped list, and that is a strong spam signal. Bounces also give you no revenue and cost you sending capacity.

BusinessMCP’s infrastructure guide gives rules of thumb: about 2% as the benchmark and persistently above about 5% as the danger zone. They are vendor guidance rather than provider-published limits, but they are a useful alarm.

The verification ladder, cheapest first

BusinessMCP’s guide on email finders versus verification lays the checks out in order, and the sequence is worth copying.

Check	What it confirms	What it cannot confirm
Syntax	The address is well formed	That anything exists
MX lookup	The domain accepts mail	That the mailbox exists
Disposable, role, free-mail lists	Throwaway domains, shared inboxes (info@, sales@), consumer providers	Whether a role inbox is monitored
Catch-all detection	Whether the domain accepts mail for any address	Which addresses are real on such domains
SMTP mailbox probe	Asks the server about the specific recipient	Reliable answers; greylisting and rate limits interfere

Key takeaway: each rung adds signal and cost. Use cheap checks on everything, and reserve the slow, risky probe for addresses where mailbox-level certainty is worth it.

Catch-all domains: the limit nobody can remove

A catch-all domain accepts mail for any local part, so [email protected] does not bounce at the SMTP stage even when no such mailbox exists. No verifier can separate real mailboxes from guesses there. The honest options are to treat catch-all addresses as risky, send to them at low volume, or skip them. BusinessMCP’s approach is to hold catch-all and unknown addresses for review rather than sending autonomously.

What a good verifier returns

The word “valid” should make you suspicious. The BusinessMCP verification API, documented in the guide above, never returns it. Its verdicts are:

• undeliverable: drop it.
• risky: disposable, catch-all, role inbox or no MX; hold for review.
• domain_ok: the domain accepts mail but the mailbox was not contacted.
• unknown: DNS timed out; retry later.

BusinessMCP lists email verification at $0.002 per call on its email deliverability checker page, alongside a $0.01 per-call authentication check, with $5 of free credit for 7 days. Prices change; confirm on the page. Whatever tool you choose, prefer one that admits uncertainty over one that promises certainty.

A practical pre-send workflow

1. Collect with confirmation where possible. Double opt-in prevents most typos.
2. Run cheap checks (syntax, MX, disposable, role) on the whole list.
3. Label by evidence. Published addresses, pattern-validated and pattern-built guesses should look different in your CRM so guesses never pass as confirmed.
4. Hold risky addresses. Do not auto-send to catch-all or role addresses.
5. Send in a small first batch, watch bounces, then continue.
6. Suppress hard bounces permanently and never retry them.
7. Re-verify old lists before reuse; addresses decay as people change jobs.

Authentication still matters

Verification stops bounces. It does not make mail trusted. Pair it with correct SPF, DKIM and DMARC, which you can grade with the free deliverability checker and set up using our authentication guide. Both halves matter: verification prevents bounces, authentication affects whether delivered mail is trusted.

Where verification fits in the larger picture

• For cold programs, verification is mandatory hygiene; see cold email deliverability.
• For newsletters, double opt-in and sunset policies replace most of it.
• For the provider rules that punish high complaint rates, read Gmail and Yahoo requirements.

Mistakes to avoid

• Running the SMTP probe from your own sending IPs, which can harm your reputation. Use a third-party service or skip it.
• Treating “role” addresses as safe because they usually exist.
• Verifying once and mailing the same list for a year.
• Ignoring unknown results. Retry them later instead of treating them as good.
• Believing a vendor’s claimed accuracy percentage without testing it on a sample you can check yourself.

Measuring the effect

Track bounce rate before and after introducing verification on comparable sends. If hard bounces fall and complaints do not rise, the workflow is doing its job. If bounces stay high on verified lists, look at list age and source. A verified address that was collected three years ago can still bounce, because the person left the company the week after you checked. Verification is a snapshot, so schedule re-checks for any list you reuse, and always follow current provider guidance for the numbers that matter.

Worked example: cleaning a 10,000-address list

Numbers here are illustrative, to show the logic rather than predict your results. Suppose you inherit a list of 10,000 addresses gathered over three years from webinar signups, with no confirmation step.

1. Syntax and MX pass removes the obviously broken entries and domains that no longer accept mail. These are the cheapest removals and the safest.
2. Disposable and role filters flag throwaway domains and shared inboxes. Disposable addresses go; role addresses go to a review pile.
3. Catch-all detection splits the remainder. Addresses at catch-all domains move to a “risky” segment instead of the main send.
4. A pilot send to the cleanest segment, at low volume, shows your real bounce rate before you commit the rest.
5. Staged expansion brings in the risky segment in small batches only if the pilot is clean and complaints stay low.

The principle is to let evidence, not hope, decide who gets mail. The risky segment is where most damage hides, so give it the smallest batches and the closest watching.

What verification cannot do

Verification will not tell you whether someone wants your email. A perfectly valid address can still belong to a person who never asked to hear from you, and that person is the one who reports spam. Consent is a separate question, and for cold outreach it carries legal weight in many places. BusinessMCP’s cold email deliverability and compliance guide discusses that side, and a lawyer can advise on yours.

Nor does verification fix a broken domain. If SPF or DKIM is failing, even verified addresses will see poor placement. Grade the sending domain first with the free BusinessMCP checker, then verify the list, then send.

Keep a suppression list forever

The most valuable file in any sending operation is the suppression list: hard bounces, complaints and unsubscribes. It should be shared across every tool and domain that sends on your behalf, and imported before every send. Losing it when you switch platforms is a classic way to re-mail people who asked you to stop. Keep it in a plain format you control.