Add SMTPedia as a preferred source on Google
Email verification
Validate every address before it enters your sending queue. Catch disposables, spamtraps, catch-alls, role accounts, and dead mailboxes. The reference on keeping your bounce rate under 1 percent and your reputation intact.
Email verification is the process of confirming that an address exists, accepts mail, and belongs to a real person before you send. It sits between your list and your ESP, catching bad addresses that would otherwise become hard bounces, spamtrap hits, or reputation damage.
The stakes have risen in 2026. Gmail and Yahoo enforce a 0.3 percent complaint threshold that a single dirty import can breach. Blocklists like Spamhaus escalate on trap hits. Buying a "verified" list still means you own the deliverability consequences. The only sustainable approach: validate at collection, re-validate on cadence.
This hub covers the mechanics (SMTP probing, RFC 5321 checks), the taxonomy (disposables, roles, catch-alls, spamtraps), and the tooling (which providers to use, how they compare). Every guide is technical where it needs to be, plain-spoken everywhere else.
Disposable emails
61 providers tracked with domain counts, detection methods, and known aliases.
Read guides →Spamtraps and honeypots
Pristine vs recycled traps, detection cost, and how to avoid trap-heavy sources.
Read guides →Role-based emails
info@, sales@, support@: when to accept them and when they will burn you.
Read guides →Catch-all detection
Domains that accept everything: how to identify, score, and decide whether to send.
Read guides →Verification tools
7 providers compared: accuracy, pricing, free tier, API quality.
Read guides →CVLKRA validation
India KYC compliance for verified email addresses under PMLA regulations.
Read guides →Verification runs a chain of checks: syntax (RFC 5321), MX record lookup, then an SMTP probe that connects to the recipient mail server and issues RCPT TO without sending. If the server accepts the recipient, the address is treated as valid. Layered on top: disposable domain lists, role-account rules, catch-all detection, and known-trap databases.
No. Catch-all domains accept everything at the SMTP layer, so probing cannot distinguish real mailboxes from typos. Some providers block SMTP probes entirely and rate-limit verification traffic. Recycled spamtraps (once-real addresses now used as traps) also pass every technical check. Verification catches the majority of bad addresses; the last 5 percent needs list hygiene practices.
Every 3 to 6 months for active senders, more frequently for lists that go months between campaigns. Addresses decay: roughly 20 percent of a B2B list becomes invalid every year through job changes, provider closures, and abandonment. Re-verify before any major send to a segment that has not received mail in 90+ days.
Even a "verified" purchased list is dangerous. Verification confirms the address is technically deliverable; it says nothing about consent. Sending to purchased addresses without consent triggers complaints, spamtrap hits, and blocklist listings. GDPR and CAN-SPAM make this a legal risk in addition to a deliverability one.
Syntax check confirms the address format is legal per RFC 5321: correct local-part, valid domain characters, no forbidden syntax. It catches typos ("gmial.com") but does not confirm the mailbox exists. SMTP verification goes further: it looks up the domain MX record, opens a connection, and probes the recipient. A syntax check runs in microseconds; SMTP verification takes seconds and can be rate-limited by receivers.
Yes. ESP bounce handling catches invalid addresses after the send, when the damage is done: your IP has already made a delivery attempt, the receiver has already logged a failure, your reputation has already taken the hit. Pre-send verification catches the same addresses before they reach the receiver. For senders above a few thousand messages per day, both are needed.