Deliverability

Email Verification

Definition

Email verification is the process of checking, before you send, that an address is well-formed, that its domain can receive mail, and that the mailbox is likely to accept it. It runs a layered set of tests (syntax, MX lookup, and an SMTP probe) and flags risky addresses like spam traps, disposable domains, and role accounts. Done first, it keeps your bounce rate low.

  • Confirms an address is deliverable before you send to it
  • Layered checks: syntax, then MX lookup, then an SMTP probe
  • Flags catch-all domains, disposable addresses, role accounts, and spam traps
  • Cuts your bounce rate and protects sender reputation
At a glance
Also called Email validation · list verification
Core checks Syntax · MX · SMTP probe
Flags Disposable · role-based · catch-all · traps
When to run At signup and before each send
Limit Catch-all domains cannot be confirmed
Goal Lower bounces, protect reputation

What email verification checks

Email verification is a stack of tests, run cheapest-first, that together estimate whether an address will accept mail. The point is to catch typos, dead domains, and bad data before a send turns them into a hard bounce. It does not guarantee delivery, but a good verifier removes most of the addresses that would otherwise bounce or land you in trouble.

The layers run roughly in this order:

  • Syntax check. Is the address even valid in form (name@domain.tld), with no stray characters or missing parts?
  • Domain and MX check. Does the domain exist, and does it publish MX records, meaning it can receive mail at all?
  • SMTP probe. The verifier opens an SMTP conversation and issues RCPT TO for the address to see whether the server accepts or rejects that specific mailbox, without actually sending a message.
  • Risk flags. Is it a known spam trap, a disposable throwaway domain, or a role account like info@ or support@?

Where verification hits its limits

The SMTP probe is powerful, but two things blunt it. First, many servers run a catch-all (or accept-all) policy: they accept mail for every address at the domain, real or not, so the probe gets a “yes” it cannot trust. A verifier can only mark these “unknown,” not “valid,” and you have to decide whether to risk them.

Second, some providers deliberately give vague or misleading SMTP responses to defeat verification and to avoid leaking which mailboxes exist. Aggressive probing can also itself harm your reputation if you hammer a provider, which is why bulk verification is best done through a dedicated service rather than your own sending infrastructure. The honest output of verification is a risk score, not a guarantee.

An SMTP probe rejecting an unknown mailbox without sending a message 
> MAIL FROM:<probe@verifier.example>
< 250 OK
> RCPT TO:<nosuchuser@example.com>
< 550 5.1.1 No such user here

When and how to use it

Use verification at two moments. At the point of capture, validate the address in real time at signup so a typo never enters your list; pairing this with double opt-in stops most bad data at the door. Before a send, run any old, imported, or long-dormant list through a bulk verifier so you are not mailing addresses that have decayed since you last touched them.

Verification is a core part of list hygiene, not a replacement for it. It removes the addresses that would bounce, while suppression of unsubscribes and complainers, and a sunset policy for the unengaged, handle the rest. Together they keep your bounce rate and complaint rate inside the limits mailbox providers enforce.

How an address is verified

An address is submitted for checking
Syntax check: is it well-formed?
Malformed: invalid
Domain and MX check: can the domain receive mail?
No MX: invalid
SMTP probe: does the server accept this mailbox?
Rejected: invalid Catch-all: unknown
Accepted and low-risk: safe to send

Verification result types

Valid Risky Invalid
Meaning Mailbox accepts mail Cannot be confirmed Will bounce
Examples Verified inbox Catch-all, role account No MX, no such user
Action Send Send with caution Suppress
Bounce risk Low Medium High

By the numbers

3
The core verification layers: syntax, MX lookup, and an SMTP probe, run from cheapest to most thorough.
550 5.1.1
The SMTP rejection a probe looks for to mark a mailbox invalid: the user does not exist.

Common mistakes

Trusting a catch-all as valid
A catch-all domain accepts every address, so a “valid” result there is meaningless. Treat catch-all addresses as risky, not confirmed, and lean on engagement to sort the real ones from the rest.
Verifying once and never again
Addresses decay. A list verified a year ago has since accumulated dead mailboxes and new spam traps. Re-verify before mailing any list you have not sent to recently.
Probing from your own sending IP
Bulk SMTP probing from the IP you send real mail on can itself damage your reputation. Use a dedicated verification service that does this carefully and at arm’s length.
Skipping verification because you use double opt-in
Double opt-in stops bad sign-ups but does nothing for imported lists or addresses that decayed after they confirmed. The two are complementary, not interchangeable.

Frequently asked questions

How does email verification work?
It runs a layered set of checks, cheapest first. A syntax check confirms the address is well-formed, an MX lookup confirms the domain can receive mail, and an SMTP probe opens a connection and issues RCPT TO to see whether the server accepts that specific mailbox without sending a message. On top of that it flags disposable domains, role accounts, and known spam traps. The output is a risk verdict, not an absolute guarantee.
Can email verification detect every bad address?
No. Catch-all domains accept mail for every address whether or not the mailbox exists, so a verifier can only mark them “unknown.” Some providers also return deliberately vague SMTP responses to defeat probing. Verification removes the clearly dead and clearly risky addresses, which is most of them, but it cannot promise that every “valid” address will accept your mail.
Does email verification improve deliverability?
Yes, indirectly but strongly. By removing addresses that would hard bounce, it keeps your bounce rate low, and a low bounce rate is one of the signals mailbox providers use to decide inbox placement. It also screens out spam traps that could get you blacklisted. Combined with suppression and a sunset policy, verification is a cornerstone of list hygiene.
When should I verify email addresses?
At two points: in real time when an address is captured at signup, so typos never enter your list, and in bulk before you send to any old, imported, or long-dormant list. Verifying at capture keeps new data clean, while periodic re-verification handles the decay that creeps into every list over time.
Reviewed by Jennifer Jackson, Email Deliverability Analyst · June 2026 ← Back to glossary