email · phone · whatsapp · bin · bulk
MultiValidator Features
Verify, validate and understand your data with transparent checks, detailed verdicts and developer-ready APIs.
More than a regex checker: every result carries the stages that produced it, so a verdict can be read instead of trusted blindly.
Everything you need to verify data.
One platform, several kinds of check. The email pipeline combines format, domain, mailbox and reputation signals into a single verdict — and each of the checks below returns its own result, so you can see which one moved it.
Email syntax validation
RFC-style parsing, normalization and length limits, before anything leaves the process. An address that will not parse stops here.
DNS / MX lookup
A live query for the domain's MX and A records. No mail route, no mailbox — the result is undeliverable with mx_not_found attached.
SMTP mailbox probe
A polite MAIL FROM / RCPT TO exchange that asks whether the mailbox is accepted, then closes. Nothing is sent to the mailbox.
Disposable email detection
Domains belonging to known throwaway providers are matched at the domain level, before any probe is attempted.
Role-based email detection
info@, sales@, support@ and their relatives are classified from the local part. A signal about the inbox, never a claim that the address is invalid.
Typo detection and suggestions
A domain one keystroke from a well-known provider comes back with a suggestion — jordan@gmil.com returns didYouMean: jordan@gmail.com. Applying it is your call.
Free-provider detection
gmail.com, outlook.com and friends are flagged as context, because consumer domains bounce at different rates to business ones. It is not a verdict.
Spam-trap heuristics
Trap-pattern addresses are flagged before they can damage sender reputation. A heuristic signal, not a register of every trap that exists.
Verdicts
Deliverable, risky, undeliverable or unknown — four states for email, and two of the other kinds use three of them because their datasets answer one way.
Verification score
Email scores are a weighted composition of the stage outcomes on a 0–100 scale. Phone, WhatsApp and BIN map each state to a fixed score instead.
The verdict rules are published rather than implied — what each state means and how the score is composed are both in the API documentation.
How MultiValidator verification works.
Eight stages run in order on an email address. Most resolve locally; one makes a live DNS query, one opens an SMTP handshake, and the last one is arithmetic over what came back.
Syntax
localRFC-5321/5322 parsing, normalization, length limits. Zero network calls.
DNS / MX resolution
live DNSA live lookup for MX and A records. No records, no mailbox: mx_not_found.
Disposable detection
provider listKnown throwaway providers matched at the domain level before any probe.
SMTP mailbox probe
SMTP handshakeA 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
heuristicFlags for trap-pattern addresses before they poison your sender reputation.
Role-account detection
heuristicinfo@, sales@, support@ — addresses that rotate, get shared, or go unread.
Free-provider flag
provider listgmail.com, outlook.com and friends bounce at higher rates; flagged as context, not a verdict.
Verdict + score
computeddeliverable / risky / undeliverable / unknown, a 0–100 score from the stage outcomes, and a didYouMean typo suggestion when one applies.
Stage names and behaviour come from the engine itself, so this list and the API’s per-stage output can never drift apart. A stage that is skipped is reported as skipped, not as passed.
The map, in two lanes.
Products run the full pipeline and return a verdict with its reasons. The free tools each answer one question, in your browser, with no account and no API key.
Products
full pipeline · the current per-check rateEmail Validation
Every verdict shows its work: syntax, DNS/MX, disposable, SMTP, spam-trap, role, score.
- syntax
- DNS
- SMTP
- score
Phone Validation
Line type, carrier, region and risk — with the reason attached.
- line type
- carrier
- risk
IIN/BIN Checker
Six digits resolve to a scheme, a funding type and an issuer.
- scheme
- funding
- issuer
- country
Bulk verification
CSV or JSON, thousands of rows, one verdict per row with live progress. Email queues; phone, WhatsApp and BIN return inline.
- CSV
- JSON
- auto-detected columns
- live progress
Free tools
free · no API key · no signupEach tool checks one thing and shows its working. Most parse locally in your browser; the DNS tools make a single public query and send no mail.
Email Health Check
One address, every local check: syntax, typo, DNS/MX, disposable, role, provider and spam-trap, with an honest local score.
- 7 stages · free
MX Record Lookup
Does this domain accept mail at all? A live DNS query for MX and A records — nothing sent.
- live DNS
DMARC Checker
One TXT query at _dmarc.<domain>, read tag by tag: policy, reporting and alignment.
- DNS · local parse
Disposable Email Detector
Throwaway domains, matched against a known provider list before they inflate your list.
- provider list · local
Role-Based Email Checker
info@, sales@, support@ — addresses that rotate or go unread. Context, not a verdict.
- heuristics · local
Phone Lookup
Parse a number for its country, calling code, formats and type, in your browser.
- parsing · local
WhatsApp Checker
Check whether one number is registered on WhatsApp — with an honest unknown when the provider cannot answer.
- registration · server
Reverse Phone Lookup
Start from a number and read its numbering metadata — with the owner boundary stated plainly.
- metadata · local
Phone Number Formatter
Paste a number once and get the international, national and E.164 forms back.
- formatting · local
HLR Lookup
Numbering metadata for a number. No HLR provider is wired in, so it reports no carrier or network status.
- parsing · local
IIN/BIN Checker
Read and validate a card BIN locally. The free issuer dataset is still being prepared, and the tool says so.
- local read · no dataset yet
One engine, behind all of it.
The free tools are single stages pulled out for convenience. The products run the whole pipeline and hand back every stage’s reason, which is what the API returns too.
The chain below is what the pipeline exists to prevent — send to addresses nobody cleared, and the damage runs through your sender reputation.
Built for every verification workflow.
The same engine, pointed at the five places verification actually happens.
Signup validation
Check an address before it becomes a row in your users table, so a typo never costs you the account.
- Syntax
- DNS/MX
- Disposable
- Role
- SMTP probe
CRM and lead hygiene
Clean an imported list before a campaign or a CRM sync, one verdict per row.
- Bulk verification
- CSV upload
- Verdicts
- Reason codes
Campaign preparation
Find the addresses that need review before you send, rather than after the bounce report.
- Deliverability signal
- Disposable
- Role
- Risky / undeliverable
Transactional email protection
Validate the address at the point it is captured, so account mail is not the first place a typo shows up.
- Real-time API
- Typo suggestions
- Verdict
- Score
Developer integrations
Wire verification into an application and read the result as data rather than a boolean.
- REST API
- Bearer keys
- Structured JSON
- Webhooks
Built for developers.
The API is the same engine the dashboard runs — not a smaller version of it. Everything below is implemented and documented; nothing is planned-for.
One verification endpoint
POST /api/v1/verify handles email, phone, WhatsApp and BIN, selected by the kind field. The synchronous path returns a verdict in one round trip.
Bearer authentication
The same API keys the dashboard issues. Send them as Authorization: Bearer mv_<64 hex> and every request is attributed to your account.
Structured JSON
The state, the score, the credits consumed and the per-stage detail come back together, so a result can be stored and audited rather than re-derived.
Reason codes per stage
A failed check carries the reason string that produced it — mx_not_found, 'Missing @ symbol', a raw SMTP response code — instead of a bare false.
Latency on every response
latencyMs is returned with the result, so you can measure the pipeline in your own environment rather than trusting a claim about it.
Webhooks and retries
Subscribe an endpoint and receive verification.completed and bulk.completed events, signed with an HMAC header and retried on a fixed schedule when delivery fails.
Bulk submission in the same API
Post a list to /api/v1/bulk, then poll status or download the finished file. Email queues; phone, WhatsApp and BIN return completed payloads inline.
Documented errors and rate limits
Every error code is listed with the condition that raises it, and rate-limited responses carry an X-RateLimit-Reset header.
SDKs and an MCP server are listed as upcoming in the documentation, and they are not presented here as available.
Verify lists at scale.
Bulk verification runs the same engine as a single call, over a file rather than a value — with one verdict, score and reason per row.
- Upload a CSV and let the mapper detect which column holds which kind — email, phone, WhatsApp or BIN headers are recognised automatically.
- Rows are processed against the same engine as the API, so a row's verdict matches what a single call would have returned.
- Email jobs queue: a job id, live progress, and a results file to download when the run finishes.
- Phone, WhatsApp and BIN payloads skip the queue entirely and come back completed on the submission itself.
- Every row carries its own verdict, score and reason, and the finished run keeps state totals for the file.
- Credits are per processed row — charged per row at the current rate — with no quality selector to pick.
Every verdict shows its work.
A result is not a boolean. Below is the shape of one, with the fields the API actually returns — the state, the score, the stage outcomes and the suggestion when there is one.
one result
amy@verisend.example
- state
- risky
- didYouMean
- null
- latencyMs
- 214
- creditsConsumed
- 0.25
Risky because the mailbox greylisted the probe. The address may be perfectly good — the verdict reports what happened, not a prediction.
stages
- syntaxpass — normalizedEmail returned
- dnspass — hasMxRecord true
- disposablepass — not a known throwaway domain
- smtppass — responseCode 450, isGreylisted true
- spam-trappass — isSpamTrap false
- rolepass — isRole false
- free-emailpass — isFreeEmail false
Stage objects carry pass and, on failure, the reason string. A skipped stage is reported as skipped. Full field list in the response schema.
More than an email syntax checker.
Both work on the same string. Only one of them leaves the browser.
Syntax checking
Answers one question: does this address look structurally valid? It is fast, free and local — and it is the first stage of the pipeline, not a substitute for it.
- Format and RFC-style structure
- Length limits
- Normalized form
- Typo suggestion when a domain is one keystroke off
Try it: email health check
Full verification
Adds everything that needs the network: does the domain route mail, is the mailbox reachable, is the domain disposable, is the inbox a role account — then maps those answers to a verdict.
- Syntax, DNS/MX and the SMTP probe
- Disposable, role, free-provider and spam-trap signals
- A verdict, a score and the reason behind each stage
- The same engine in the API and in bulk
Read more: email validation
Which one do I need?
One row per starting point, and one destination each.
| You have | Use |
|---|---|
| One address, before you hit send | Email Validation/products/email-validation |
| A whole list from a spreadsheet | Bulk verification/products/bulk-verification |
| A phone number you need the line type of | Phone Validation/products/phone-validation |
| The first six digits of a card | IIN/BIN Checker/products/bin-checker |
| A domain — can it receive mail at all? | MX Lookup/tools/mx-lookup |
| A domain — what DMARC policy does it publish? | DMARC Checker/tools/dmarc-checker |
| An info@, sales@ or support@ address | Role Checker/tools/role-checker |
Transparent by design.
What a verification result is, and what it is not. These are the limits of the method, kept on the page rather than in a footnote.
- A result describes the checks that ran at that moment. Mail servers change behaviour, so a verdict is a snapshot rather than a standing fact.
- SMTP servers throttle, greylist and block probes. When one refuses, the response code is returned and the verdict reflects it instead of guessing.
- A catch-all domain accepts every address, which makes individual mailbox existence impossible to prove. The pipeline says so rather than pretending otherwise.
- Risky is not a softer word for invalid. A greylisted, disposable or role address may deliver perfectly well.
- Unknown means no definitive answer came back. Reporting it as valid would be a fabrication.
- Provider behaviour changes, and coverage varies by region, so a dataset answer is only as current as the dataset.
- Verification is not a guarantee of future delivery: inbox placement depends on the receiver's filtering on the day you send.
- No claim of perfection is made anywhere on this site — not 100% accuracy, not zero false positives or negatives.
On the roadmap, and marked as such.
These are not available yet, and we will not pretend otherwise. They sit here so you know what is coming rather than guessing from a footer link — when one ships it moves up into the map above.
- IP lookupupcoming
- Domain intelligenceupcoming
- Domain authorityupcoming
- Domain ageupcoming
- Carrier lookupupcoming
- VIN decoderupcoming
Nothing in this band has an endpoint, a response shape or a route. The IP half of the domain lookup is the clearest example: the domain half is live, the IP half is here.
MultiValidator features FAQ.
What the platform verifies, how each check works, and what it deliberately does not claim.
Email addresses, phone numbers, WhatsApp numbers and card BINs. Email runs the full pipeline — syntax, DNS/MX, disposable, SMTP, spam-trap, role and free-provider checks — and returns a verdict, a score and a reason. Phone, WhatsApp and BIN resolve against provider datasets and return line type and carrier, WhatsApp registration, or scheme, funding and issuer.
Related free tools
Each tool checks one layer. To run the full pipeline — MX lookup, live SMTP probe and catch-all detection with a reason and a score — use the API.
Stop mailing ghosts.
Start with free credits. No card, no call, no “book a demo”.