简体中文
EnglishWhat Does an Email Verification Service Actually Check?
Updated
An email verification service checks several layers of an address, not just its spelling. At minimum, it confirms the syntax is valid, the domain exists and can receive mail (via MX records), and often whether the specific mailbox is deliverable through an SMTP handshake. Many services also flag disposable, free, or role-based addresses and return a status such as valid, invalid, unknown, or risky. The exact checks and result labels vary by provider, so treat any single result as a signal, not a guarantee.
The layers of an email verification check
Verification typically runs through a sequence, and each layer can stop the process early if it fails.
1. Syntax and format validation
The service parses the address against email standards: a local part, an @ symbol, and a domain. It catches obvious problems like missing @, illegal characters, or malformed domains. This is the cheapest check and the first filter.
2. Domain and DNS checks
The service looks up the domain's DNS records, especially MX (mail exchange) records, which tell the internet where to deliver mail for that domain. No MX records usually means the domain cannot receive email. Some services also check A records and DNS configuration as a secondary signal.
3. Mailbox-level (SMTP) verification
This is the deepest common check. The service connects to the recipient's mail server and starts an SMTP conversation, asking whether the specific mailbox exists. The server's response indicates whether the address is likely deliverable. This step is where results get less certain, because many servers refuse to answer, rate-limit, or give misleading responses to protect against spam and harvesting.
4. Risk and category flags
Beyond deliverability, services often label the address type:
- Disposable email domains — temporary addresses from throwaway providers.
- Free email domains — consumer providers (the provider's own database distinguishes these).
- Role-based addresses — generic mailboxes like
info@orsupport@that may not reach a specific person.
WhoisXML API, for example, offers a Disposable Email Domains Database and a Free Email Domains Database as separate products alongside its Email Verification API, so these categories can be checked independently of a live SMTP probe.
What the result statuses mean
Verification results usually fall into a small set of categories. The exact wording depends on the provider, but the meaning is broadly consistent:
| Status | What it usually means | Practical reading |
|---|---|---|
| Valid / deliverable | Syntax, domain, and mailbox checks passed | Safe to send, though not a guarantee of engagement |
| Invalid / undeliverable | A hard failure at syntax, domain, or mailbox level | Remove or suppress; sending risks bounces |
| Unknown / risky | The server would not confirm, or signals conflict | Treat cautiously; consider a re-check or a softer send strategy |
| Disposable / role / free | The address type is flagged | Decide based on your use case, not automatically discard |
The unknown category is the one people misread most often. It does not mean the address is bad. It usually means the receiving server declined to confirm the mailbox, which is common with large providers. A verification service cannot force an answer.
How to use verification results to decide whether to send
Verification is a decision input, not a verdict. A workable approach:
- Suppress invalid addresses before sending. Hard failures at the syntax or domain level rarely recover.
- Send to valid addresses as your primary audience.
- Handle unknown addresses deliberately. For transactional or high-value mail, you may still send; for bulk marketing, consider suppressing or segmenting them to protect sender reputation.
- Treat category flags as policy choices. A disposable address may be fine for a low-stakes signup and wrong for a paid account. A role address may be correct for a company contact form and wrong for a personal outreach list.
- Re-verify over time. Mailboxes go dormant and domains expire, so a result has a shelf life.
Why no single check is conclusive
SMTP verification depends on the receiving server's cooperation, and servers have strong incentives to be uncooperative. Catch-all domains accept mail for any address, so a "valid" response there is weak. Greylisting and rate limits can produce false negatives. This is why reputable services combine multiple checks and report a status rather than a binary yes/no, and why you should match the strictness of your sending to the cost of a bad address.
Where to start
WhoisXML API's Email Verification product line covers the checks described here through an Email Verification API, a web lookup, and a bulk validator, with disposable and free email domain databases available separately. The site lists a free trial and paid plans starting from $129/month, with separate API and database pricing pages; check current terms on those pages before committing, since pricing and trial conditions can change.