Bulk Email Verifier — MX, Disposable & Typo Detection

Clean an email list before you send to it. Paste addresses or point the Actor at a file, and get back a per-address verdict: which are safe to send to, which will bounce, which are throwaway signups, and which are simple typos you can fix instead of discard.

Built for lead lists exported from Apollo, LinkedIn, Hunter, a CRM, or a signup form.

What it checks

Check	What you get
Syntax	Malformed addresses caught before they cost you a bounce
Domain / MX	Live DNS lookup. Domains that cannot receive mail at all are flagged undeliverable
Disposable	8,000+ throwaway providers (mailinator, 10minutemail, …), from a maintained public blocklist, updated with each release
Typos	gmial.com → gmail.com, yahoo.co → yahoo.com. Returns a corrected address so you can recover the lead instead of deleting it
Role accounts	info@, sales@, support@ — deliverable, but not a person. Flagged separately so you can decide
Free providers	Gmail/Yahoo/Outlook marked, useful when you only want business addresses

Every address gets a safe_to_send boolean and a confidence score. Duplicates are removed automatically, and Gmail's dot/plus aliases (john.doe+news@gmail.com) are folded so you don't pay twice for the same mailbox.

What it does not do — read this before you buy

This Actor does not open an SMTP connection to confirm an individual mailbox exists. Neither does any other Actor on Apify: the platform blocks outbound port 25, which is what an SMTP probe requires.

So when a tool here reports an address as "verified" or "deliverable" with 99% certainty, that number did not come from checking the mailbox. We would rather tell you exactly what we proved:

• undeliverable, disposable, invalid_syntax, typo_suspected — high confidence. These are decided by DNS and syntax, which are authoritative. This is the bulk of what is actually wrong with a real list.
• deliverable_domain — the domain accepts mail; whether that specific mailbox exists is unknown. The field mailbox_verified is always false, because it never was.

For most lists the difference doesn't matter: typos, dead domains and disposables are the overwhelming majority of bad addresses. And for Gmail, Outlook and Yahoo an SMTP probe wouldn't help anyway — they accept-all at the RCPT stage and reveal nothing.

If you need per-mailbox confirmation, use a service that operates its own mail infrastructure. If you need a list cleaned of everything that is provably bad, this is faster and far cheaper.

Input

Any one of these:

• Paste addresses into the text box — one per line, or separated by commas/semicolons/spaces
• JSON array via emails, when calling from the API
• File URL via fileUrl — a public .txt or single-column .csv link (a header row named email is skipped)

{
  "emailsText": "john.doe@gmail.com\ninfo@apify.com\nsomeone@gmial.com",
  "concurrency": 50
}

Output

One row per input address, in the order you supplied them:

{
  "email": "someone@gmial.com",
  "normalized": "someone@gmial.com",
  "domain": "gmial.com",
  "status": "typo_suspected",
  "reason": "domain looks like a misspelling of gmail.com",
  "suggestion": "someone@gmail.com",
  "confidence": 88,
  "safe_to_send": false,
  "disposable": false,
  "role_account": false,
  "free_provider": false,
  "mailbox_verified": false
}

Statuses: deliverable_domain, role_account, undeliverable, disposable, typo_suspected, invalid_syntax, unknown.

unknown means the DNS lookup timed out — the address is not condemned, just unresolved. Re-run those, or raise DNS timeout in the input.

Pricing

Free. There is no per-address fee and no markup on top of it — you pay only the Apify platform compute your own run consumes, which for this Actor is a fraction of a cent per thousand addresses.

For comparison, verifying 100,000 addresses costs roughly two cents of compute here. Paid alternatives on this Store charge between $0.00089 and $0.10 per address for the same category of checks.

Duplicates are removed before any work is done, so you never pay compute for the same mailbox twice.

Speed

Roughly 300 addresses/second on a list of entirely distinct domains, and over 1,000/second on typical lead lists, where many contacts share the same company domain — results are cached per domain within a run, so a 5,000-contact export from one company costs one DNS lookup, not 5,000.

Common uses

• Cleaning a cold-outreach list before import, to protect sender reputation
• Filtering disposable signups out of a product's user table
• Recovering mistyped addresses from a webform instead of losing the lead
• Splitting business addresses from personal ones for B2B campaigns

FAQ

Will this stop my emails bouncing? It removes the addresses that are provably undeliverable, which is where most bounces come from. It cannot promise a zero bounce rate — nothing that doesn't own mail infrastructure can.

Why is confidence 70 for a good address? Because the domain was confirmed and the mailbox was not. We don't inflate that number.

Do you keep my list? Results go to your own dataset on your account. The Actor sends your addresses to no third party; the only outbound traffic is DNS queries for the domains.