Email Validator & Verifier — Bulk Email Check avatar

Email Validator & Verifier — Bulk Email Check

Pricing

from $0.30 / 1,000 emails

Go to Apify Store
Email Validator & Verifier — Bulk Email Check

Email Validator & Verifier — Bulk Email Check

Email Validator checks syntax, MX/A DNS records, disposable/free-provider/role classification and typo suggestions for a list of email addresses — one scored row per address, no SMTP mailbox probing.

Pricing

from $0.30 / 1,000 emails

Rating

0.0

(0)

Developer

Murat Uzun

Murat Uzun

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

2 days ago

Last modified

Share

What is Email Validator & Verifier?

Email Validator & Verifier is an Apify Actor that checks syntax, MX/A DNS records, disposable-domain, free-provider and role-account status for a list of email addresses and returns one scored row per address. It runs a full RFC 5322-lite structural check, resolves the domain's mail-exchange path over Google's public DNS-over-HTTPS resolver, matches the domain against curated disposable and free-provider lists, and flags generic role addresses like info@ or support@. This is syntax + DNS/MX + list-based validation, not SMTP mailbox verification — it never opens an SMTP connection to confirm a specific mailbox exists, because outbound port 25 is blocked on the Apify platform (and on most cloud infrastructure). Every address still gets a clear deliverability verdict and a 0-100 score you can filter a lead list on immediately.

Pricing: Email Validator & Verifier costs $0.50 per 1,000 results (pay per result, no subscription; Apify's free plan credit covers small runs).

What data does Email Validator & Verifier extract?

Email Validator & Verifier extracts 18 fields per email address:

FieldTypeDescription
email, normalizedEmailstringAddress as given, and lower-cased with Gmail dot/plus canonicalisation applied
isValidSyntax, localPart, domain, domainAsciiboolean, stringRFC 5322-lite structural check result, split parts, and the domain's punycode/ASCII form
hasMx, mxRecords, mxFallback, mxProviderboolean, array, stringWhether the domain can receive mail, its MX hosts, whether an A/AAAA fallback was used, and the detected mailbox vendor (Google Workspace, Microsoft 365, Zoho Mail…)
isDisposable, isFreeProvider, isRoleAddressbooleanMatches against the embedded disposable-domain, free-provider and role-prefix lists
didYouMeanstringA likely-intended address when the domain looks like a typo of a free provider
deliverability, score, reasonsstring, number, arrayVerdict (deliverable-likely/risky/undeliverable/unknown), 0-100 confidence, and why
error, scrapedAtstringPer-address failure note and check timestamp

How to use Email Validator & Verifier

  1. Paste your addresses into Emails — straight out of a CRM export, sign-up form log or lead list works fine; blank lines and duplicates are ignored.
  2. Leave Check MX / A records on to verify each domain can actually receive mail. Turn it off for a syntax-and-list-only pass when you just need speed.
  3. Raise Max concurrency to 20-30 for lists of thousands, click Start, then export as JSON, CSV, Excel or HTML.

Example input

{
"emails": ["jane.doe@example.com", "support@apify.com", "test@mailinator.com", "user@gmial.com"],
"checkMx": true,
"maxConcurrency": 10
}

Example output

{
"email": "jane.doe@example.com",
"normalizedEmail": "jane.doe@example.com",
"isValidSyntax": true,
"localPart": "jane.doe",
"domain": "example.com",
"domainAscii": "example.com",
"hasMx": true,
"mxRecords": ["a.iana-servers.net"],
"mxFallback": false,
"mxProvider": null,
"isDisposable": false,
"isFreeProvider": false,
"isRoleAddress": false,
"didYouMean": null,
"deliverability": "deliverable-likely",
"score": 100,
"reasons": ["No issues found"],
"error": null,
"scrapedAt": "2026-09-13T09:00:00.000Z"
}

Input parameters

ParameterTypeDefaultDescription
emailsarray["support@apify.com"]Email addresses to validate, one row each
checkMxbooleantrueLook up MX (falling back to A/AAAA) over DNS-over-HTTPS
maxConcurrencyinteger10Addresses checked in parallel (1-50)
inputDatasetIdstringnoneRead addresses from another Actor run's dataset — see Chain it after contact-extractor
inputFieldstringemailColumn in that dataset holding the address, e.g. emails for an array column (array values are flattened)

Chain it after contact-extractor

inputDatasetId lets Email Validator & Verifier read its input straight from another Actor's dataset instead of (or alongside) a pasted emails list, so a lead-generation pipeline never has to copy-paste addresses between runs:

  1. Run Email Extractor — Website Contact & Social Finder against your target sites. It returns one row per domain with an emails field — an array of every address found on that site.
  2. Copy the finished run's Dataset ID from its Output tab (or the defaultDatasetId field on the run object if you're chaining via the API).
  3. Start Email Validator & Verifier with:
{
"inputDatasetId": "<contact-extractor's dataset ID>",
"inputField": "emails",
"checkMx": true
}

inputField has to be set to "emails" here (not left on the email default) because contact-extractor's column is an array of addresses per domain, not one address per row. withInputAliases flattens that array automatically — a 50-domain contact-extractor run whose sites each expose 2-3 addresses becomes 100-150 individual rows here, each scored for syntax, MX and disposable/free/role status. Addresses from inputDatasetId are merged with (and deduplicated against) anything also passed in emails, so the two sources can be combined in one run.

Pricing

Email Validator & Verifier uses pay-per-event pricing: $0.0005 per email result, i.e. $0.50 per 1,000 addresses, plus a negligible actor-start fee. Each address needs at most one DNS-over-HTTPS lookup, so a list of 10,000 leads runs in a couple of minutes and costs a few dollars. Set Maximum cost per run and the Actor trims the list to what the budget covers instead of overspending.

Email Validator & Verifier vs. ZeroBounce and NeverBounce

Most "email verifier" SaaS tools open a live SMTP connection to the mailbox provider on port 25 to test whether a specific inbox exists (a "ping" that catch-all domains and greylisting can make unreliable anyway). Cloud platforms including Apify block outbound port 25, so this Actor does not attempt that step — and is upfront about it. What it gives you instead, at a fraction of the cost, is the check that actually predicts most bounce and lead-quality problems: is the syntax even valid, does the domain accept mail at all, is it a disposable throwaway, and is it a generic role inbox rather than a named contact. For high-stakes sending, pair this Actor's fast first-pass filter with a dedicated SMTP-verification tool on the addresses that pass.

Email Validator & VerifierZeroBounceNeverBounce
Price per 1,000 emails$0.50 ($0.0005/email)~$99/mo for 10,000 credits, or ~$20/1,000 pay-as-you-go~$8/1,000 pay-as-you-go
Syntax + MX/A DNS checkYesYesYes
Disposable-domain listYes — 478 curated domainsYesYes
Free-provider / role-account flagsYesYesYes
Typo suggestions (didYouMean)YesYesYes
SMTP mailbox checkNo — port 25 is blocked on Apify (and most cloud platforms)YesYes
Catch-all domain detectionNo — requires the same blocked SMTP connectionYesYes
Runs on Apify (API, scheduling, inputDatasetId chaining)YesNoNo

List prices, Sept 2026 — ZeroBounce and NeverBounce change their tiers frequently, check their current pricing pages before budgeting a large list. The honest gap is the two "No" rows: if a bounce rate near zero matters more than cost (a paid ad-audience upload, a high-value cold outreach send), pair this Actor's first pass with one of the SMTP-verification services above for the addresses that survive it. For everyday list hygiene — deduping a sign-up form, gating a lead list before a CRM import, catching gmial.com typos — the DNS/list-based check here catches most of the real problems for a fraction of the price.

Using Email Validator & Verifier with AI agents and MCP

Email Validator & Verifier is pay-per-event with limited permissions — the two requirements for an Actor to be callable through the Apify MCP server at mcp.apify.com. An agent passes emails and gets back one structured row per address — syntax, MX status, disposable/free/role flags, a typo suggestion and a 0-100 score — ready to filter a lead list, gate a sign-up form, or clean a mailing list before a campaign. The same run works from n8n, Make, Zapier and LangChain through Apify's integrations.

FAQ

Does this verify a mailbox actually exists? No. It checks syntax, whether the domain can receive mail (MX/A records), and whether it's disposable, free or a role account. It never opens an SMTP session, so a syntactically valid address at a domain with working MX can still bounce if that specific mailbox was never created — no tool running on a cloud platform (port 25 blocked) can rule that out without an SMTP handshake.

What does deliverability: "unknown" mean? The MX/A check was skipped (checkMx: false) or the DNS lookup itself failed (timeout, resolver error) — the address may be fine, but the domain's ability to receive mail was not confirmed this run.

How current is the disposable-domain list? It's a curated, embedded snapshot (478 domains: mailinator, guerrillamail, 10minutemail, temp-mail, yopmail and their many mirrors) dated 2026-09-13, not a live feed. New disposable services appear constantly; treat isDisposable as a strong signal, not a guarantee.

Why did a real Gmail address get a typo suggestion? didYouMean only fires when the domain is NOT already an exact match for a known free provider and is within a Levenshtein edit distance of 2 from one (e.g. gmial.com, yahooo.com). An exact gmail.com never triggers it.

Is this legal to run? Yes. DNS records are public infrastructure data, and no message content is read or sent.

Can I export to CSV or Excel? Yes, from the Output tab or the API, with a ready-made Overview view.

Part of the webdatatools web-intelligence suite — every Actor is pay-per-event, reads public data without a login, and returns one clean row per entity:

Browse the whole suite at webdatatools, or call ten of these Actors straight from Claude, Cursor or Cline with the webdatatools MCP server.

Website & domain intelligence

Content for AI, LLMs and RAG

Search, video and social

Leads, jobs and company data

Developer, app and research data

Support and feedback

Found a mailbox provider it should recognise, a disposable domain worth adding, or a scoring edge case? Open an issue on the Issues tab.