Email Verification Best Practices

Email verification checks whether an email address exists, accepts mail, and is safe to send to before you actually send. It's the last gate between your list and your reputation. Every bounced email damages your sender domain reputation. A 5% bounce rate triggers spam filters. A 10% bounce rate can get your domain blacklisted. Verification costs $0.003-0.01 per email. Reputation recovery takes weeks. The math is obvious.

The principle: verify every email before it enters a sequence. No exceptions. Not "most emails." Not "emails from purchased lists." Every email, every time, regardless of source.

How Email Verification Works

The 5-step verification process

Every verification tool runs these checks in order. The result is a composite verdict based on all five.

Verification result categories

When to Verify

Verification triggers

Verification timing rules

• Verify as close to send time as possible. An email verified 30 days ago may have been deactivated since. For high-stakes sends (ABM, enterprise), verify within 48 hours of sending
• Bulk verify on import. Re-verify on enrollment. Import verification catches the obvious invalids. Enrollment verification catches the recently deactivated
• Never skip verification because "these emails came from a trusted source." CRM data decays. Enrichment tools have 5-15% error rates. Event platforms have typos. Verify everything

Verification Tool Comparison

Major tools

Tool selection

Selection rules

• Accuracy above 95% is the minimum bar. Below that, you're accepting a 5%+ false-positive rate (marking valid emails as invalid) or false-negative rate (marking invalid emails as valid). Both are expensive
• API access is essential for automation. If you're verifying on form submit, on CRM import, or in a workflow, you need API access. Bulk-upload-only tools are fine for one-time cleans but not for ongoing hygiene
• Test with 500 known-good and 500 known-bad emails. Measure true positive rate, true negative rate, and unknown/catch-all rate against your ground truth. Every tool claims 97%+ accuracy. Test it yourself

Catch-All Domain Handling

Catch-all domains are the hardest verification challenge. The server says "yes, I accept mail for any address," so verification tools can't confirm whether a specific mailbox exists.

Catch-all prevalence

• ~15-25% of B2B domains are catch-all
• More common with smaller companies, custom mail servers, and Microsoft 365 tenants configured to accept all mail
• Less common with large enterprises (they typically reject invalid addresses)

Catch-all decision framework

Catch-all rules

• Never batch more than 20% catch-all addresses in a single send. If 40% of your list is catch-all, split into batches and spread over days
• Track bounce rates separately for catch-all vs verified-valid addresses. If catch-all bounces exceed 5%, tighten your catch-all policy
• Remove catch-all addresses on first hard bounce. Don't retry. A hard bounce on a catch-all domain means the pattern guess was wrong
• Re-verify catch-all addresses monthly. Some catch-all domains switch to rejection-based configs over time. A previously catch-all domain may become verifiable

Bounce Rate Management

Bounce rate targets

Bounce types

When bounce rate exceeds targets

Bounce rate > 3%?
│
├── Check list source
│   └── Purchased list or unverified import? → Re-verify entire list.
│       Remove invalids. This is a data quality problem
│
├── Check verification coverage
│   └── Were all emails verified before sending? → If no, start verifying.
│       If yes, your verification tool may have low accuracy. Test a different tool
│
├── Check catch-all ratio
│   └── More than 25% of bounces from catch-all addresses? → Tighten
│       catch-all policy. Reduce catch-all volume per batch
│
├── Check email age
│   └── Sending to contacts found 3+ months ago? → Re-verify before send.
│       Email addresses decay at 2-3% per month
│
└── Check domain reputation
    └── Using a new or recently warmed domain? → Reduce send volume.
        Warm up slower. Check SPF/DKIM/DMARC configuration

Verification Workflow Integration

Workflow 1: Verify on CRM import

CSV upload / API import
  → Pre-import: bulk verify entire list
  → Filter: remove Invalid, Disposable, Risky
  → Flag: mark Catch-All with "catch_all = true" property
  → Import: only Valid + Catch-All (flagged) into CRM
  → Log: record verification date and result per contact

Workflow 2: Verify on sequence enrollment

Contact added to sequence
  → Check: last_verified_date > 30 days ago?
  → If yes: re-verify via API before enrollment
  → If result = Valid: enroll
  → If result = Invalid: remove from sequence, update CRM
  → If result = Catch-All: enroll with catch-all flag, monitor bounce
  → If result = Unknown: hold, retry in 24 hours

Workflow 3: Monthly re-verification

Scheduled monthly (1st of month)
  → Query: all contacts with lifecycle stage = Lead or MQL
    AND last_verified_date > 30 days ago
  → Bulk verify
  → Update CRM: verified_status, last_verified_date
  → Remove from active sequences: any contact now Invalid
  → Alert RevOps: report of newly invalid contacts

Workflow 4: Real-time verification on form submit

Form submitted (demo request, content download)
  → API call: verify email in real-time (< 3 seconds)
  → If Valid: process normally (route, nurture, alert)
  → If Invalid: show form error "Please enter a valid work email"
  → If Disposable: show form error "Please use your work email"
  → If Catch-All: process normally (can't determine in real-time)
  → If Unknown/Timeout: process normally, verify async later

Real-time verification rules:

• Timeout must be < 3 seconds. If verification takes longer, accept the email and verify asynchronously. Don't make the user wait
• Don't block form submission on "Unknown" results. Network issues cause unknowns. Blocking creates a bad user experience for a valid email
• Show user-friendly errors, not technical messages. "Please enter a valid work email" not "SMTP verification failed with 550 response"

Data Hygiene Integration

Verification properties in CRM

Automation rules

• Contacts with email_verified_status = Invalid should be automatically removed from all active sequences
• Contacts with email_bounce_count >= 2 should be flagged for manual review and removed from outbound
• Contacts with email_last_verified_date > 90 days should be re-verified before any new enrollment
• New contacts with email_verified_status = Unverified should not be enrollable in sequences until verified

Cost Analysis

Verification cost vs bounce cost

The verification ROI is effectively infinite. $50-100 per month in verification costs protects a sender reputation that takes weeks to rebuild and thousands of dollars in lost pipeline to recover.

Pre-Send Checklist

Before any outbound send:

• [ ] All emails verified within the last 30 days
• [ ] Invalid, Disposable, and Risky addresses removed
• [ ] Catch-all addresses flagged and limited to < 20% of the batch
• [ ] Role-based addresses (info@, sales@) excluded from personal outbound
• [ ] Bounce rate from last send was < 3% (if not, investigate before sending again)
• [ ] SPF, DKIM, and DMARC configured on sending domain
• [ ] Sending domain is warmed up (if new)
• [ ] Unsubscribed contacts excluded
• [ ] Previous hard-bounced contacts excluded

Anti-Pattern Check

• Skipping verification because "these emails came from Apollo/Hunter." Even the best finders have 5-15% invalid results. Verify everything. The $50 cost protects your domain reputation
• Treating catch-all as "valid." Catch-all means "we can't tell." Send with caution, monitor bounces, remove on first hard bounce. Don't treat catch-all the same as verified-valid
• Verifying once and never re-verifying. Email addresses decay at 2-3% per month. A list verified 6 months ago has 12-18% decay. Re-verify monthly for active contacts, quarterly for nurture lists
• Sending to contacts that previously hard-bounced. A hard bounce is permanent. The email doesn't exist. Never retry. Mark as invalid in CRM and exclude from all future sends
• No verification properties in CRM. Without email_verified_status and email_last_verified_date, you can't automate verification workflows or report on data quality. Add these properties on Day 1
• Accepting 5%+ bounce rate as normal. Below 2% is healthy. 2-3% is a warning. Above 3% is damaging your domain. If bounce rate exceeds 3%, stop sending and diagnose before continuing
• Real-time verification blocking form submissions for > 5 seconds. If the verification API is slow, accept the email and verify asynchronously. A blocked form loses the lead entirely
• Not tracking bounce rates separately for catch-all addresses. If catch-all bounces are 15% while verified-valid bounces are 1%, your catch-all policy is too loose. Track them separately to know