Bulk Email Verifier | MX, Syntax & Deliverability Score
Pricing
from $0.34 / 1,000 verified email (decisive result)s
Bulk Email Verifier | MX, Syntax & Deliverability Score
Verify email lists in bulk: syntax + MX via DNS-over-HTTPS, disposable/role/free flags, typo fixes (didYouMean), Gravatar evidence, mail-provider fingerprint and a 0-100 deliverability score. Unknowns, duplicates and garbage lines are never charged. HTTP-only, pay per result, MCP-ready.
Pricing
from $0.34 / 1,000 verified email (decisive result)s
Rating
0.0
(0)
Developer
Mr Zack
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
Bulk Email Verifier & List Cleaner — MX, Typo Fixes & Existence Evidence
Verify email lists at $0.48 per 1,000 — the lowest price in the category — with checks the cheap verifiers don't do: Gravatar existence evidence, typo autocorrect suggestions, mail-provider fingerprinting and a transparent 0–100 deliverability score.
Unknown results are never charged. Neither are duplicates or unparseable lines. You pay only for decisive verdicts (valid / risky / invalid).
Who this is for
- Cold-email senders — a 15–20% bounce rate can burn a sending domain in one campaign. Clean the list first, keep your sender reputation.
- Lead-list buyers & scrapers — 20–40% of scraped emails are dead. Chain this actor straight after any lead scraper (it reads emails from any Apify dataset).
- CRM owners — periodic hygiene: re-verify your contact base on a schedule and archive the dead rows before your ESP charges you for them.
Pairs perfectly with Contact Details Scraper: scrape → pass its dataset ID here → send only what's deliverable.
What each email goes through
- Syntax validation (RFC-style, normalizes case/whitespace/
mailto:) - Typo detection —
bob@gmial.com→didYouMean: bob@gmail.com(one-edit distance against 25 major providers + common TLD slips like.con→.com). Recover leads other verifiers throw away. - MX lookup via DNS-over-HTTPS (Google + Cloudflare resolvers, RFC 5321 A-record fallback, RFC 7505 null-MX detection)
- Mail-provider fingerprint — google-workspace, microsoft-365, zoho, proton, fastmail, mimecast, proofpoint, custom… Know which mailboxes are corporate-grade.
- Disposable check against a continuously-maintained blocklist (8,000+ domains, refreshed at run start) + role-account (
info@,sales@…) and free-provider flags - Gravatar existence probe — a hit proves this exact mailbox belongs to a real registered person. No other verifier in the category surfaces this.
- Domain liveness — is there a live website behind the domain?
- Deliverability score 0–100 + verdict:
valid/risky/invalid/unknown
Output fields
| Field | Description |
|---|---|
email | Normalized address |
status | valid · risky · invalid · unknown (unknown = never charged) |
deliverabilityScore | 0–100 composite (null when unknown) |
didYouMean | Suggested fix when the domain looks like a typo |
mxStatus / mxHosts | MX result + hosts |
mailProvider | Fingerprinted mailbox provider |
isDisposable / isRole / isFree | Hygiene flags |
hasGravatar | Existence evidence: this exact email owns a Gravatar |
domainAlive | Live website on the domain? |
syntaxValid, domain, verifiedAt | Supporting detail |
A SUMMARY record in the key-value store gives you the run at a glance: valid %, provider breakdown, disposable/role/free counts, typo suggestions found, and exactly how many results you were charged for.
Honest scope: what "verified" means here
This actor runs MX-tier verification plus independent existence evidence (Gravatar, domain liveness). It does not claim SMTP-handshake mailbox pings: from shared cloud IPs those are frequently greylisted, blocked, or answered by catch-all servers — which is how other tools end up labeling dead mailboxes "SMTP valid". We'd rather give you verifiable signals than a confident guess. For most list-cleaning use cases (killing hard bounces before they happen), MX + evidence is what does the work: an address whose domain has no mail server cannot receive email, full stop.
Pricing that can't surprise you
- $0.48 / 1,000 decisive results + $0.01 per run — lowest in the category (typical competitors: $0.60–$5.00 / 1,000)
unknownresults (DNS unreachable): free- Duplicates in your input: deduplicated up front, free
- Unparseable garbage lines: skipped, free
How to schedule this actor (recommended)
List hygiene isn't a one-off — lists decay ~2–3% per month.
- Open the actor page → Schedules tab → create a schedule (weekly or monthly fits most CRM/outreach cadences).
- Point the input at your standing dataset (
datasetId+emailField) so every run verifies your latest scraped or imported leads. - Add a Google Sheets or webhook integration and filter on
status = "valid"— your sender only ever sees clean rows.
Input example
{"emails": ["jane.doe@acme.com", "bob@gmial.com", "info@startup.io"],"datasetId": "abc123DatasetFromYourLeadScraper","emailField": "email"}
emailField accepts a string, an array of strings, or objects with an email property — Contact Details Scraper output works with zero configuration.
Fair use & privacy
Verification uses public DNS records and public Gravatar/domain endpoints only — no login, no inbox access, no email is ever sent, nothing is stored beyond your own dataset.
Questions or a field you wish existed? Open an issue on the actor — feature requests routinely ship within days. If this actor saved your sender reputation, a review genuinely helps an indie builder compete with the big resellers.
Changelog
- 0.1.1 (16 Sep 2026) — A run with no input no longer fails: the example input is the default, so "Run" with an empty form (or
{}via API) returns the demo dataset. Output unchanged. - 0.0.5 (10 Sep 2026) — Maintenance: billing safety (
chargeSafely— a failed charge can no longer kill a run that already has data), test suite wiring, README. - 0.0.1 (25 Aug 2026) — Launch.
Found this useful? A review helps more than you'd think
If this Actor saved you time, a short review on the Reviews tab of this Store page takes 30 seconds and is the only signal other buyers have before they spend anything. If something is broken instead, open a ticket on the Issues tab — parser bugs and field requests get fixed.
Related Actors from the same account