Email Verification: the Layers, and What They Can Tell You
Reviewed: 18 September 2026
“Email verification” is not one check. Tools use several layers, each answering a different question, each with its own certainty. Knowing the difference stops you from trusting a result for more than it is worth.
The five layers
1. Syntax check. Is the string a validly formatted address (one @, plausible local part and domain)? Fast and local. It cannot tell you whether the address exists.
2. Domain and MX check. Does the domain exist and publish mail (MX) records? A domain without mail records cannot receive your campaign. Still no guarantee about the specific mailbox.
3. Disposable check. Is the domain a known throwaway provider? Domain-level only; a non-listed domain is not proof of a real mailbox.
4. Catch-all detection. Does the domain accept mail to any address? On catch-all domains, mailbox-level answers are unreliable, so results there are inherently uncertain.
5. Mailbox verification (optional, external). Does this specific mailbox accept mail? This is the only layer that looks at the individual mailbox. ListGuard offers it as an explicit option through your own ZeroBounce or Hunter.io key: only the addresses you choose to verify are sent to that provider, and this is the only situation in which addresses leave our infrastructure.
How ListGuard fits in
Core cleaning in ListGuard covers layers 1–4 natively: syntax, domain/MX, disposable and catch-all handling run on our own European infrastructure, and your list is not stored after cleaning. Layer 5, mailbox verification, is strictly optional and runs through your own ZeroBounce or Hunter.io account.
What no verification can promise
Every layer, including mailbox verification, is a point-in-time answer. A verified mailbox can still full later, a catch-all answer is probabilistic, and spam traps do not announce themselves. Treat verification as risk reduction before a send, not as a guarantee — a mailbox that verifies today can still bounce next month. Keep bounce handling and suppression in place. See how suppression works and the security and methodology page for the full data flow.