Email verification is the process of checking whether an email address exists and is safe to send to — without sending an actual email. This guide explains every stage, from syntax to machine learning.
Email verification is the process of checking whether an email address is formatted correctly, belongs to an active domain with valid MX records, and maps to an existing mailbox on the receiving mail server — without sending an actual email.
The verifier checks that the email address is formatted correctly: a local part, an @ symbol, a domain, and a valid TLD. This catches obvious typos like "[email protected]" or "userdomain.com". Syntax errors are detected in milliseconds without any network request.
The verifier queries DNS to confirm the domain exists and has Mail Exchange (MX) records pointing to a mail server. If there are no MX records, no server is configured to receive email for that domain — the address is invalid regardless of whether the mailbox exists.
The verifier connects to the mail server via SMTP (the protocol used to send email) and performs a RCPT TO command — asking the server if the specific mailbox exists. The server responds with 250 (exists), 550 (does not exist), or accepts all (catch-all). No email is sent; the connection closes after the check.
The verifier checks additional signals: Is the address a known spam trap? Is the domain disposable (Mailinator, Guerrilla Mail)? Is it a role address (info@, admin@, noreply@)? Has the domain or address appeared in breach databases? These signals determine if the address is risky to send to even if it exists.
For ambiguous addresses — especially catch-all domains where the SMTP server accepts everything — machine learning models score deliverability based on 40+ signals including domain age, sending history patterns, MX provider reputation, and social profile presence. This converts uncertain results into actionable likely_valid or likely_invalid classifications.
valid
Deliverable
The mailbox exists and the server accepted it. Safe to send to.
invalid
Do Not Send
The mailbox does not exist or the domain does not receive email. Sending will hard-bounce.
catch_all
Send With Caution
The server accepts all addresses (catch-all). Mailbox may or may not exist. Use ML score to decide.
risky
Evaluate Carefully
Address exists but shows risk signals — role-based, disposable domain, or spam trap pattern. May harm sender reputation.
unknown
Verify Again
The server did not return a definitive response (greylisted or temporarily unavailable). Retry later.
likely_valid
Probably Safe
ML predicts deliverable based on 40+ signals. Confidence typically >70%.
Every invalid address in your list is a potential hard bounce. ESPs (Mailchimp, SendGrid, ActiveCampaign) monitor bounce rates closely. Above 2% hard bounce rate, most ESPs throttle or suspend your sending account.
Spam traps — addresses maintained by ISPs and anti-spam organizations to catch bulk senders — look like normal addresses but cause immediate IP or domain blacklisting when emailed. They cannot be identified from the address alone; verification services cross-reference them against continuously updated databases.
Email verification removes invalid, risky, and trap addresses before sending — keeping bounce rates below 0.5%, protecting your sender reputation, and ensuring inbox placement remains high.
Email verification is the process of checking whether an email address is valid, deliverable, and safe to send to without sending an actual email. It checks syntax, domain DNS records, SMTP server response, and risk signals like spam traps and disposable domains.
Email validation checks syntax only — is the format correct. Email verification goes further: it confirms the domain has MX records and the specific mailbox is active on the receiving server. Verification is a superset of validation.
Single-address verification takes 0.5–5 seconds depending on the mail server response time. Bulk verification of 10,000 addresses typically takes 5–15 minutes with parallel SMTP connections. BounceZero caches previously verified addresses for near-instant repeated lookups.
Yes. Email verification services cross-reference addresses against continuously updated spam trap databases maintained by anti-spam organizations. BounceZero also uses pattern-matching ML to identify addresses that exhibit spam trap behavior even if not yet in the database.
Email verification does not process personal data in a way that requires GDPR consent under most interpretations — it queries mail servers in the same way a sending MTA would. BounceZero is UK ICO registered and stores verification results under UK GDPR. For large-scale processing, consult your DPO.
5-stage pipeline. 40+ signals per email. 100 free verifications.
| Feature | BounceZero | Typical alternative |
|---|---|---|
| Deliverable | Mailbox exists, SMTP confirmed, no risk signals | Safe to include in campaigns |
| Risky — catch-all | Domain accepts all mail; individual mailbox uncertain | Send in small batches with bounce monitoring |
| Risky — role address | Shared inbox (info@, support@, admin@) | Exclude from marketing; flag for manual review |
| Risky — disposable | Temporary inbox (Mailinator, TempMail, etc.) | Block at signup; remove from lists |
| Undeliverable — invalid | No DNS/MX record, or SMTP confirms non-existence | Suppress permanently — never mail again |
| Undeliverable — spam trap | Known spam trap address | Remove immediately; investigate list source |
Two different tools for two different moments in the sender workflow
Integrate BounceZero's API at signup forms, checkout flows, or CRM entry points. The API responds in under 400ms — fast enough to validate before form submission. Block invalid and disposable addresses at the source. Prevents bad data from entering your systems in the first place.
Upload a CSV of your full list before any major send. BounceZero processes at 10,000 emails per minute. A 50K list is done in 5 minutes. Remove all Undeliverable results, segment Risky catch-all addresses for separate monitoring. Run before every campaign on lists older than 90 days.
Even real-time verified lists decay. Contacts change jobs, abandon accounts, or change providers after you first captured their address. Quarterly bulk verification on your full database keeps bounce rate below 0.5% year-round and prevents the gradual accumulation of invalid addresses that eventually triggers ISP throttling.
Deep-dive guides on how email verification and inbox placement work
The RCPT TO handshake explained — codes, catch-alls, limits
Why domains accept everything and how ML classifies deliverability
Temp addresses, how to detect them, and why they matter
Hard vs soft bounces, SMTP codes, and how to fix them
Get from 5-15% to under 0.5% in 6 steps
Authentication, list hygiene, IP warmup, ISP monitoring
Follow BounceZero