Bulk Email Verifier & Validator: MX, Disposable and Role Check

Clean your email list in seconds, before you send. Paste thousands of addresses and get one result per email: valid syntax, whether the domain exists and accepts mail (MX records), disposable or temporary inbox detection (9,900+ known providers), role addresses (info@, sales@, support@), free-provider flag (Gmail, Yahoo, Outlook…), typo suggestions (jane@gmial.com → jane@gmail.com) and SPF/DMARC presence. Every address gets a simple status and a 0–100 score.

• ⚡ Fast: 2,000 emails checked in about 5 seconds, with DNS results cached per domain
• 💸 Cheap: pay per email checked, no start fee, no subscription. Duplicates are removed for free
• 🧹 Practical: catches typos, dead domains and throwaway inboxes, the main causes of bounces and fake sign-ups
• 🤖 Agent-ready: simple input and output, fixed price per email, works from the API and the Apify MCP server

What does it check?

Check	Field
RFC syntax, length and international (IDN) domains	syntaxValid
Domain exists, MX records, null-MX, A-record fallback	domainExists, hasMx, mxRecords
Disposable / temporary email providers	disposable
Role or shared inboxes	roleAccount
Free webmail providers	freeProvider
Common domain typos	didYouMean
SPF and DMARC records	hasSpf, hasDmarc

Status values

• deliverable_domain: the syntax is valid and the domain accepts email. The individual mailbox is not tested (see FAQ).
• risky: disposable provider, role address, probable typo, or no MX record.
• undeliverable: invalid syntax, the domain does not exist, or the domain refuses email.
• unknown: DNS timed out. Not common; re-run these addresses.

Input example

{ "emails": ["john.doe@gmail.com", "info@apify.com", "someone@mailinator.com", "jane@gmial.com"] }

Output example

{
  "email": "jane@gmial.com",
  "status": "risky",
  "score": 0,
  "reason": "possible typo, did you mean jane@gmail.com?",
  "domain": "gmial.com",
  "hasMx": false,
  "disposable": true,
  "roleAccount": false,
  "freeProvider": false,
  "didYouMean": "jane@gmail.com",
  "mailboxVerified": false
}

Use it from the API or with AI agents

curl -X POST "https://api.apify.com/v2/acts/poised_beardlichen~email-verifier-bulk/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" -d '{"emails": ["john.doe@gmail.com"]}'

AI agents can call it through the Apify MCP server with https://mcp.apify.com/?tools=poised_beardlichen/email-verifier-bulk. It also works with Make, Zapier, n8n and Google Sheets through Apify integrations.

Pricing

Pay per unique email checked, with no start fee. Set Maximum cost per run and the Actor stops cleanly at your limit.

FAQ

Does it check whether the mailbox really exists? No. Mailbox checks need an SMTP connection on port 25, which cloud platforms block, and many big providers (Gmail, Outlook, Yahoo) don't reveal it reliably anyway. This Actor confirms that the address is well formed and that the domain can receive email, and it flags disposable, role and typo addresses. That is why mailboxVerified is always false. Tools that claim full mailbox checks charge much more.

Where does the disposable list come from? From the community-maintained, public-domain disposable-email-domains project, plus a free-provider list from free-email-domains (MIT).

Is it safe for my list? Yes. No email is ever sent to your contacts, and the Actor only performs DNS lookups on the domains. Results stay in your own Apify storage.

How many emails can I check? Up to 1,000,000 per run. Larger lists can be split across runs.

Do duplicates cost extra? No. With Remove duplicates on (the default), repeated addresses are skipped.

Calling it from an AI agent or a script (async pattern)

A single email finishes in a few seconds; 10,000 emails take a few minutes. The Apify MCP server waits only about 30–45 seconds for a run before it returns. So for batches, slow pages, or whenever a call returns before the run is done, start the run and fetch the results afterwards rather than waiting on it:

1. Start the run: POST https://api.apify.com/v2/acts/poised_beardlichen~email-verifier-bulk/runs with input such as {"email": "jane@gmial.com"}. The response contains data.id (the run ID) and data.defaultDatasetId.
2. Wait for it to finish: poll GET https://api.apify.com/v2/actor-runs/<runId>?waitForFinish=60 until status is SUCCEEDED.
3. Fetch the results: GET https://api.apify.com/v2/datasets/<defaultDatasetId>/items?clean=true.

Send your token as Authorization: Bearer <APIFY_TOKEN>. Through MCP, if the call returns a run ID instead of results, use the server's run-status and dataset tools (e.g. get-actor-run, then get-dataset-items) with that ID. For small, quick jobs you can use the synchronous endpoint POST /v2/acts/poised_beardlichen~email-verifier-bulk/run-sync-get-dataset-items instead, which waits for up to 300 seconds.

Other tools by us

• PDF to Text & Markdown with OCR: turn PDFs, DOCX and scans into clean, LLM-ready text.
• Website Screenshot & PDF API: bulk screenshots and PDFs with cookie banners removed.
• Image to Text OCR API: extract text from PNG, JPEG, TIFF and WebP images in 27 languages, at $1.50 per 1,000 images.
• Bulk PageSpeed & Lighthouse Checker: Lighthouse scores, Core Web Vitals and top fixes for many URLs on mobile and desktop, from $0.005 per audit.
• Website Screenshot & PDF for AI Agents: a lightweight copy of the screenshot tool for agents and one-off calls (no Standby). Same prices, starting at $0.0015 per screenshot.

Support

Spotted a wrong result or a missing disposable domain? Open an issue on the Issues tab.