We make Tamtam, and this page ends with where it fits. How we checked this page.
The short answer
Email verification runs four checks without sending a message: the address is well formed, the domain exists, the domain has mail servers (MX records), and the server answers “yes” when asked to accept mail for that mailbox. The last step is the one that matters and the one that fails on catch-all domains, which say yes to everything. A good verifier returns valid, invalid, catch-all or unknown, and you send only to valid.
The four checks, in order
Syntax: is there a local part, an @ and a domain, with no illegal characters. This catches typos for free.
Domain: does the domain exist in DNS. A company that changed its name may have let the old domain lapse.
MX records: does the domain publish mail servers. No MX record means nobody receives mail there.
SMTP handshake: the verifier connects to the mail server, introduces itself, names a sender and asks to deliver to the address (the RCPT TO step). A “250” reply suggests the mailbox exists; a “550” means it does not. The verifier then disconnects before any message content is sent, so nothing lands in the inbox.
Why some answers come back “catch-all” or “unknown”
Catch-all domains accept mail for any address, real or invented. The handshake says yes to jane.doe@ and to xyz123@ alike, so it cannot tell you whether your prospect’s mailbox exists. Good verifiers flag these addresses as catch-all (or accept-all) rather than calling them valid.
Greylisting servers reject the first attempt on purpose and accept a retry minutes later. A verifier that does not retry marks good addresses as bad.
Some large providers do not reveal mailbox status to probes at all, so the handshake cannot confirm those addresses either. An answer the verifier cannot settle is not the same as invalid.
What to do with each result before a send
Valid: send. Invalid: suppress and never retry. Catch-all: send only in small batches and watch the bounces, or find a second source that agrees on the address. Unknown: re-verify a day later before deciding.
Deliverability guides put a healthy total bounce rate under 2% for cold email, with hard bounces under 1%, and treat 5% as the point to stop sending. A list that is 15% catch-all can blow through that on its own, which is why the share of catch-all addresses matters as much as the share of valid ones.
- Verify on the day you send, not the day you bought the list
- Count catch-all results separately in every report
- Remove any address after one clear hard bounce
How to tell a good verifier from a bad one
It separates catch-all from valid. A tool that calls every catch-all address “valid” makes its numbers look better and your bounce rate worse.
It retries greylisted servers and paces its probes, because servers throttle or block verifiers that hammer them.
It tells you when the check was made. An address verified six months ago tells you about six months ago.
Where Tamtam fits
Tamtam checks the mailbox before your reps see an email, at the moment you request it, after asking 35+ providers in turn. A verified email costs 1 enrich credit and nothing is charged when no verified email is found. If the job is to clean a file of addresses you already own, a dedicated verifier is built for exactly that. And it does not send email, so warmup and bounce handling stay with your sequencer.
Read next in the glossary
Frequently asked questions
Does email verification send an email?
No. The verifier stops the conversation with the mail server before any message is sent. The server does see the connection, though.
What is a catch-all email address?
An address on a domain that accepts mail for every address, existing or not. Verification cannot confirm the mailbox there, so good tools flag it as catch-all instead of valid.
How often should I re-verify a list?
Before every send to an old list. People change jobs and mailboxes are closed; a check from last quarter does not cover that.
