Bulk Email Verifier

Clean your email lists fast and reliably — no external API, no anti-bot walls, no per-check third-party fees. Paste up to 100,000 addresses and get back a clear verdict for each: deliverable, risky, or undeliverable, with a 0–100 score and the reasons.

What it checks

Check	What it catches
Syntax	Malformed addresses (RFC-style validation)
MX records	Domains that can't receive mail at all (dead / parked domains)
Disposable	Temp-mail providers (mailinator, guerrillamail, 10minutemail, …)
Role accounts	info@, sales@, support@, noreply@ — deliverable but not a person
Free providers	gmail / outlook / yahoo / icloud … (tagged, not penalised)
Typos	gmial.com → suggests gmail.com (with a "did you mean")
Suspicious locals	Random-hash tracking addresses

Why this one

Most Trustpilot-of-email-verifier actors are thin wrappers over a paid API — you pay them, they pay someone else, and if that API hiccups your run fails. This actor does the checking itself: pure DNS + logic, so it's fast, transparent, and it doesn't break when a third party does. Every verdict comes with the exact reason, so you can trust it.

Input

{
    "emails": ["john.doe@gmail.com", "info@apify.com", "test@mailinator.com", "user@gmial.com"],
    "checkMx": true,
    "concurrency": 20
}

• emails — the list to verify (max 100,000)
• checkMx — look up MX records (on by default; turn off for a faster syntax-only pass)
• concurrency — addresses verified in parallel (default 20)

Output (one record per email)

{
    "email": "info@apify.com",
    "status": "risky",
    "score": 85,
    "domain": "apify.com",
    "syntaxValid": true,
    "mxFound": true,
    "isDisposable": false,
    "isRole": true,
    "isFreeProvider": false,
    "didYouMean": null,
    "reason": "role_account"
}

Status meaning:

• deliverable — valid syntax, domain accepts mail, no red flags
• risky — deliverable but flagged (role account, disposable, likely typo, placeholder)
• undeliverable — bad syntax or the domain has no mail servers
• unknown — MX check was skipped (checkMx: false)

Use cases

• Clean a list before a campaign to protect your sender reputation and cut bounces
• De-dupe and tag leads (person vs. role, free vs. business)
• Validate signups in bulk

Notes

This actor verifies syntax, domain, and reputation — the reliable layer of email validation. It does not open an SMTP connection to each mailbox (that's routinely blocked by mail servers and unreliable due to catch-all configs), so a deliverable result means "valid and the domain accepts mail," not a guaranteed inbox. That's the honest, dependable signal — and it's what actually protects your bounce rate.