Email Validation API - Bulk Email Checker & Verifier
Pricing
from $0.40 / 1,000 results
Email Validation API - Bulk Email Checker & Verifier
Bulk email verification and validation API for lead lists. Check syntax, MX records, disposable/free domains, role accounts, catch-all behavior, and optional SMTP signals. Clean CRM lists and assess email risk without an API key. Results do not guarantee mailbox ownership, reachability, or delivery.
Pricing
from $0.40 / 1,000 results
Rating
0.0
(0)
Developer
Ava Torres
Maintained by CommunityActor stats
2
Bookmarked
119
Total users
3
Monthly active users
15 hours ago
Last modified
Categories
Features
Share
Bulk Email Verification & Validation API ($0.50/1K)
Assess email addresses in bulk with no API key required. Check list-quality signals before campaigns and flag records that need review. Results are risk signals, not proof that a mailbox is owned, reachable, or able to receive a particular message.
What it does
For each email address, the actor checks:
- Syntax validation - RFC-compliant email format check
- MX record lookup - Reports whether DNS mail-exchanger records are configured for the domain
- Disposable domain detection - Flags temporary/throwaway email services (Mailinator, Guerrilla Mail, etc.)
- Free provider detection - Identifies Gmail, Yahoo, Outlook, etc.
- Role account detection - Flags generic addresses (info@, admin@, support@, etc.)
- Optional catch-all signal - Reports catch-all behavior only when SMTP checking observes it
- Domain typo suggestions - Suggests corrections (gmial.com -> gmail.com)
- Optional SMTP signal - Attempts to observe whether a mail server accepts the address, subject to provider blocking, greylisting, catch-all behavior, and other inconclusive responses
Use cases
- CRM cleanup - Flag structurally invalid, disposable, or domain-risk records for review
- Lead-list checks - Assess scraped email lists before outreach
- Email campaign prep - Identify obvious list-quality risks before sending
- Data quality - Flag disposable, role-based, and catch-all addresses
- List hygiene - Identify free vs business email addresses
Input
| Field | Type | Description |
|---|---|---|
| emails | string[] | Email addresses to validate |
| enableSMTP | boolean | Enable SMTP reachability check (default: false) |
| maxResults | integer | Maximum paid dataset items (default demo: 5; max: 100,000) |
| concurrency | integer | Parallel validations (default: 5, max: 20) |
Output
Each email produces a result with:
valid means the syntax is valid, an MX record exists, and the domain is not flagged as disposable. It does not mean the mailbox or owner was verified.
{"email": "user@gmail.com","valid": true,"syntaxValid": true,"mxFound": true,"disposable": false,"freeProvider": true,"roleAccount": false,"catchAll": false,"domain": "gmail.com","localPart": "user","mxRecords": "gmail-smtp-in.l.google.com, alt1.gmail-smtp-in.l.google.com"}
Use with AI Assistants (MCP)
This actor works as an MCP tool with Claude Desktop, Cursor, and other MCP clients.
Setup: Add this to your MCP client configuration:
{"mcpServers": {"email-validator": {"url": "https://mcp.apify.com?tools=pink_comic/email-validation-checker"}}}
Then ask your AI: "Validate these email addresses: john@example.com, sales@acme.com" -- it will run the validator and return results.
Pricing and first run
- $0.0005 per result ($0.50 per 1,000)
- No start fee
- The default five-address demo costs at most $0.0025
maxResultsand an Apify maximum-total-charge limit both cap paid output- Bulk Apify output is written in bounded 1,000-row batches so large advertised workflows do not depend on one oversized dataset request
No API key or external account is needed.
Evidence limits
SMTP checking is disabled by default because datacenter IPs are frequently blocked, servers can greylist requests, and catch-all/provider policies can produce misleading or inconclusive signals. Syntax, MX, and disposable-domain checks establish domain-level risk indicators only.
The output does not prove mailbox ownership, consent, live reachability, inbox placement, message delivery, or compliance with anti-spam rules. Treat smtpReachable as a point-in-time signal and valid as the documented structural/domain rule—not a deliverability guarantee.
How to use
- Open Email Validation API - Bulk Email Checker & Verifier in Apify Console and click Start (or Try for free).
- Fill in the input form - start with Email Addresses, Max Results, Concurrency. Every field is optional unless marked required, and the form is prefilled with a working example.
- Set Maximum results to cap your cost, then run the Actor.
- Download the results as JSON, CSV, Excel, XML or HTML, or pull them with the Apify API.
Example input
{"emails": ["test@gmail.com","user@mailinator.com","ceo@apple.com","info@microsoft.com","fake@nonexistent-domain-12345.com"],"enableSMTP": false,"maxResults": 100,"concurrency": 5}
Output example
One record from a real run (long values shortened, contact details partly masked):
{"email": "t***@gmail.com","valid": true,"syntaxValid": true,"mxFound": true,"disposable": false,"freeProvider": true,"roleAccount": false,"catchAll": false,"domain": "gmail.com","localPart": "test","mxRecords": "gmail-smtp-in.l.google.com, alt1.gmail-smtp-in.l.google.com, alt2.gmail-smtp-in.l.google.com, alt3.gmail-smtp-in.l.google.com, alt4.gmail-smtp-in.l.google.com"}
FAQ
How much does Email Validation API - Bulk Email Checker & Verifier cost?
$0.0005 per result. For example, 1,000 results cost about $0.50. Higher Apify plans get a Store discount.
Do I need an API key or login?
No. Just configure the input and run it.
Can I run it on a schedule or from code?
Yes. Use Apify Schedules for recurring runs, or call it from the Apify API, the JavaScript or Python client, Make, Zapier, n8n, or any MCP-compatible AI agent.
Why did my run return no results?
Your filters are probably too narrow. Remove a filter or broaden the search, then run again. You only pay the result price for records that are actually saved.
Is the data accurate and up to date?
Each run fetches live data from the source described above, so results are as current as that source. Verify critical records with the original source before acting on them.