What is Email Verification?
Definition: The process of validating whether an email address exists, is deliverable, and is safe to send to, using SMTP checks, domain validation, and mailbox pinging to prevent bounces.
Email verification sits between enrichment and outbound. You found 1,000 email addresses through Apollo or Clay. Before you load them into Instantly and start sending, you need to know which ones will bounce. A bounce rate above 2-3% damages your sender reputation and can get your domain blacklisted.
Verification tools check several things: Does the domain exist? Does the mail server respond? Does the specific mailbox exist? Is the address a known spam trap? Is it a catch-all domain (accepts all emails regardless of address)? The result is a status: valid, invalid, risky, or unknown.
Most GTM Engineers run verification as a step in their Clay waterfall or as a standalone batch process. NeverBounce, ZeroBounce, and MillionVerifier are popular standalone services. Clay and FullEnrich include verification in their enrichment workflows.
The economics are simple. Verification costs $0.003-$0.01 per email. A bounced email costs you sender reputation that takes weeks to rebuild. Run verification on every list, every time. Even if the emails are "verified" by the provider. Providers often verify at collection time but addresses go stale fast. Someone changes jobs, and their old email bounces within 90 days.
Batch verification vs real-time verification serves different purposes. Batch verification runs your entire list through a service before loading it into your sequencing tool. This catches the obvious invalids upfront. Real-time verification checks each email right before sending, catching addresses that went bad between your batch check and the send date. Services like ZeroBounce and NeverBounce offer both modes. For campaigns that run over several weeks, real-time verification prevents the decay problem where a batch-verified list loses 2-3% validity per month.
Verification results include nuance that many teams ignore. Beyond "valid" and "invalid," most tools return categories like "risky," "accept-all," "disposable," and "role-based." Role-based addresses (info@, support@, sales@) rarely convert in cold outreach because they go to shared inboxes. Disposable addresses (Mailinator, Guerrilla Mail) indicate someone who doesn't want to hear from you. Filtering these categories out before sending, in addition to removing invalids, produces cleaner campaigns with higher engagement rates.
Building verification into your automation pipeline as a mandatory step, rather than an optional one, prevents the most common deliverability failures. In Clay, add a verification column after your email enrichment column and a filter that blocks unverified emails from reaching the CRM push or sequence enrollment step. In n8n, add a verification API node between enrichment and output. This structural enforcement means no unverified email ever reaches your sending tool, regardless of who runs the workflow or how rushed the timeline is.