Check RFC syntax, DNS MX, and disposable domains on up to 1,000 supplied emails

Bulk Email Syntax & MX Validator (Store README title: Email Deliverability Checker) audits email strings you already hold. It checks RFC syntax, live DNS MX, and known disposable-domain patterns, then returns per-address technical signals including a 0–100 score. It does not send mail and does not discover, enrich, or acquire addresses. Domain SPF/DMARC policy grades belong on DMARC & Email Security Checker. Phone-string E.164 formatting belongs on Bulk Phone Format Validator.

$3.00 per 1,000 email data-quality results

Open Bulk Email Syntax & MX Validator on Apify

Syntax, MX, and disposable checks on email strings, not domain policy or phone numbers

Use this page when the job is list hygiene on a consented email export: syntax, MX presence, disposable-provider flags, and a composite score. Use DMARC & Email Security Checker when the job is SPF, DMARC, MX, and optional DKIM posture on domains you supply. Use Bulk Phone Format Validator when the job is offline E.164 normalization of phone strings.

This Actor DMARC & Email Security Checker Bulk Phone Format Validator
Intent Validate user-supplied email strings: RFC syntax, DNS MX, disposable-domain checks Audit SPF, DMARC, MX, and optional DKIM; return a 0–100 / A–F grade Normalize user-supplied phone strings to E.164 with type detection
Input Email strings in emails (max 1000) Hostnames in domains (max 500) Phone strings in numbers (max 1000)
What it reads The strings you pass; live DNS MX when checkMx is true; disposable-provider blocklist when checkDisposable is true Public SPF, DKIM, DMARC, MX, and related DNS for email-auth review The strings you pass; google-libphonenumber runs locally, no network
Primary output Per-address technical row: validity, syntax, MX, disposable flag, domain, 0–100 score Per-domain score, spf, dmarc, dkim, mx Format-validation row: validity, E.164, country, line type
Sends mail / discovers addresses None. No messages sent; no address discovery or enrichment None. Passive public DNS only None. Does not acquire numbers or crawl profiles
Inbox / mailbox proof No. Published FAQ: no SMTP handshake; a positive result does not prove mailbox ownership Not an email-string validator Not a phone reachability ping

The Store description is: audit user-supplied email data using syntax, DNS MX, and disposable-domain checks. No messages are sent and no addresses are discovered or enriched. The README states a positive result is a technical signal only and does not prove mailbox ownership, consent, or permission to send messages. Pass an authorized CRM or customer-supplied list — not a harvest from public pages.

Use cases

Published Key Features: RFC-compliant syntax validation; DNS MX lookup for working mail exchangers; disposable detection (tempmail, guerrillamail, mailinator, 10minutemail); 0–100 composite score per email; bulk processing up to 1,000 emails per run; no sending required. The README Lead Enrichment Pack places this Actor as step 2 after a consented CSV clean, then Bulk Phone Format Validator for phone strings.

Store Quickstart: start with Quickstart (5 Demo Emails) on a mixed set of valid, invalid, and disposable addresses, then Database migration audit, Sales Outreach Pre-Flight, or CRM Hygiene Audit.

How is Bulk Email Syntax & MX Validator different from DMARC & Email Security Checker and Bulk Phone Format Validator?

This Actor checks RFC syntax, DNS MX, and disposable-domain membership on email strings you already have. Required input is emails (maximum 1000). The Store description states it audits user-supplied email data using syntax, DNS MX, and disposable-domain checks; no messages are sent and no addresses are discovered or enriched. DMARC & Email Security Checker audits public SPF, DMARC, and MX (optional DKIM) on domains you supply (domains, maximum 500) and returns a 0–100 score with an A–F grade — domain email-auth policy, not per-address syntax on a list. Bulk Phone Format Validator is offline libphonenumber formatting of phone strings in numbers (maximum 1000). Use this Actor to validate a consented email-string list. Use DMARC & Email Security Checker for SPF/DMARC/MX posture on authorized domains. Use Bulk Phone Format Validator for E.164 hygiene.

What input is required?

emails is required. The live schema description is “Emails to validate (max 1000).” Other live schema fields:

Field Type Default Notes
emails string[] required Emails to validate (max 1000). Schema prefill is test@gmail.com, user@mailinator.com, bad@@invalid.
checkMx boolean true Check MX records via DNS lookup.
checkDisposable boolean true Check against disposable email providers.
delivery string dataset dataset or webhook
webhookUrl string — POST target when delivery is webhook
dryRun boolean false Run without saving results (for testing)

The schema sets additionalProperties to false. The README Input table lists only emails, checkMx, and checkDisposable. Live schema also includes delivery, webhookUrl, and dryRun. README examples that send includeDisposable or mxOnly are not live schema fields. Live schema names do not include checkDkim or checkBimi.

Published Store example run input:

{
  "emails": [
    "test@gmail.com",
    "user@mailinator.com",
    "bad@@invalid"
  ],
  "checkMx": true,
  "checkDisposable": true,
  "dryRun": false
}

Published README input example (schema-valid):

{
  "emails": ["user@example.com", "fake@10minutemail.com"],
  "checkMx": true,
  "checkDisposable": true
}

README examples labeled Bulk pre-send hygiene (includeDisposable) and MX-only mode (mxOnly) are not live input fields. Start with Quickstart (5 Demo Emails). Use dryRun: true before larger batches or webhook delivery.

Run Bulk Email Syntax & MX Validator on Apify

What does a result row contain?

The published README output table lists domain, hasMx, mxRecords, spfPass, spfRecord, dmarcPass, dmarcPolicy, dkimPass, and bimiPass. The published README sample uses email, isValid, syntaxOk, mxValid, mxRecords (priority plus exchange), isDisposable, domain, and score (0–100). There is no published output JSON schema on the Store page.

Published README sample:

{
  "email": "user@example.com",
  "isValid": true,
  "syntaxOk": true,
  "mxValid": true,
  "mxRecords": [{"priority": 10, "exchange": "mail.example.com"}],
  "isDisposable": false,
  "domain": "example.com",
  "score": 95
}

That sample is the published README illustration, not a live coverage guarantee. The output table lists SPF, DMARC, DKIM, and BIMI fields; the sample does not. The table describes dkimPass as applying if checkDkim is enabled and bimiPass if checkBimi is enabled; those names are not live schema fields. Domain SPF/DMARC policy grades for hostnames you supply belong on DMARC & Email Security Checker.

Published FAQ on the score field: 90+ is described as safe for sending, 70–90 as risky, and below 70 as discard or double opt-in. Typos such as gmial.com are described as invalid when the domain has no MX records. The embedded disposable list is described as 3,000+ known providers, updated with releases (examples: tempmail, guerrillamail, mailinator, 10minutemail).

Does it send mail, discover addresses, or check if an inbox exists?

No. The Store description states: audit user-supplied email data using syntax, DNS MX, and disposable-domain checks; no messages are sent and no addresses are discovered or enriched. The README states the Actor never sends a message and does not discover, enrich, or acquire addresses. A positive result is a technical signal only and does not prove mailbox ownership, consent, or permission to send. The published FAQ states it does not check if the inbox exists — that would require an SMTP handshake, which is not safe for bulk checking.

The published FAQ also states this is not a per-mailbox existence check (“domain-level configuration only”) and that dkimPass=true would mean at least one DKIM selector was detected (default, google, k1, mail, etc.), not that all senders sign correctly. Use an authorized export. This Actor is not a people-finder, not a mailer, and not an SMTP probe.

How is Bulk Email Syntax & MX Validator priced?

Billing is pay-per-event. The live Store card is $3.00 / 1,000 email data-quality results. The billed event is Email data-quality result at $0.003, charged only for one delivered technical validation result for a user-supplied address. You are not charged for Apify platform usage, only the fixed event price.

The README Cost section still quotes actor-start $0.01 plus dataset-item $0.003 ($3.01 for 1,000 items); live Store billing currently lists only the $0.003 Email data-quality result event. Check the Store pricing card for the current per-event rates.

$3.00 per 1,000 email data-quality results ($0.003 per delivered technical validation result)

See Bulk Email Syntax & MX Validator pricing on Apify

How do dataset, webhook, and dry-run delivery work?

delivery defaults to dataset. Set delivery to webhook and provide webhookUrl to POST results. dryRun true runs without saving results (for testing). The Store Quickstart starts with Quickstart (5 Demo Emails) on a mixed set of valid, invalid, and disposable addresses, then Database migration audit, Sales Outreach Pre-Flight, or CRM Hygiene Audit (bulk-validate up to 1,000 addresses from an existing CRM export).

Open Bulk Email Syntax & MX Validator on Apify

Limits to keep in mind

Open Bulk Email Syntax & MX Validator on Apify

Related pages