Bulk Email Verifier & Email List Cleaner

Clean email lists with syntax checks, DNS MX/A checks, disposable-domain detection, role-account flags and typo hints. This email validation API sends no email and never uses SMTP.

Use cases

• Clean CRM/newsletter imports before sending.
• Block disposable sign-ups and flag generic role mailboxes.
• Verify email addresses in n8n, Make, or a custom API workflow.
• Catch provider typos such as bob@gmial.com.

Input

{"emails":["anna.svensson@telia.com","info@scb.se","x@mailinator.com","bob@gmial.com","ceo@startup.io","john.doe@outlook.com"],"checkMx":true}

Real output sample

input	verdict	score	reasons	mxStatus	disposable	roleAccount
test@mailinator.com	risky	30	disposable_domain	mx	true	false
john.doe@gmail.com	valid	100	—	mx	false	false
bad@@x	invalid	0	invalid_syntax	—	false	false
support@hm.com	valid	90	role_account	mx	false	true
anna@gmial.com	risky	1*	no_mx_a_record_fallback, disposable_domain, possible_domain_typo	a_record_only	true	false

Sample from a real platform run (input order differs). Current versions floor risky scores at 20. Every row includes inputIndex, normalizedInput, input, email, reasons, and DNS/classification fields; input_normalized explains a normalization.

Verdicts and limits

valid means syntax passed and the domain advertises MX; it does not prove that an inbox exists. risky means disposable, probable typo, role mailbox, or A-record fallback. invalid means bad syntax, reserved domain, or no receiving DNS. unknown means DNS was inconclusive and is not charged.

There is no SMTP probing: it is slower, unreliable, and can resemble unsolicited mailbox testing. Catch-all domains cannot be identified with DNS alone. Gmail/Outlook results are domain-level checks. The free plan caps 100 checked addresses per run; capped inputs remain visible as deferred rows.

Pricing

List	Usage charge
1,000 addresses	$1 + start fee
100,000 addresses	$100 + start fee

Only successful checks are charged; duplicates, blanks, and unknown DNS results are not. The free-plan cap is 100 addresses.

API and clients

$curl -X POST 'https://api.apify.com/v2/acts/interconnected_seaport~bulk-email-verifier-mx/run-sync-get-dataset-items?token=YOUR_TOKEN' -H 'content-type: application/json' -d '{"emails":["a@example.com"],"checkMx":true}'

const { ApifyClient } = require('apify-client');
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('interconnected_seaport/bulk-email-verifier-mx').call({ emails: ['a@example.com'] });
console.log(await client.dataset(run.defaultDatasetId).listItems());

from apify_client import ApifyClient
client = ApifyClient()
run = client.actor('interconnected_seaport/bulk-email-verifier-mx').call(run_input={'emails': ['a@example.com']})
print(client.dataset(run['defaultDatasetId']).list_items().items)

n8n and Make can call the same Apify actor endpoint and iterate over dataset items.

FAQ

Does valid mean the inbox exists? No; it means syntax is acceptable and the domain can receive mail.

Why no SMTP? SMTP probing is slow, often blocked, and can resemble abuse; this actor performs DNS-only checks.

What about catch-all domains? DNS cannot distinguish a catch-all from a real mailbox.

Is unknown free? Yes. DNS-inconclusive results are written but not charged.

Can I process large lists? Yes, subject to your plan and the free-plan cap of 100.

GDPR and lawful use

Email addresses are personal data in many jurisdictions. Use a lawful basis, limit retention, secure exports, and honor deletion/access requests. The actor sends no mail and queries only DNS, but you remain responsible for lawful processing, consent, and provider terms. No evasion or SMTP probing is performed.