Email Validation & Verification API
Every verdict shows its work.
Verify email addresses with syntax, DNS/MX, SMTP mailbox checks, disposable email detection, role-based detection, typo suggestions, and transparent deliverability scoring.
Email validation checks
Eight stages run against every address. Each one reports what it did and what it found, so a verdict can be read line by line.
Syntax
RFC-5321/5322 parsing, normalization, length limits. Zero network calls.
DNS / MX resolution
A live lookup for MX and A records. No records, no mailbox: mx_not_found.
Disposable detection
Known throwaway providers matched at the domain level before any probe.
SMTP mailbox probe
A polite MAIL FROM / RCPT TO exchange — nothing is ever sent. Hosts may refuse; when they do, you get the raw response code.
Spam-trap heuristics
Flags for trap-pattern addresses before they poison your sender reputation.
Role-account detection
info@, sales@, support@ — addresses that rotate, get shared, or go unread.
Free-provider flag
gmail.com, outlook.com and friends bounce at higher rates; flagged as context, not a verdict.
Verdict + score
deliverable / risky / undeliverable / unknown, a 0–100 score from the stage outcomes, and a didYouMean typo suggestion when one applies.
Stages run in parallel where safe — the SMTP probe only fires when syntax and DNS pass.
DNS / MX — stage 02, drawn
A live lookup, drawn as the tree it is. Records found, the probe proceeds; none found, the verdict stops here with mx_not_found.
SMTP — stage 04, drawn
The mailbox probe is a polite exchange that stops at RCPT TO. Nothing is ever sent — and when a server refuses, you get the raw code.
Typos — the suggestion stage
The domain fix list (gamil, gmial, gmai, hotmial…) produces a didYouMean suggestion. We flag it; you decide — the verdict never silently rewrites the address.
What is email validation?
Email validation is the process of checking whether an email address is properly formatted, connected to a valid mail domain, and supported by available mailbox signals. MultiValidator combines syntax validation, DNS and MX checks, SMTP mailbox probing, disposable email detection, role-based detection, typo detection, and other signals to provide a clear verification result.
Instead of relying on a single check, MultiValidator evaluates multiple stages and returns a deliverability status, quality score, and reason code for each verification.
what that covers
- Syntax, normalization and length limits — run locally.
- DNS and MX record lookup for the domain.
- An SMTP mailbox probe, a disposable email checker, role detection and typo suggestions.
How email verification works
Four steps, in order. Each one can end the run early — a domain with no mail records never reaches the mailbox probe.
Check email syntax
First, MultiValidator checks the structure, formatting, normalization, and length of the email address.
Check DNS and MX records
The domain is checked for DNS and mail-exchange records to determine whether the domain is configured to receive email.
Verify mailbox signals
When supported by the receiving server, MultiValidator performs an SMTP mailbox probe without sending an actual email.
Return a verification result
The verification combines the available signals into a verdict, quality score, and reason code so developers can understand why an address received its result.
Email verification API for developers
Integrate email verification directly into your application with the MultiValidator Email Validation API. Verify email addresses programmatically and receive structured results for syntax, DNS/MX, SMTP, disposable, role-based, typo, and deliverability-related checks.
Use the API for signup validation, lead capture, CRM data cleaning, transactional workflows, and email list verification — or run a whole file through bulk email verification.
One call, every reason.
Every verdict ships with the stage results that produced it. If you disagree with a verdict, you can see exactly which rule fired — and re-run the row.
$ curl -X POST https://api.multivalidator.io/api/v1/verify \ -H "Authorization: Bearer mv_<64 hex>" \ -H "Content-Type: application/json" \ -d '{"email": "sarah@bounced-host.example"}'{ "email": "sarah@bounced-host.example", "state": "undeliverable", "qualityScore": 0, "stages": { "syntax": { "pass": true, "normalizedEmail": "sarah@bounced-host.example" }, "dns": { "pass": false, "reason": "Domain has no MX or A records" }, "disposable": { "pass": true, "isDisposable": false, "domain": "bounced-host.example" } }, "didYouMean": null, "latencyMs": 214}
Four verdicts, in practice.
Illustrative rows — the shape of what comes back, with the reason that shipped on each one.
| Address | State | Score | Reason |
|---|---|---|---|
| sarah@bounced-host.example | undeliverable | 0.0 | mx_not_found |
| jordan@gmil.com | risky | 61.0 | did_you_mean |
| info@starter.example | risky | 48.0 | role_address |
| user@10minutemail.example | undeliverable | 0.0 | disposable_domain |
| amy@verisend.example | deliverable | 97.0 | smtp_accept |
| contact@relay-guarded.example | unknown | — | probe_refused |
Sample data for illustration — the shape is real, the rows are not. The score is a probability computed from the stages, never a guarantee of deliverability.
Where those scores come from
The 0–100 score is the sum of seven stage weights. A greylisted probe, for example, earns 80 of the 100 points and lands risky — the marker below shows exactly where that verdict sits.
Where email validation helps
The same pipeline, pointed at the places addresses enter your systems — and at the lists you already hold.
Validate signup emails
Check email addresses during registration to reduce malformed, disposable, and problematic addresses entering your user database.
Clean email lists
Verify existing contact lists before campaigns, outreach, or CRM imports.
Improve CRM data quality
Identify invalid, risky, disposable, or role-based addresses before they enter sales and marketing workflows.
Reduce email bounce risk
Detect addresses and domains that may create delivery problems before sending campaigns.
Validate leads
Check lead email addresses before sales outreach so your team can work with cleaner contact data.
Verify emails in real time
Use the API to verify addresses instantly during forms, applications, onboarding, and other workflows.
Start with the API documentation, the email health checker, the role checker or pricing — or read how bulk verification works.
Email validation vs. email verification
Email validation typically starts with checking the format and domain configuration of an address. Email verification can include additional signals such as DNS, MX, and SMTP mailbox checks to assess whether the address appears reachable.
MultiValidator combines multiple validation and verification signals into a single result, making it easier to understand the condition of an email address before using it.
Email validation
- Syntax
- Format
- Domain
- DNS/MX
Email verification
- Syntax
- DNS/MX
- SMTP signals
- Disposable detection
- Role detection
- Additional verification signals
Known limits
Catch-all servers can accept a probe for an address that doesn't exist. We flag the server; we can't read its mailboxes from the outside.
Gmail, Outlook and similar providers throttle SMTP probing. A refused probe returns risky/unknown with the response code — never a confident invalid.
A score is a probability, not a promise — deliverability depends on the receiver's filtering on the day you send.
Re-running a row costs another credit — and can legitimately land differently. Providers throttle probes, greylists clear, and the reason code on each row tells you exactly which rule fired and why the answer changed.
Email validation FAQ.
The questions this pipeline gets asked most — answered the same way the API answers them.
Email validation checks whether an email address has a valid structure and whether its domain and available mail-server signals indicate that it may be able to receive email.
Stop mailing ghosts.
Start with free credits. No card, no call, no “book a demo”.