Bulk Email Validator - MX, Disposable, Role & Typo Check avatar

Bulk Email Validator - MX, Disposable, Role & Typo Check

Pricing

from $0.49 / 1,000 email verifieds

Go to Apify Store
Bulk Email Validator - MX, Disposable, Role & Typo Check

Bulk Email Validator - MX, Disposable, Role & Typo Check

Bulk email validator and list cleaner: syntax, MX records, disposable domains, role accounts, typo hints, free-provider flag, SPF and DMARC per address. No API key, no email sent.

Pricing

from $0.49 / 1,000 email verifieds

Rating

0.0

(0)

Developer

Detroit Web Agent - Open Data

Detroit Web Agent - Open Data

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

12 days ago

Last modified

Features

Limited permissions

Share

Bulk Email Validator: MX, Disposable, Role & Typo Check

Use this to clean an email list before you send to it. Paste addresses, press Start, and get one row per address with a verdict (valid, risky, invalid), a 0-100 score and a plain-English reason. It checks syntax, whether the domain has a mail server (MX record), whether the domain is a disposable or throwaway one, whether the address is a role account (info@, sales@), and whether the domain looks like a typo of a big provider (gmial.com, hotmial.com, .con).

It needs no API key, no login and no proxy, and it never sends an email.

Run in 30 seconds

  1. Open the Input tab. The prefilled list (26 addresses: real company mailboxes, disposable domains, typos and malformed lines) is a ready-to-run test.
  2. Click Start. The default run normally finishes in well under a minute.
  3. Open the Emails table in the Output tab, or download the dataset as JSON, CSV, Excel or HTML.
  4. Replace the list with yours and run again.

What does this Actor do?

For every address the Actor returns a flat, spreadsheet-ready row:

GroupFields
Verdictstatus (valid, risky, invalid), score (0-100), reason
SyntaxsyntaxValid, domain
Mail servermxFound, mxHost (lowest-priority-number MX, falling back to the A record)
Flagsdisposable, roleAccount, freeProvider, didYouMean (for example gmial.com becomes gmail.com)
Domain mail policyspf, dmarc
Mailbox probe (experimental)smtpCheck, catchAll

A run also saves a summary to the key-value store under OUTPUT: unique addresses, duplicates skipped, counts by status, and any warnings.

Limits: what this can and cannot tell you

  • It does not confirm that a mailbox exists. Confirming a single mailbox needs an outbound connection on port 25, which Apify and most cloud networks block. A valid verdict means: the syntax is right, the domain has a working mail setup, and it is not a disposable domain. It does not mean the person reads that mail.
  • Experimental mailbox probe. The optional smtpCheck input tries the port-25 handshake anyway. On Apify it normally reports blocked and the row falls back to the domain-level result. Nothing is guessed.
  • No email is sent. Ever.
  • Role accounts such as info@ and sales@ are valid mailboxes but often shared or filtered. They lose 15 points and are flagged, not rejected.
  • The disposable-domain list is bundled in the Actor and is a snapshot, so brand-new throwaway domains may be missed.

Input

FieldWhat it does
emailsOne address per line. Blank lines and duplicates are skipped and not charged.
smtpCheckExperimental port-25 mailbox probe. Default off, see Limits.
catchAllCheckWith the probe, also test a random impossible address. Default off.
smtpMailFromEnvelope sender for the experimental probe. Nothing is delivered to it.
maxItemsStop after this many unique addresses.

Example input

{
"emails": ["support@apify.com", "someone@gmial.com", "test@mailinator.com", "not-an-email"],
"maxItems": 100
}

Output sample

{
"email": "dev@hotmail.con",
"status": "invalid",
"score": 0,
"reason": "domain has no mail server (no MX or A record); did you mean hotmail.com",
"syntaxValid": true,
"domain": "hotmail.con",
"mxFound": false,
"disposable": false,
"roleAccount": false,
"didYouMean": "hotmail.com"
}

Your own run will show the real values for every field.

How the score works

Start at 100, capped at 90 because the mailbox itself is not confirmed. Subtract 70 for a disposable domain, 15 for a role account and 10 for a probable typo. Bad syntax or a domain with no mail server is invalid (0). 80 and above is valid, 1 to 79 is risky.

Use cases

  • Clean a newsletter or cold-outreach list before sending, to cut bounces.
  • Check sign-up emails in a CRM export and flag disposable addresses.
  • Catch typos such as gmial.com, hotmial.com or .con endings.
  • Separate role accounts from named people.

Tips for good results

  • Run a small sample first and read the reason column.
  • Treat risky as "send with care", not as bad.
  • Sort by score and review the lowest rows first.

Field reference

status is the verdict. score is the 0-100 number described above. mxFound is true when the domain publishes MX records or at least an address record. spf and dmarc are true when the domain publishes those DNS records. smtpCheck and catchAll are only filled when you turn on the experimental probe and the server is reachable on port 25 (accepted, rejected, unknown, blocked, provider_hidden).

Pricing and cost control

Pay per address: $0.0008 per email on the free plan, $0.00049 on the Gold plan (Bronze $0.00075, Silver $0.00064), plus a $0.00005 start fee per run. That is $0.80 per 1,000 emails on the free plan. Duplicates and blank lines are never charged. Use "Maximum cost per run" or maxItems to cap spend; the run stops cleanly at the limit.

API and AI agents

$curl -X POST "https://api.apify.com/v2/acts/transparent_meteorite~bulk-email-verifier/run-sync-get-dataset-items?token=YOUR_TOKEN" -H "Content-Type: application/json" -d '{"emails": ["support@apify.com", "someone@gmial.com"], "maxItems": 100}'
from apify_client import ApifyClient
client = ApifyClient("YOUR_TOKEN")
run = client.actor("transparent_meteorite/bulk-email-verifier").call(run_input={"emails": ["support@apify.com"]})
for row in client.dataset(run["defaultDatasetId"]).iterate_items():
print(row)

AI agents (MCP): add the Apify MCP server (https://mcp.apify.com) with this Actor enabled, then ask an assistant such as Claude or ChatGPT to "verify these 500 emails and drop the disposable ones".

Integrations and scheduling

Send results to Google Sheets, Slack, email, Make, Zapier or n8n with the Apify integrations, or call the Actor from your code through the REST API and the Python and JavaScript clients. Open the API tab for ready-to-copy snippets.

The Actor only analyses addresses you provide, using public DNS records and the standard mail-server handshake. It does not scrape any website, and it sends no message. You are responsible for complying with email and privacy laws (such as GDPR and CAN-SPAM) when you contact the people on your list.

FAQ

Does it send an email to the address? No.

Does it confirm the mailbox exists? No, see Limits. It tells you whether the address is well-formed, the domain can receive mail, and the address is not a known throwaway or an obvious typo.

Why is a good-looking address risky? Usually a disposable domain or a role account. The reason column lists each cause.

Are duplicates charged? No.

What if my list has 100,000 addresses? Set maxItems high enough. If the run reaches its time limit, the Actor stops cleanly and the summary lists how many were not checked, and those are not charged.

Do I need an API key? No.

Support

Found a bug or need a field? Open an issue on the Issues tab with the run URL and you will get a reply there.

Changelog

  • 0.1: First private build. Syntax, MX, disposable, role, typo, SPF and DMARC checks, plus an experimental port-25 probe.