Skip to content
    Learning library / Deliverability

    Email Verification Before You Send

    The verification pipeline that protects your sender reputation. Risk tiers, sendex scores, and why that 'valid' email might still bounce.

    In this guide

    A list can contain addresses that are outdated or incorrectly formatted. Checking them before sending reduces avoidable delivery failures and helps you identify data sources that need attention.

    Verification helps identify invalid or uncertain addresses before sending. Results vary by provider and cannot identify every spam trap, prove permission or guarantee delivery.

    This guide explains exactly what happens during verification, what the results mean, and how to use them to protect your deliverability.

    1. Why Verification Matters More Than You Think

    Email providers track your bounce rate obsessively. Every bounced email signals "this sender doesn't maintain their list" — and the penalty is swift.

    What Happens Without Verification:

    Day 1: Campaign sends to 1,000 contacts (no verification)

    Day 2: 50 addresses bounce in this illustrative example; investigate the cause before sending again

    Day 3: Pause the affected segment and inspect provider responses before another campaign

    Week 2: Open rates crater; replies drop to near zero

    Month 1: Domain reputation is "Poor" — deliverability is broken

    Warning

    Bounces are permanent reputation damage. Unlike low open rates (which recover), high bounce rates can take months to repair. Prevention via verification is the only reliable strategy.

    2. What Verification Actually Checks

    Email verification isn't just "does this address exist?" It's a multi-layer analysis that checks syntax, domain, mailbox, and risk signals.

    The Verification Stack:

    1

    Syntax Check

    Is the email format valid? Catches typos like "john@@company.com" or "john@company"

    2

    Domain Check

    Does the domain exist? Does it have valid MX records for receiving email?

    3

    Mailbox Check

    Does this specific mailbox exist? SMTP-level verification without sending a real email.

    4

    Risk Assessment

    Does the provider flag disposable, role-based or catch-all status? What checks and limitations does it document?

    Note

    Verification doesn't send email. SMTP verification pings the mail server to check if the mailbox accepts messages — without actually delivering anything. No engagement signals are created.

    3. The 5 Risk Tiers Explained

    Verification results aren't just "valid" or "invalid." They're assigned to risk tiers that indicate the provider's assessment of the address.

    Safe

    Verified deliverable email. Mailbox exists, domain is valid, no risk signals detected. Review freshness and campaign eligibility.

    Low Risk

    Likely deliverable but with minor concerns. Possibly catch-all domain or limited mailbox data. Send, but monitor bounce rates.

    Medium Risk

    May have delivery issues. Could be catch-all, temporary issue, or limited data. Consider excluding from large campaigns.

    High Risk

    The provider has reported issues or uncertain signals that require review. Do not include in campaigns.

    Blocked

    Do not send when the address is invalid or suppressed. Investigate other provider flags before including a contact in a campaign. Keep suppression rules enforced.

    Pro Tip

    Document the verification statuses your campaign will exclude. A score threshold is a sending policy choice, not a universal guarantee.

    4. Interpret Verification Scores

    Some verification providers supply a score alongside a status. Read that provider's current definition and scale before using it in a sending rule. A score does not establish an inbox-delivery probability.

    For MSP prospecting, record the provider, verification time and returned status. Exclude invalid addresses, investigate unknown or catch-all results, and verify stale records again before the next campaign. Set any score cutoff as a documented internal policy and review actual delivery failures.

    5. Special Cases to Watch

    Some emails pass basic validation but still pose risks. Understanding these edge cases helps you make smarter decisions about who to include in campaigns.

    Role-Based Addresses

    info@, support@, sales@, admin@

    These go to groups, not individuals. Higher spam complaint rates. Many email tools block role-based addresses entirely.

    Catch-All Domains

    Domains configured to accept email to any address (even nonexistent ones)

    Verification can't confirm if the specific mailbox exists. "deliverable" result but may still bounce. Treat as medium risk.

    Disposable/Temporary Emails

    Services like Guerrilla Mail, 10 Minute Mail, Mailinator

    Created to avoid spam. Inbox often deleted within hours. Not real prospects — automatically blocked.

    Spam Traps

    Addresses created by ISPs specifically to catch spammers

    Some providers flag suspected traps using their own data. No verification service can promise to identify all of them. Use reliable sources and honor suppression and consent requirements.

    Free Email Providers

    Gmail, Yahoo, Outlook personal accounts

    Not invalid, but for B2B outreach, personal emails are often lower quality leads. Flagged for awareness, not blocked.

    Warning

    Spam traps are silent killers. You won't see a bounce — the email is accepted. But behind the scenes, your domain is flagged. Verification is the only way to detect them before sending.

    6. Protecting Your Sender Reputation

    Verification is step one. But protecting your reputation requires ongoing hygiene and smart sending practices.

    Email Verification Best Practices

    Do This
    • Verify every email before adding to any campaign
    • Re-verify stale contacts before a new campaign
    • Block all high-risk and blocked tier emails
    • Monitor bounce rates in real-time during campaigns
    • Maintain a suppression list of known bad addresses
    Avoid This
    • Send to unverified imported lists
    • Assume 'valid' means 'safe' (check risk tier too)
    • Ignore catch-all domain warnings
    • Skip verification to 'save time' on small campaigns
    • Send to role-based addresses in cold outreach

    The Verification Workflow:

    Import: New contacts enter the system (any source)

    Verify: Automatic Kickbox verification assigns risk tier

    Filter: High-risk and blocked contacts are suppressed

    Enrich: Safe contacts proceed to enrichment pipeline

    Campaign: Only verified, enriched contacts enter campaigns

    Monitor: Bounce webhook updates status in real-time

    Pro Tip

    Verification is not a one-time event. Emails go stale. People leave companies. Domains expire. Re-verify stale contacts before the next campaign.

    Key Takeaways

    • 1.Investigate rising bounces. Inspect failure codes and pause affected sends.
    • 2.Verification checks 4 layers — syntax, domain, mailbox existence, and risk signals.
    • 3.5 risk tiers: Safe, Low Risk, Medium Risk, High Risk, Blocked — not all "valid" emails are safe to send.
    • 4.Sendex score (provider-specific) — an additional provider signal to interpret alongside status.
    • 5.Watch special cases — role-based, catch-all, disposable, and spam traps all pose unique risks.
    • 6.Re-verify stale records — email data decays fast. Verification isn't a one-time event.

    Common questions

    Why does email verification matter before sending a cold outreach campaign?

    Verification helps identify invalid or risky addresses before sending. Monitor actual delivery responses as well: verification cannot establish consent or guarantee inbox placement. Google's published spam-rate targets are not universal bounce-rate limits.

    What is a sendex score and how should I use it?

    A verification score is a provider-specific signal. Check its definition and scale in the provider documentation, then combine it with status and recent delivery results. It is not a guarantee of delivery, and any campaign cutoff should be a documented internal policy.

    What types of email addresses should I never include in cold outreach?

    Exclude invalid addresses and known suppression entries. Investigate unknown, disposable, role-based and catch-all results before use. Verification cannot reliably identify every spam trap or establish permission to contact someone.

    How often should I re-verify email contacts?

    Re-verify before a new campaign when records are stale, the source is uncertain or recent delivery failures suggest a problem. Set the review interval based on your data source and observed changes rather than a universal expiration date.

    Share on LinkedIn ↗

    Keep reading

    Start with a conversation

    What are you
    working toward?

    Tell us about your business. We’ll work out where we can help.

    Talk to us