Same product as Email Validator. Both listings run identical code (syntax + live DNS/MX + disposable/free/role detection; no SMTP mailbox probe). Use whichever you already have configured.

Bulk Email Validator

Validate and clean email lists at scale — syntax, MX, disposable and role-account checks in one pass.

You supply the addresses; the Actor validates them. Use it in line with applicable outreach and privacy law.

📊 Sample Output

email	status	isValid	domain	localPart	normalized
[email on record]	valid	True	stripe.com	support	[email on record]
[email on record]	valid	True	github.com	info	[email on record]
[email on record]	valid	True	mailinator.com	someone	[email on record]

Real rows from run pMjYbZhnvamntGNeB on build 0.0.23 (2026-09-25), unedited apart from masked emails/phones and shortened long text; fields the source does not publish are empty.

⚙️ Sample inputs

This is the Store example input — the same input Apify's automated check runs — so it is proven to return rows on the current build. Paste it into the input form, or send it through the API, CLI or a schedule:

{
  "emails": [
    "jeff@amazon.com"
  ]
}

🔧 Input reference

Field	Type	Default	What it does
emails	array of string	["support@stripe.com", "info@github.com", "someone@mailinat…	Email addresses to validate. Accepts either a JSON array (recommended) or a string with one email per line / comma-separated. Each address returned as a row is billed once.
singleEmail	string	""	Convenience field to validate a single email address

🧾 JSON sample record

One real record from run pMjYbZhnvamntGNeB (emails/phones masked, long text shortened):

{
  "email": "[email on record]",
  "status": "valid",
  "isValid": true,
  "valid": true,
  "syntaxValid": true,
  "mxValid": true,
  "hasMx": true,
  "domain": "stripe.com",
  "localPart": "support",
  "normalized": "[email on record]",
  "isDisposable": false,
  "disposable": false,
  "isFreeProvider": false,
  "isRoleAccount": true,
  "roleAccount": true,
  "deliverable": true,
  "mxRecords": [
    {
      "priority": 10,
      "server": "aspmx.l.google.com"
    },
    {
      "priority": 20,
      "server": "alt2.aspmx.l.google.com"
    },
    {
      "priority": 20,
      "server": "alt1.aspmx.l.google.com"
    },
    {
      "priority": 30,
      "server": "aspmx2.googlemail.com"
    },
    {
      "priority": 30,
      "server": "aspmx3.googlemail.com"
    }
  ]
}

💰 Pricing

Event	Price (USD)	When it is charged
Actor Start (apify-actor-start)	$5e-05	Charged when the Actor starts running. Number of events charged depends on Actor memory (one event per GB, minimum one event).
Email validation (apify-default-dataset-item)	$0.05	Charged per email address validated — checks MX records, SMTP, role-based detection, disposable domains, syntax, and deliverability scoring.

Pay-per-event: you pay only for what the run delivers. A run that delivers nothing bills no result events (only the actor-start event, when the actor defines one). Example: a run that delivers 100 results costs 100 × $0.05 = $5.00 plus the start fee.

🔗 Related Actors

More from the NexGenData Leads, contacts & enrichment family:

• Website Contact Scraper — Emails & Phones from a URL List API
• Domain Security Posture Checker — DNS, SPF, DMARC, TLS
• Email DMARC Auditor — SPF/DKIM/DMARC Bulk Check
• Google Maps Reviews Scraper — Local Review Monitoring API
• IP Geolocation — Bulk IP to Location & ISP
• IPinfo / MaxMind GeoLite2 Replacement — DB-IP Powered IP Lookup

30 more in this family on the NexGenData Store page.

📊 What you get

Clean JSON, one record per email validated:

• email / normalized — the address, lower-cased and trimmed
• status — valid or invalid
• isValid / valid — the domain publishes MX records
• syntaxValid — RFC-shaped address
• mxValid / hasMx — MX lookup result
• mxRecords — up to 5 {priority, server} entries
• domain / localPart
• isDisposable / disposable — throwaway-mailbox domain
• isFreeProvider — consumer webmail domain
• isRoleAccount / roleAccount — generic mailbox (info@, sales@, support@ …)
• deliverable — syntax OK and MX present and not disposable
• reason — why an address was rejected (invalid_syntax, nxdomain, no_mx_records)

Scope (honest): validation is syntax + live DNS/MX + list checks. No SMTP mailbox probe is performed — deliverable means the domain can accept mail, not that the individual mailbox exists. Addresses whose DNS never answers are skipped and not billed; if DNS is unreachable for every domain the run fails rather than returning filler rows.

Pricing: $0.050 per email validated (Pay-Per-Event) — about 20 emails per $1. Only delivered rows are charged.

🤖 Use with AI agents

Point Claude, the OpenAI Agents SDK, an n8n flow or any MCP-aware client at it and clean lists on demand.

Agentic payments (x402): Supports agentic payment via x402 — agents can call this actor with USDC, no API key required.

🔗 Related lead-gen actors

The lead-gen workflow chain — found leads? verify → enrich → push to CRM:

1. Find: B2B Leads Finder · Company Email Finder · Person Email Finder · Website Contact Scraper · Yellow Pages
2. Enrich: Company Enrichment · B2B Contact Enricher · Lead List Enricher · Website Tech & Contact Audit
3. Verify & clean: Email Verification · Lead List Cleaner
4. Deliver: Leads to Notion CRM

Front door — Sales Intelligence MCP: the sales-intelligence agent that fronts this whole cluster → Sales Intelligence MCP

---

Validation of addresses you supply, against live DNS.

Validate the phone column too: Phone Number Validation — format, line type and carrier for every number in your list.