Bulk Email Verifier — MX, Disposable & Deliverability avatar

Bulk Email Verifier — MX, Disposable & Deliverability

Pricing

from $0.70 / 1,000 results

Go to Apify Store
Bulk Email Verifier — MX, Disposable & Deliverability

Bulk Email Verifier — MX, Disposable & Deliverability

Verify thousands of emails at once: syntax, MX/domain check, disposable & role-based detection, free-provider flag and a deliverability score. Fast, cheap, keyless bulk email validation for lead lists and list cleaning.

Pricing

from $0.70 / 1,000 results

Rating

0.0

(0)

Developer

Haketa

Haketa

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Share

Bulk Email Verifier — Syntax, MX, Disposable & Deliverability

Verify thousands — or millions — of emails at once. Paste a list and get, for every address: syntax validity, MX/domain check, disposable & role-based detection, free-provider flag, and a deliverability score with a clear valid / risky / invalid status.

Fast, cheap and keyless — clean your lead lists before you send, and cut bounces.


Why this Actor?

A dirty email list wrecks your sender reputation: hard bounces, spam traps and wasted sends. Verifying emails one by one is slow, and most tools charge per credit. This Actor cleans a whole list at once — DNS-based, so it's fast and inexpensive at scale — and tells you exactly which addresses are safe to send to.

  • Clean lead lists before an outreach or newsletter campaign.
  • Cut bounce rate and protect sender reputation.
  • Enrich a CRM with deliverability status and flags.
  • Filter forms/signups by catching disposable and role-based addresses.

What you get

One record per email:

FieldDescription
emailThe address
statusvalid, risky, or invalid
isValidWhether it's a valid, deliverable address
deliverabilityScore0–100 confidence score
reasonWhy this status
domainEmail domain
syntaxValidPasses RFC syntax
hasMxDomain has MX records (can receive mail)
mxHostPrimary mail server
isDisposableDisposable / temporary domain
isRoleBasedRole address (info@, admin@, sales@…)
isFreeProviderFree provider (Gmail, Yahoo, Outlook…)
scrapedAtTimestamp

Example output

{
"email": "ceo@microsoft.com",
"status": "valid",
"isValid": "true",
"deliverabilityScore": "92",
"reason": "deliverable",
"domain": "microsoft.com",
"syntaxValid": "true",
"hasMx": "true",
"mxHost": "microsoft-com.mail.protection.outlook.com",
"isDisposable": "false",
"isRoleBased": "false",
"isFreeProvider": "false",
"scrapedAt": "2026-07-08T15:00:00.000Z"
}
  • bad@nonexistent-domain.cominvalid (no MX — the domain can't receive mail).
  • test@mailinator.comrisky (disposable domain).
  • info@company.comrisky (role-based).
  • john@gmail.comvalid (free provider).

How the status is decided

StatusMeaning
invalidBad syntax, or the domain has no MX record (cannot receive mail) — don't send.
riskyDeliverable domain but disposable or role-based — send with caution.
validGood syntax + real mail domain, not disposable, not role — safe to send.

The deliverabilityScore (0–100) gives you a single number to threshold on.


Input

FieldTypeDefaultDescription
emailsarrayRequired. The emails to verify (thousands to millions).
checkDisposablebooleantrueFlag disposable/temporary domains against an up-to-date blocklist of 7,900+ domains.
maxConcurrencyinteger50Emails verified in parallel.

Example

{
"emails": ["john@gmail.com", "info@company.com", "test@mailinator.com"],
"checkDisposable": true
}

Use cases in detail

1. Clean a lead list before outreach

Run your list, keep status: valid, drop invalid, and review risky — you'll cut bounces dramatically and protect your domain's reputation.

2. Reduce newsletter bounce rate

Verify subscribers before a big send; remove dead domains and disposables.

3. Enrich & segment a CRM

Add deliverabilityScore, isFreeProvider and isRoleBased to segment personal vs business vs role contacts.

4. Signup / form hygiene

Catch disposable and role addresses at the point of collection.


How to use it

  1. Click Try for free.
  2. Paste your emails.
  3. Click Start.
  4. Export results as JSON, CSV, Excel, or via the Apify API.

Runs are fast — domains are cached, so a big list resolves in seconds.


Calling from the API

curl -X POST "https://api.apify.com/v2/acts/YOUR_ACTOR_ID/runs?token=YOUR_APIFY_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "emails": ["john@gmail.com", "test@mailinator.com"] }'

Then fetch the dataset:

$curl "https://api.apify.com/v2/acts/YOUR_ACTOR_ID/runs/last/dataset/items?token=YOUR_APIFY_TOKEN&format=csv"

Works with webhooks, Zapier, Make and n8n.


Frequently asked questions

How does it check deliverability without sending? It validates syntax, checks the domain's MX records (whether it can receive mail at all), and flags disposable, role-based and free-provider addresses. This catches the large majority of bad addresses reliably.

Does it do SMTP mailbox verification? No — SMTP mailbox probing requires port 25 (blocked on virtually all cloud/hosting networks) and is unreliable anyway (catch-all domains, greylisting, false positives). This Actor gives you honest, fast, DNS-based verification instead of a flaky SMTP guess.

How many emails can it handle? Thousands to millions — domains are cached, so unique-domain lookups (not per-email) drive the work.

What's a role-based address? Addresses like info@, admin@, sales@ that go to a team, not a person — often lower engagement and higher spam-complaint risk.

Is the disposable list current? Yes — it fetches an up-to-date community blocklist (7,900+ domains) on each run, with a built-in fallback.


Tips

  • Threshold on deliverabilityScore (e.g. keep ≥ 80) for a quick clean.
  • Keep valid, drop invalid, review risky for the safest list.
  • Filter isRoleBased / isFreeProvider to separate business from personal contacts.

Notes

This Actor performs DNS/MX lookups and pattern checks on the emails you provide. It does not send mail. Verify that you have the right to process the email addresses you submit, in line with applicable privacy laws (GDPR/CAN-SPAM etc.).


Support

Want catch-all detection, SMTP (where possible), or another flag? Open an issue from the Actor's page.