Bulk Email Verifier - MX, Disposable, Role & Deliverability

Clean an email list before you send. Paste or upload addresses and get, for each one, whether the format is valid, whether the domain can actually receive mail (MX), whether it is a disposable or role-based address, which mail provider runs it, and a likely-typo suggestion - plus a single status and a 0-100 confidence score you can sort and filter on.

No browser, no proxy, no anti-bot target: every check is DNS plus local logic, so runs finish in seconds and cost a fraction of a cent per address.

What each check means (read this - it is honest about the limits)

Field	What it tells you
status	deliverable · risky · undeliverable · unknown - the headline verdict
score	0-100 confidence, combining every signal below
formatValid	The address passes RFC-shaped syntax and length rules
mxFound / mxHost	The domain publishes an MX (or A) record, so it can receive mail, and the primary mail host
mailProvider	Who runs the mail: Google Workspace, Microsoft 365, Zoho, Proton, Proofpoint, and more
isDisposable	The domain (or its MX operator) is a throwaway/temporary-mail service
isRoleBased	A shared address like info@, support@, sales@ - not a specific person
isFreeProvider	A consumer mailbox (gmail, outlook, yahoo, ...)
didYouMean	A likely typo fix, e.g. user@gmial.com -> user@gmail.com
normalizedEmail	Canonical form for de-duping (gmail dots and +tags removed)
smtpChecked / smtpAccepted	Optional: the result of a live mailbox handshake (see below)

About mailbox-level verification. Confirming that a specific mailbox exists needs a live SMTP handshake on port 25, which most cloud platforms (Apify included) block to prevent abuse. So by default this actor verifies domain-level deliverability and address hygiene - a deliverable result means the address is well-formed and its domain accepts mail and is not disposable or role-based, which is exactly what you need to cut bounces from a list. Turn on Attempt SMTP mailbox check to try the handshake anyway: where the platform allows it, results are upgraded to a confirmed mailbox; where it does not, they degrade silently to the DNS verdict and nothing fails.

Input

{
  "emails": ["jane.doe@gmail.com", "info@acme.com", "hello@mailinator.com"],
  "smtpCheck": false,
  "maxItems": 1000
}

• Emails - one per line. Or leave empty to get a small free sample.
• Import emails from a file - paste a whole list, or link a public .txt/.csv, a Google Sheet/Drive share link, or an Apify key-value-store record. Blank lines, # comments, quotes and extra CSV columns all parse.
• Output fields - tick only the fields you want for a lean CSV/Sheets export.

Output (one row per address)

{
  "email": "info@acme.com",
  "status": "risky",
  "score": 70,
  "formatValid": true,
  "mxFound": true,
  "mxHost": "aspmx.l.google.com",
  "mailProvider": "Google Workspace",
  "isDisposable": false,
  "isRoleBased": true,
  "isFreeProvider": false,
  "didYouMean": null,
  "reason": "role-based address (not a specific person)"
}

Use with AI assistants (MCP)

This actor is available through the Apify MCP server, so an AI assistant or agent can call it as a tool - hand it a list of addresses and get back a clean, scored dataset it can act on (drop the undeliverables, flag the disposables, keep the deliverables).

Agent-ready: autonomous payments (x402 & Skyfire)

This actor is agent-ready - AI agents can discover it, run it, and pay for it autonomously, with no Apify account and no human in the loop. It uses pay-per-event pricing and limited permissions, so it qualifies for Apify's agentic-payment standards:

• x402 - an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the Apify MCP server - no account, no API key.
• Skyfire - agent-to-service payments for fully autonomous AI-agent workflows.

Building an AI agent, MCP tool, or autonomous data pipeline? This scraper is ready to plug in and pay as it goes.

Notes

• Verification is based on public DNS and address structure; a deliverable result reduces bounce risk but is not a guarantee that a person reads the mailbox.
• Disposable and role lists are maintained inside the actor and matched against the live MX host, so vanity domains that resolve to a throwaway provider are still caught.