Email Verifier & Email Validation - Bulk Email Checker avatar

Email Verifier & Email Validation - Bulk Email Checker

Pricing

$2.00 / 1,000 email checks

Go to Apify Store
Email Verifier & Email Validation - Bulk Email Checker

Email Verifier & Email Validation - Bulk Email Checker

Email verifier and email validation API: bulk verify email addresses with syntax, MX, disposable, role and typo checks. Clean email lists cheaply.

Pricing

$2.00 / 1,000 email checks

Rating

0.0

(0)

Developer

Tudor Lane

Tudor Lane

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

12 hours ago

Last modified

Features

Limited permissions

Share

Email verifier and email validation in one bulk tool: check if email addresses are real before you send. Syntax, domain, MX records, disposable/throwaway, role and free-provider flags, plus typo fixes (gmial.com → gmail.com). No SMTP probing, so it is fast and cheap for list cleaning, signups and CRMs.

Use when…

  • You need to check email syntax, MX, disposable, role or free-provider flags before send.
  • A signup, CRM or list-clean agent must bulk-verify addresses without SMTP probing.
  • You want typo suggestions (e.g. gmial.com) and a clear valid/risky/invalid style result.

Price: $0.002 per email check

Try this input

Copy-paste this JSON as the Actor input (it matches a successful run / the default schema):

{
"requests": [
"info@bbc.co.uk",
"someone@mailinator.com",
"bob@gmial.com"
]
}

Sample output (real run 2026-10-25)

One dataset item, shortened:

{
"email": "someone@mailinator.com",
"normalized": "someone@mailinator.com",
"valid_syntax": true,
"domain": "mailinator.com",
"domain_exists": true,
"has_mx": true,
"mx_hosts": [
"mail.mailinator.com",
"mail2.mailinator.com"
],
"disposable": true,
"role_account": false,
"free_provider": false,
"did_you_mean": null,
"score": 20,
"…": "+4 more keys"
}

Check email addresses before you send: syntax, domain, mail (MX) records, disposable/throwaway domains, role addresses, free providers and typos. Up to 5,000 addresses per run.

What it does

  • Syntax check and normalised address
  • Domain exists and has MX (mail) records
  • Disposable / throwaway domains (Mailinator, 10minutemail and ~10,000 more)
  • Role accounts (info@, sales@, support@) and free providers (Gmail, Outlook, Yahoo)
  • Typo suggestion: bob@gmial.com → bob@gmail.com
  • Score 0-100 and a verdict: deliverable_likely / risky / undeliverable / invalid

Quick start

Click Start - the default input already works:

{"requests": ["info@bbc.co.uk", "someone@mailinator.com", "bob@gmial.com"]}

Sample output (real run, 25 Oct 2026)

EmailMail server (MX)DisposableRole addressDid you meanScoreVerdict
info@bbc.co.ukyesnoyesno suggestion85deliverable_likely
someone@mailinator.comyesyesnono suggestion20risky
bob@gmial.comnoyesnobob@gmail.com0risky

Use cases

  1. Clean a mailing list before a campaign to cut bounces.
  2. Sign-up forms: block throwaway addresses and catch typos.
  3. CRM hygiene: flag dead domains and role addresses on old records.
  4. AI agents: check an address in one call before sending.

Pricing

$0.002 per email checked. Invalid input rows are not charged. No subscription.

FAQ

Does it confirm the mailbox exists? No. It does not "ping" the mail server (SMTP check): that is unreliable with catch-all servers and many providers treat it as abuse. The verdict is based on syntax, DNS and lists. Where does the disposable list come from? The open disposable-email-domains project (CC0), refreshed on every build. Can AI agents use it? Yes - via the Apify API, or add https://mcp.apify.com?actors=tudorlane/email-verify to an AI assistant.

Limits & failure modes

  • "deliverable_likely" means the domain can receive mail, not that this exact person's mailbox exists.
  • Catch-all and brand-new disposable domains may slip through.
  • Some typo domains are also on the disposable list, so they show as disposable too.
  • No SMTP mailbox probing — “accepts mail” is inferred from MX/domain signals, not a live RCPT check.
  • Catch-all domains can look valid even when the local part does not exist.
  • DNS failures mark the address as unknown/risky rather than inventing a pass.