Email Validator — Bulk Syntax, Domain & MX Record Checks avatar

Email Validator — Bulk Syntax, Domain & MX Record Checks

Pricing

from $1.20 / 1,000 email validateds

Go to Apify Store
Email Validator — Bulk Syntax, Domain & MX Record Checks

Email Validator — Bulk Syntax, Domain & MX Record Checks

Validate email addresses in bulk: syntax, domain DNS, MX records, role and free-provider flags, with a valid, risky or invalid status. USD 1.50 per 1,000.

Pricing

from $1.20 / 1,000 email validateds

Rating

0.0

(0)

Developer

Muhammad Afzal

Muhammad Afzal

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

1

Monthly active users

19 days ago

Last modified

Features

Limited permissions

Share

Email Validator checks up to 10,000 email addresses per run for valid syntax, a resolvable domain, working MX records, role accounts, free-provider domains and about 56,000 known disposable domains, and returns one row per address with a valid, risky or invalid status and the reasons. It is made for lead-generation teams, CRM admins and AI agents cleaning a list before outreach or import, and costs about USD 1.50 per 1,000 emails on the FREE tier (USD 0.001501 each; USD 1.20 per 1,000 on GOLD).

What does the email validator check?

Each address you submit becomes one dataset row:

FieldWhat it contains
emailThe address exactly as you submitted it
normalizedEmailTrimmed address with the domain converted to ASCII (IDNA), or null when parsing failed
statusvalid, risky or invalid
isValidtrue for valid and risky, false for invalid
confidence0.95 for valid, 0.65 for risky, 0.15 for invalid
syntaxValidWhether the address matches a safe RFC-style mailbox format
domain, domainAscii, localPartThe parts of the address used for the checks
dnsChecked, domainHasDnsWhether the DNS check ran, and whether the domain has A, AAAA or MX records
mxChecked, hasMx, mxRecordsWhether the MX check ran, whether MX records exist, and the mail servers sorted by priority
isDisposableWhether the domain, or a parent domain, is on the built-in list of about 56,000 temporary mailbox domains
isRoleAccountWhether the mailbox is generic, such as info@, sales@ or support@
isFreeProviderWhether the domain is a common consumer provider such as gmail.com or outlook.com
reasonsPlain-English reasons for the result
checkedAtISO 8601 time of the check

A run summary is saved to the OUTPUT key-value record with total, valid, risky and invalid counts.

How do I validate a list of emails in bulk?

Paste the addresses into Email addresses (one per line), or paste any text into Text containing emails and the Actor pulls out every address it finds. Duplicates are removed case-insensitively, and Maximum emails caps how many unique addresses one run processes (default 1,000, up to 10,000). Addresses are checked one at a time; a three-address run finished in about 2 seconds on 2026-10-26.

{
"emails": ["john@apify.com", "sales@example.org", "bad@@example"],
"emailText": "",
"checkDns": true,
"checkMx": true,
"allowDisposable": false,
"allowRoleAccounts": true,
"outputInvalidOnly": false,
"maxEmails": 1000
}

Turn on Output invalid only when you only want the rejects in the dataset; every address is still checked, counted in OUTPUT and charged.

What do valid, risky and invalid mean?

invalid means the address fails a hard check: bad syntax, no MX records or a failed MX lookup, no DNS records, or a disposable domain while Allow disposable emails is off. risky means the address is usable but lower quality: a consumer free-provider domain (always), a role account while Allow role accounts is off, or a run with the DNS or MX check switched off. valid means the address passed every enabled check.

A gmail.com, outlook.com or yahoo.com address therefore comes back risky with confidence 0.65, never valid, because the Actor is tuned for B2B lead quality. Filter on isFreeProvider if consumer addresses are fine for you.

Is this an email verifier?

No, it validates rather than verifies: it never connects to the mail server or sends anything, so it cannot confirm that a specific mailbox exists or detect catch-all domains. It tells you whether an address is well formed and whether its domain can receive mail at all, which removes typos, dead domains and obvious junk cheaply before a mailbox-level verification or a send.

When should I use it, and when not?

Use Email Validator to clean a scraped or imported list before enrichment, CRM import or outreach, to screen sign-up addresses in batch, or to give an AI agent a quick yes/no on addresses it collected.

Do not use it when:

  • You need proof that a mailbox exists or will not bounce. Use a mailbox-level (SMTP) verification service.
  • You need the freshest disposable-domain coverage. The built-in list holds about 56,000 known temporary mailbox domains and is updated only when the Actor is rebuilt. Check domains against a list of about 98,500 disposable domains, refreshed on every run, with Disposable Email Domains List & Checker.
  • You need to find email addresses. Extract contact fields from public pages with AI Web Scraper.

How do I call it from the API?

JavaScript (apify-client):

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('muhammadafzal/email-address-validator').call({
emails: ['alex@example.com', 'bad@@example'],
checkDns: true,
checkMx: true,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.map((i) => `${i.email}: ${i.status}`));

Python (apify-client):

from apify_client import ApifyClient
client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("muhammadafzal/email-address-validator").call(run_input={
"emails": ["alex@example.com", "bad@@example"],
"checkDns": True,
"checkMx": True,
})
for item in client.dataset(run.default_dataset_id).iterate_items():
print(item["email"], item["status"], item["reasons"])

Use it from an AI assistant

Email Validator works from Claude, ChatGPT, Cursor or any MCP client through Apify's MCP server. Add the single-tool URL https://mcp.apify.com/?tools=muhammadafzal/email-address-validator to your client, then ask, for example: "Validate these 12 email addresses and tell me which ones have no MX records or look like role accounts." The assistant passes the list, runs the check and summarises the statuses.

Output example

The three prefill addresses, from a run on 2026-10-26 (shortened):

[
{
"email": "john@apify.com",
"status": "valid",
"isValid": true,
"confidence": 0.95,
"syntaxValid": true,
"domainAscii": "apify.com",
"hasMx": true,
"mxRecords": ["aspmx.l.google.com", "alt1.aspmx.l.google.com"],
"isDisposable": false,
"isRoleAccount": false,
"isFreeProvider": false,
"reasons": ["Email passed all enabled validation checks."]
},
{
"email": "sales@example.org",
"status": "invalid",
"isValid": false,
"confidence": 0.15,
"syntaxValid": true,
"domainHasDns": true,
"hasMx": false,
"mxRecords": [],
"isRoleAccount": true,
"reasons": ["Domain has no MX records."]
},
{
"email": "bad@@example",
"normalizedEmail": null,
"status": "invalid",
"syntaxValid": false,
"reasons": ["Email must contain exactly one @ sign."]
}
]

Pricing: how much does email validation cost?

Email Validator uses pay-per-event pricing, with platform usage included.

EventFREEBRONZESILVERGOLDPLATINUM / DIAMOND
Email validated (each processed address)USD 0.001501USD 0.001463USD 0.001425USD 0.0012USD 0.0012
Actor start (per started GB of allocated memory)USD 0.006251USD 0.006094USD 0.005938USD 0.005USD 0.005

These prices have applied since 20 September 2026, and no change is scheduled. Default memory scales with Maximum emails and stays at or under 1 GB, so a run pays one start event.

Worked totals on the FREE tier:

  • 1,000 emails: 1,000 × USD 0.001501 + USD 0.006251 = USD 1.51
  • 10,000 emails: 10,000 × USD 0.001501 + USD 0.006251 = USD 15.02

Every processed address is charged, including invalid ones and those hidden by Output invalid only. A result that cannot be stored is listed in OUTPUT.summary.notStored and not charged. The estimatedPpeCostUsd value in OUTPUT and the cost in the run status message use the live per-email price of your pricing tier. Set a maximum cost per run in Apify Console to cap spending; the run stops cleanly when it is reached.

FAQ

Does it send emails or log in to the mail server?

No. It only parses the address and runs DNS and MX lookups on the domain.

Why is my gmail.com address marked risky?

Consumer free-provider domains are always marked risky because they are lower-signal for B2B lists. The address may be perfectly deliverable; use isFreeProvider to keep or drop them.

How complete is the disposable-email check?

It checks each domain and its parent domains (so inbox.mailinator.com counts) against a bundled list of about 56,000 known temporary mailbox domains. New throwaway services appear constantly, so for a list refreshed on every run use Disposable Email Domains List & Checker.

How many emails can I validate in one run?

Up to 10,000 unique addresses. Split larger lists across runs.

Am I charged for invalid addresses?

Yes. Each processed address is one event, whatever its status.

Can I switch off the DNS and MX checks?

Yes, for a syntax-only pass. Addresses that pass syntax are then marked risky, because their domains were not checked.

Is there a free email validator option?

Apify's free plan includes monthly platform credit you can spend here; 1,000 emails cost about USD 1.51 on the FREE tier.

Validation is a data-quality step, not permission to contact anyone. Follow CAN-SPAM, GDPR, CASL and local consent rules, and keep personal data only as long as you need it.

Last verified: 2026-10-27