Email Validator & Verifier — MX, SMTP & Syntax

Validate email addresses in bulk with syntax, domain, MX, disposable-domain, role-account, and optional SMTP checks for list QA.

What this actor does

Validate email addresses in bulk with syntax, domain, MX, disposable-domain, role-account, and optional SMTP checks for list QA. The actor is configured for public or user-supplied sources, evidence-backed output rows, capped runs, and KVS summaries for blocked, empty, duplicate, or capped work.

What you can use it for

• Build repeatable email validator datasets for analysis and automation.
• Export records with source URLs, evidence fields, and run summaries.
• Run buyer-ready tasks for: Validate a CSV of email addresses; Check MX and disposable status before outreach; Find invalid addresses in a lead list.

Search-intent terms: email validator, email verifier, mx check, disposable email detection, list cleaning, smtp validation, email QA.

Inputs

The input schema supports the actor's source fields plus cost and quality controls. Important caps include emails, maxConcurrency, smtpTimeout, checkMx, checkSmtp, allowDisposable. Public task examples below provide small, safe starting inputs.

Outputs

Paid dataset rows and paid KVS artifacts are written only after the configured PPE charge succeeds. Rows include source/evidence fields where the actor can determine them and avoid fabricated values.

Key-value store reports

Every run writes SUMMARY.md and SUMMARY.json. Diagnostic CSV or JSON reports are used for blocked pages, no-result pages, duplicates, unsupported inputs, and capped runs instead of paid dataset rows.

Pricing

This actor uses pay-per-event pricing with Apify platform usage included in the event prices. Store discount tiers are configured for FREE, BRONZE, SILVER, and GOLD users.

Event	Unit	FREE	BRONZE	SILVER	GOLD
actor-start	run	$0.00500	$0.00500	$0.00450	$0.00400
email-validated	record	$0.00390	$0.00390	$0.00351	$0.00312

Primary paid output event: email-validated. Runtime-paid dataset rows and runtime-paid artifacts use this active paid-output event unless a future pricing revision adds an actor-specific artifact boundary with matching code.

Cost controls and max-charge behavior

Default max charge: $5.00. When the run reaches the max charge or an event-charge limit, it stops gracefully and writes free summary diagnostics without adding unpaid dataset rows.

Platform usage / proxy / browser / API notes

The configured model is fixed-inclusive PPE: platform usage is included in event prices and the platform-usage pass-through toggle is off. Features that require browser rendering, proxies, provider APIs, or additional fetches are bounded by the input caps and priced through explicit events.

Reliability notes and limitations

The actor processes public or permissioned inputs only. Blocked pages, login walls, unsupported formats, empty results, and provider errors are recorded as diagnostics. The actor does not fabricate rankings, prices, reviews, sentiment, traffic, compliance status, or private contact data when source evidence is unavailable.

Example inputs

{
  "emails": [
    "test@gmail.com",
    "invalid@nonexistent-domain-12345.com"
  ],
  "checkMx": true,
  "checkSmtp": true,
  "checkDisposable": true,
  "checkRole": true,
  "checkFreeProvider": true,
  "checkCatchAll": false,
  "smtpTimeout": 10000,
  "maxConcurrency": 5
}

Public task examples

• Validate a CSV of email addresses: Dataset rows matching the validate a csv of email addresses use case, plus SUMMARY.md and SUMMARY.json reports in the key-value store.
• Check MX and disposable status before outreach: Dataset rows matching the check mx and disposable status before outreach use case, plus SUMMARY.md and SUMMARY.json reports in the key-value store.
• Find invalid addresses in a lead list: Dataset rows matching the find invalid addresses in a lead list use case, plus SUMMARY.md and SUMMARY.json reports in the key-value store.

Ethical/allowed-use notes

Use this actor only for public data, owned files, or sources you have permission to process. Respect source terms, privacy expectations, robots guidance, and applicable laws. Do not use the actor to collect secrets, bypass access controls, or make unsupported legal, financial, medical, or compliance decisions.