How does email verification work?

Email verification checks whether an address can receive mail without sending a message to it. A verifier checks the syntax, confirms the domain has DNS and MX records, flags disposable and role addresses, then asks the mail server over SMTP whether the mailbox exists. Results are usually labelled valid, invalid, catch-all or unknown, because some servers accept every address or give no clear answer.

Facts about other products checked on 2026-11-09 · sources listed below

Check	What it tests	What it catches
Syntax	Is the address correctly formed?	Typos, missing @, illegal characters
Domain, DNS and MX	Does the domain exist and publish mail servers?	Dead or misspelled domains
Disposable and role	Is it a throwaway inbox or a shared inbox like `info@`?	Low-value or temporary addresses
Mailbox (SMTP)	Will the server accept mail for this recipient?	Mailboxes that do not exist
Catch-all test	Does the server accept a random, fake address too?	Domains where a yes proves nothing
Retry or second opinion	Can an unclear answer be resolved?	Timeouts, greylisting, blocked probes

What email verification means

Email verification is the process of checking whether an email address is real and able to receive mail, without sending a message to it. Sales and marketing teams run it before a campaign so they do not send to addresses that bounce, because a high bounce rate can damage a sending domain's reputation. The reasons are covered in more depth in why email verification is important.

The phrase has a second common meaning. When you sign up for an app and get a "confirm your email" link, that is also called email verification: it proves you own the address. This page is about the first meaning, checking an address from the outside, which is what B2B data and outreach tools do.

It also helps to separate verification from discovery. Finding someone's work email (part of lead enrichment) produces a candidate address. Verification tests whether that candidate, or any address you already hold, is likely to be delivered.

The checks, step by step

Most verifiers run cheap checks first and stop early when an address clearly fails.

Syntax. Is the address correctly formed? A missing @, spaces, illegal characters or obvious typos in common domains fail here.
Domain and DNS. Does the domain exist, and does it publish MX records that tell the internet which servers accept its mail? A domain with no MX record normally cannot receive email.
Disposable and role addresses. Is the domain a throwaway inbox service? Is the address a shared inbox like info@ or sales@ rather than a person? These are not always invalid, but they are usually flagged.
Mailbox-level (SMTP) check. The verifier connects to the domain's mail server and starts the same conversation a sending server would, up to the point where it names the recipient. The server's reply code shows whether it would accept mail for that mailbox. The verifier then disconnects before any message is sent.
Catch-all test. The verifier also asks about a random address that should not exist on the same domain. If the server accepts that too, the domain is catch-all: it says yes to everything, so a yes for the real address proves nothing.
Handling unclear answers. Some servers time out, temporarily reject unfamiliar senders (greylisting) or block verification traffic. A careful verifier retries, may ask a second verifier, and labels anything still unclear as unknown.

What the result labels mean

Labels vary by tool, but they map to four outcomes.

Valid or verified: the server accepted the mailbox and the domain is not catch-all.
Invalid: the address is malformed, the domain cannot receive mail, or the server rejected the mailbox. These bounce.
Catch-all (accept-all): the domain accepts every address, so nobody can confirm this particular mailbox from outside. Many are real; some bounce later. See what is a catch-all email.
Unknown: the server gave no clear answer. The address is unconfirmed, not good or bad.

Some tools fold catch-all and unknown into a single "risky" bucket, and some count catch-alls as valid. Before trusting a "valid" count, check which of these the tool means.

Why verification can never be 100%

A verifier only sees what the mail server chooses to say. Several things limit accuracy:

Catch-all domains hide whether a mailbox exists.
Some servers accept a recipient during the SMTP conversation and bounce the message later.
Some mail providers block or rate-limit verification probes, which pushes results to unknown.
A result is a point in time. People change jobs and mailboxes get closed, so a list verified months ago may not be clean today.

Because of this, a claim of perfect accuracy deserves a second look, and it is good practice to re-verify a list before sending if it has not been checked recently.

How providers describe their checks

Most B2B data vendors use some version of the steps above but describe and label them differently. As published on 2026-11-09:

Wiza says it verifies in real time at request time with syntax, domain, MX, SMTP, catch-all and disposable checks, and labels results valid or risky. Wiza says risky emails have 50 to 70% deliverability and are not charged.
ZoomInfo describes syntax, domain/MX, SMTP and risk checks (catch-all, disposable, role-based), cites NeverBounce, and says it uses actual delivery attempts against catch-all domains.
Apollo says it uses seven-step email verification with 98% accuracy plus waterfall verification. The steps are not published.
Clay has not published an official verification method. Community answers say its email waterfalls validate with ZeroBounce by default and count catch-alls as valid unless "only mark safe to send" is enabled.
Leadsets runs a waterfall: syntax, DNS and MX, disposable and role checks; then a mailbox-level check; then a second verifier for uncertain, catch-all or conflicting results. It returns verified, catch-all, unknown or invalid with a confidence score and the time it was checked, and does not round uncertain results up to valid. Details are on the email verification page.

The practical takeaway: whichever tool you use, ask how catch-all and unknown results are labelled and whether you pay for them.

An example: cleaning a list before a campaign

Maya Chen runs revenue operations at Northwind Analytics (northwind.co). She has 800 addresses gathered from an event sign-up sheet and a few older spreadsheets, and wants to load them into a sequencer.

She runs the whole list through a verifier first and splits the results four ways:

Verified addresses go into the main campaign.
Catch-all addresses go into a separate send at lower volume, so any bounces stay contained.
Unknown addresses are held back and re-checked later.
Invalid addresses are removed.

If Maya used Leadsets for this, her agent would call verify_email on the batch; on paid plans, bulk lists run as an async job she can pull results from when ready. Standalone verification counts toward the enrichment limits described in limits and costs, and emails returned by enrich_person are already verified. The free plan's 1,000 records cover verification, so a small list can be checked without a card. Any verifier that keeps catch-all and unknown separate supports the same workflow.

Questions and answers

What does email verification mean?

Email verification means checking whether an email address is correctly formed and able to receive mail, without sending a message to it. In account sign-ups, the term also refers to clicking a confirmation link to prove you own an address.

Does email verification send an email?

No. A verifier talks to the recipient's mail server and stops before any message is sent. The server's response to the recipient address indicates whether the mailbox would accept mail.

What is a catch-all email address?

A catch-all domain accepts mail for any address, real or not. Because the server says yes to everything, a verifier cannot confirm that a specific mailbox exists, so these addresses are usually labelled catch-all or risky rather than valid.

How accurate is email verification?

Verification removes most bad addresses, but no verifier can guarantee every result. Catch-all domains, servers that block probes and mailboxes that close after the check all leave some uncertainty, which is why careful tools label unclear results as unknown.

What is the difference between email validation and email verification?

The terms are often used interchangeably. When people separate them, validation usually means format and domain checks, while verification adds a mailbox-level check with the mail server.

How often should I verify an email list?

Verify a list before each send if it has not been checked recently. People change jobs and mailboxes get closed, so a result reflects only the moment it was checked.

Sources · checked 2026-11-09

Prices and features change. If something here is out of date, email support@leadsets.ai and we'll fix it.

Go deeper