Bulk Email Domain Validator

Validate email syntax and mail-domain configuration with transparent evidence. The Actor normalizes addresses, checks MX and fallback address DNS, and flags known disposable domains and role-based local parts.

What the result means

• valid: syntax is valid and MX records are present without configured risk flags.
• risky: syntax is valid but a disposable, role-based, or address-only delivery signal applies.
• invalid: syntax is invalid or the domain has no observed mail/address DNS.
• unknown: DNS returned a temporary error or timeout.

This is deliberately honest: it does not send SMTP messages and does not claim mailbox existence, inbox placement, or catch-all status.

Provide inline emails or an Apify datasetId plus emailField. Duplicate values are validated once.

Quick start

{
  "emails": [
    "hello@apify.com",
    "support@example.invalid",
    "not-an-email"
  ],
  "checkMx": true,
  "flagDisposable": true,
  "flagRoleBased": true,
  "maxEmails": 500
}

For an existing Apify dataset, set datasetId and emailField instead of copying addresses into the input. maxEmails is a hard batch limit, while concurrency lets you tune DNS throughput.

Output

Each unique address produces one dataset row with its normalized address and domain, syntax status, MX/address DNS evidence, disposable and role-based flags, final status, risk labels, and an explicit error when DNS is temporarily unavailable. The OUTPUT key-value-store record summarizes valid, risky, invalid, unknown, duplicate, and budget-limited counts.

Common workflows include cleaning CRM imports, checking consented outreach lists, validating account-registration data, and adding a deterministic email-quality step to n8n or Make.

API and automation

curl -X POST \
  "https://api.apify.com/v2/acts/gifted_wagon~bulk-email-domain-validator/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"emails":["hello@apify.com"],"checkMx":true}'

Save a tested input as an Apify task for repeat jobs. In n8n or Make, send JSON to the same endpoint and route valid, risky, invalid, and unknown rows separately.

Pricing

The primary email-validated event starts at $0.0006 per unique completed validation. The OUTPUT summary is uncharged. A small Actor-start event covers startup.

Responsible use

Use results for legitimate data quality and consented communications. Validation is not permission to send email; comply with applicable privacy, marketing, and anti-spam laws.

FAQ and limitations

• Does valid prove the mailbox exists? No. It confirms syntax and observable mail-domain configuration only.
• Does the Actor send email or probe SMTP servers? No.
• Why can a result be unknown? DNS services can time out or return temporary errors; retry those rows later.
• Are duplicate addresses charged twice? No. Normalized duplicates are processed once.