How to verify emails before sending
Syntax checks, MX record lookups, and SMTP verification each catch a different kind of failure. A list sent without any of them risks a bounce spike that damages sender reputation on the first real send.
The short answer
- A syntax check confirms an address is formatted correctly but says nothing about whether the mailbox exists. A large share of invalid addresses pass syntax validation and still bounce on send.
- An MX record lookup confirms the domain can receive email at all. It catches addresses at domains with no working mail server, a different failure from a syntax error or a nonexistent mailbox at a working domain.
- SMTP verification checks whether a specific mailbox exists on a working domain. Some larger mail providers deliberately give ambiguous or false-positive responses to this check as an anti-spam measure, which limits its accuracy for those domains.
- Verification decays over time, even on a list checked previously. Addresses go stale as people change jobs. Re-verifying before a significant send catches decay that built up since the last check.
Why one verification method is not enough
Email verification happens in layers, and each layer catches a different kind of invalid address. A syntax check is the simplest. Does the address follow the basic format of a username, an @ symbol, and a domain? This catches obvious typos and malformed entries. It says nothing about whether the domain exists or whether that mailbox is real. A perfectly formatted address at a domain with no mail server, or at a domain with no such mailbox, still passes a syntax check cleanly.
An MX record lookup checks the next layer. Does the domain in the address have a configured mail server able to receive email at all? This catches addresses at domains that look plausible but have no working mail infrastructure. It is a less common failure than a typo, but it still produces a bounce if not caught beforehand.
SMTP verification goes further. It connects to the domain's mail server and asks whether a specific mailbox exists, without sending a real message. This catches nonexistent mailboxes at otherwise-working domains, the most common real-world failure. Its accuracy is not perfect. Some larger providers deliberately respond ambiguously or with false positives, to stop the check being used to harvest which addresses are real. That limits how much this layer alone can be trusted for those domains.
Verification layers and what each catches
| Layer | Catches | Limitation |
|---|---|---|
| Syntax check | Malformed or obviously invalid addresses | Says nothing about whether the mailbox exists |
| MX record lookup | Domains with no working mail server | Does not confirm a specific mailbox exists on a working domain |
| SMTP verification | Nonexistent mailboxes on working domains | Some large providers give deliberately ambiguous responses |
What to actually do before a real send
Run all three layers together rather than relying on one. Each catches failures the others miss. Treat addresses that fail SMTP verification on providers known to give ambiguous responses with more caution than a hard rejection. A false negative there can mean a good address gets discarded for no reason. Re-verify an existing list before a significant send if it has been more than a few months since the last check. Staleness builds up even on a previously clean list.
Disclosure: SalesCrew is our product. Its data bank holds and segments imported and scraped contact data, and suppression is enforced at send time. Email verification itself, running addresses through syntax, MX and SMTP checks before a first send, happens outside the product. A dedicated verification service does it before the list reaches the data bank.
A high bounce rate from one bad batch damages reputation for every future send
Questions
- Is a syntax check (does the address look valid) enough verification?
- No. A syntax check confirms an address is formatted correctly, like name@domain.com. It says nothing about whether that mailbox exists. A large share of invalid addresses pass a syntax check and still bounce on send.
- What is SMTP verification, and why is it not always reliable?
- SMTP verification connects to the receiving mail server and asks whether a specific mailbox exists, without sending an email. Some mail servers, especially larger providers, deliberately give ambiguous or false-positive answers as an anti-spam measure. That limits its accuracy for those domains.
- How often should an existing list be re-verified?
- Periodically. Email addresses go stale over time even on a previously verified list, as people change jobs or companies get acquired. Re-verify before a major campaign, rather than relying on a check done months earlier.