What is email verification?

Email verification runs a contact address through a layered technical stack, not a single check. The first step is syntax validation: does the address contain an @ symbol, a valid local part, and a properly formed domain? This is instant and requires no network calls — it catches obvious typos and formatting errors but cannot confirm whether the address belongs to a real, active mailbox.

The second step is a DNS/MX record lookup. The verifier queries the domain's mail exchange records to confirm the domain exists and is configured to receive email. A domain with no valid MX records cannot receive any messages, regardless of how the local part looks. Domains go dark — companies shut down, rebrand, or migrate infrastructure — and MX lookups catch those casualties immediately.

The third and most diagnostic step is an SMTP handshake. The verifier opens a connection to the destination mail server and issues the RCPT TO command for the target address — without ever sending a real message. The server responds with a code: 250 OK (mailbox exists), 550 No Such User (mailbox does not exist), or a temporary failure. On catch-all domains, the server returns 250 for every address presented, so verifiers flag those separately as 'Accept-All' rather than treating them as confirmed valid. The final layer cross-references known spam-trap databases, disposable email domain registries, and abuse address lists to screen for addresses that would trigger reputation penalties even if technically deliverable.

There are three primary deployment modes, each suited to a different point in the data lifecycle. Bulk list verification processes a CSV or API-fed list in a single batch — typically before a campaign or on a scheduled hygiene cadence. It is the right choice for cleaning legacy lists, scrubbing imported enrichment data, or preparing a large prospect list before a new sequence launch. Most providers return results within minutes for lists up to 100,000 addresses.

Real-time API verification fires at the moment of email capture — a signup form, a CRM import flow, or a chatbot conversation. It blocks bad addresses before they enter a system, eliminating a root cause of list decay. Services like Kickbox, Bouncer, and ZeroBounce's API return a structured response within milliseconds that downstream logic can act on to accept, flag, or reject the submission.

Continuous or automated monitoring (offered by tools like NeverBounce Sync) connects directly to an ESP or CRM and re-verifies the list on an ongoing schedule — daily or weekly — removing contacts that have become invalid since the last check. This mode is most valuable for teams with large, frequently changing contact databases where a 30-day lag between manual cleans would still allow significant decay to accumulate and damage sender reputation.

Inbox providers — principally Google and Microsoft — use bounce rate and authentication compliance as direct signals of list hygiene quality. As of November 2025, Gmail permanently rejects email from senders whose hard bounce rate exceeds 2%, issuing 5xx failure codes that do not reset automatically and compound with continued poor-hygiene sending. Earlier phases (April–June 2024) issued temporary errors and graduated enforcement; November 2025 moved to full permanent rejection.

Microsoft's parallel enforcement (effective May 5, 2025) operates on a different axis: for domains sending more than 5,000 emails per day to Outlook.com, Hotmail, Live.com, or MSN.com addresses, failure to pass SPF, DKIM, and DMARC authentication results in immediate 550 5.7.515 rejection. Microsoft has not published a bounce-rate percentage threshold equivalent to Gmail's 2% rule — its enforcement is authentication-focused rather than bounce-rate-triggered.

Bounce rate is only the most visible consequence of unverified lists. Sending to recycled spam traps — addresses that were once valid but have been repurposed by providers to detect senders with poor hygiene — can result in immediate IP blacklisting, damaging deliverability for every domain and IP sharing the same sending infrastructure. The aggregate effect is captured in inbox placement data: the average placement rate sits at 83.1% across ESPs (EmailTooltester), and senders maintaining bounce rates below 2% through active verification consistently achieve 85%+ placement, while those at 3–5% collapse to 60–70%.

The terms are used interchangeably in the industry but they describe different scopes of checking. Email validation is the lighter-weight process: it confirms that an address is syntactically correct — a properly formatted local part, an @ symbol, and a valid-looking domain. It requires no network calls and can be run client-side with a regular expression. Validation catches obvious user-entry errors (missing @, invalid TLD, extra spaces) but cannot confirm whether the address belongs to an active, real mailbox.

Email verification is the fuller process. It includes validation but goes further: querying DNS/MX records, performing an SMTP handshake, checking catch-all status, and screening against spam-trap and disposable-email databases. Verification confirms — to the degree technically possible — that the address can receive messages and is not likely to produce a bounce or a reputation penalty.

In practice, most enterprise tools use the term 'email verification' to cover the complete multi-layer process. The distinction matters most when evaluating vendor tools or understanding scope: a tool that only performs syntax checks (validation) offers very little protection against domain-gone-dark or mailbox-closed scenarios, which are the dominant drivers of B2B hard bounces. Verification is the operationally relevant standard for any sender focused on deliverability.

The recommended verification cadence depends on list size, sending frequency, and the sector's churn velocity. For active outbound sequences, most practitioners re-verify every 30–90 days; any list unused for 6 months or more should be treated as unverified and cleaned in full before sending. In high-churn sectors like SaaS and technology — where professional turnover and company restructuring push annual email decay above 35% — monthly verification sweeps are common. ZeroBounce's 2026 decay report found that at the 23% annual decay rate observed across 11 billion+ addresses, even a 90-day window exposes roughly 5–6% of a list to invalid-address risk.

The hard-bounce-rate targets enforced by Gmail — 2% as the outer boundary, with a practical goal under 1% — are the operational benchmarks most outbound teams work against. Top-performing senders consistently stay below 0.5% by combining real-time API verification at the point of data capture with periodic bulk re-verification of the full contact database. Saleshandy's analysis of 53 million+ cold emails found that senders using verified lists averaged 1.53% bounce rate versus 2.55% for unverified lists — a 40% reduction that is the difference between compliance and permanent Gmail rejection.

Bounce rate is not the only metric to watch. Spam complaint rate above 0.1% begins damaging reputation with major providers; above 0.3%, it creates significant deliverability problems. Spam-trap hits and inbox placement rate both feed into the sender reputation score that determines whether future campaigns land in the inbox or the spam folder. List hygiene is the upstream fix for all three metrics simultaneously.

Komo operates as an AI Revenue Engine that automates the signal-to-send workflow — from detecting a buying trigger (a funding event, a leadership change, a hiring surge) to researching the prospect, surfacing the best contact, and drafting a personalized outreach message for human review. That entire workflow depends on verified, deliverable contact data: a draft written for an invalid email address wastes the signal, burns a sequence slot, and accumulates the bounce rate that erodes the domain's sending health over time.

Komo integrates enrichment and verification as a standard part of the prospect research step. Before a rep reviews a draft, the contact's email address has been checked against live MX records and validated for deliverability — consistent with the hygiene practices that keep bounce rates below 1% and inbox placement above 85%.

The human-in-the-loop design adds a practical quality checkpoint: a sales rep approves every send, creating a natural moment to flag contacts where verification returned a risky or catch-all result rather than a confirmed-valid status. This combination of automated hygiene and human review is what separates signal-based outreach at scale — where deliverability is a measurable competitive advantage — from bulk campaigns that erode their own sender reputation faster than they generate pipeline.