Bulk Email Verifier — $0.50 / 1,000 emails

Clean your email lists before you send. Paste up to 100,000 addresses (or point the actor at any other actor's results) and get one clean record per email: a valid / risky / invalid / unknown status, a 0–100 quality score, the reason behind the verdict, and a did-you-mean fix for typo'd addresses — at $0.50 per 1,000 emails, with malformed rows checked free.

Lower bounce rates protect your sender reputation, keep you out of spam folders, and stop you paying your email platform for dead contacts.

What we check — and what we don't

We check: syntax and normalization · typo detection with did-you-mean fixes · disposable/temp-mail domains · role-based and no-reply inboxes · free-provider detection · live DNS: MX mail-server records, null-MX (domains that refuse all mail), A-record fallback, SPF and DMARC authentication health · a 0–100 score built from all of it.

We don't (currently): a live SMTP mailbox probe — the "does john@ exist on this server" handshake. The smtp field in every record honestly reports unknown. Cloud platforms block the network port that check requires, which affects every verification actor on Apify, regardless of what their listings claim — most quietly return "unknown" or "catch_all" dressed up in a score. We say it plainly instead, and we cap DNS-evidence scores at 85: scores of 86–100 are reserved for SMTP-confirmed mailboxes, so a score from this actor is never overstated.

What you get

One record per unique email address (duplicates are removed and never double-charged):

{
  "email": "jane@gmial.com",
  "normalizedEmail": "jane@gmial.com",
  "domain": "gmial.com",
  "status": "invalid",
  "subStatus": "typo_domain",
  "score": 0,
  "didYouMean": "jane@gmail.com",
  "syntaxValid": true,
  "mxFound": false,
  "smtp": "unknown",
  "catchAll": null,
  "disposable": false,
  "roleBased": false,
  "freeProvider": false,
  "hasTag": false,
  "mxRecords": [],
  "spf": null,
  "dmarc": null
}

Field	Meaning
status	valid — safe to send · risky — deliverable but risky (shared inbox, catch-all, throwaway) · invalid — do not send · unknown — could not be determined
subStatus	The specific reason: mx_verified, no_mx_record, typo_domain, disposable, domain_rejects_mail, bad_syntax, …
score	0–100 deliverability quality score — sort by it, pick your own cut-off
didYouMean	Suggested fix for mistyped providers (gmial.com → gmail.com)
mxFound / mxRecords	Whether the domain runs mail servers, and which ones
disposable	Throwaway/temp-mail domain (10-minute inboxes, mailinator, …)
roleBased	Shared inbox (info@, support@, noreply@, …) — risky for outreach
freeProvider	Consumer provider (Gmail, Yahoo, Outlook, …) rather than a company mailbox
hasTag	Address contains a +tag (often signup filters)
spf / dmarc	Domain email-authentication health — a spam-filter signal
smtp / catchAll	Mailbox-level SMTP probe result — currently always unknown/null, see "What we check" above

Export as CSV/Excel with one click, or append ?format=csv / ?format=xlsx to the dataset URL.

Statuses you can act on

• valid → keep. The domain provably receives mail and the address shape is good.
• risky → send with care: shared info@ inboxes, catch-all domains, disposable services.
• invalid → delete. Bad syntax, mistyped provider, no mail server, or a domain that refuses all mail (null MX).
• unknown → the evidence was inconclusive (DNS timeout, bare-A-record domain). Not charged less — but honestly labeled instead of guessed.

Verify results from other actors — zero copy-paste

Under Advanced, paste the dataset ID of any finished run and the verifier pulls addresses automatically:

• Website Contact Scraper → set Email field name to emails
• Google Maps scraper runs with email enrichment → leave it as email

Scrape → find contacts → verify, all inside Apify.

Pricing — no surprises

• $0.50 per 1,000 verified emails ($0.0005 each), pay-per-event. No subscription tiers, no platform-usage add-ons.
• Free: malformed rows (not-an-email), duplicate rows, and every re-run of the same unique address in one run.
• Set a maximum cost on any run (maxTotalChargeUsd) — the run stops cleanly at your cap and you keep everything delivered up to it.

How it works

Each address goes through: syntax & normalization → typo detection → disposable & role checks → live DNS (MX records, RFC 7505 null-MX, A-record fallback, SPF/DMARC) → scoring. The smtp and catchAll fields are reserved for our upcoming SMTP relay tier and report unknown/null until then — see "What we check — and what we don't" above.

FAQ

Is this GDPR-safe? The actor never sends email and never stores your list beyond the run's dataset, which you control and can delete.

What's a catch-all domain? One that accepts mail for any address — a "yes" there can't prove your specific contact exists, so it's risky.

Why is info@ risky and not invalid? It usually delivers — but shared inboxes convert poorly and complain often, so outreach tools treat them as risky.

How many emails per run? Up to 100,000. Need more? Split the list or run several inputs in parallel.

---

Keywords: email verification, email validator, bulk email checker, email list cleaning, verify email addresses, MX record check, disposable email detection, catch-all detection, email deliverability, reduce bounce rate, ZeroBounce alternative, NeverBounce alternative.