Bulk Email Verifier & List Cleaner
Pricing
from $2.00 / 1,000 verified emails
Bulk Email Verifier & List Cleaner
Bulk-validate email addresses: syntax, MX, disposable/role-based detection. For cold-email hygiene at scale.
Pricing
from $2.00 / 1,000 verified emails
Rating
0.0
(0)
Developer
GoCreative AI
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Verify and clean email lists in bulk — remove invalid, dead, disposable, and risky addresses before you send. Paste or upload thousands of emails and get back a clean, scored list so you can cut bounce rates, protect your sender reputation, and stop wasting sends on addresses that will never land.
No API key. No signup. No monthly subscription — pay only for what you verify.
What it does
For every email address you submit, this actor checks:
- Syntax validation — catches typos and malformed addresses (
john@@gmail,notanemail, missing TLDs) using strict RFC-style rules. - MX record lookup — confirms the domain actually has mail servers that can receive email. Dead domains and parked domains are flagged as undeliverable.
- Disposable / temporary email detection — flags throwaway domains (Mailinator, Guerrilla Mail, 10MinuteMail, and many more) that hurt deliverability and inflate lists.
- Role-based address detection — flags shared inboxes (
info@,support@,sales@,admin@) that convert poorly and often trigger spam filters. - Free-provider classification — labels Gmail / Outlook / Yahoo / iCloud so you can segment business vs personal.
- Catch-all & SMTP mailbox check (optional) — when run on a network with outbound port 25 open, it probes the mail server (
RCPT TO) to confirm the mailbox exists and detect catch-all domains. (Most cloud networks block port 25, so this is off by default — syntax + MX + classification still reliably removes the bulk of bad addresses.)
Every result comes back with a clear status (valid, risky, undeliverable) and a 0–100 confidence score, plus all the underlying signals so you can filter exactly how you want.
Why use it
- Lower bounce rates — bounces above ~3% get your domain throttled or blacklisted. Clean the list first.
- Protect sender reputation — fewer bounces and spam-traps means more of your email reaches the inbox.
- Save money on your email tool — stop paying per-contact for addresses that don't exist.
- Clean cold-email & lead lists at scale — drop it into any outreach, CRM, or scraping pipeline.
Input
| Field | Type | Description |
|---|---|---|
emails | array | List of email addresses to verify. Duplicates are removed automatically. |
smtpCheck | boolean | Optional SMTP mailbox probe + catch-all detection. Off by default (needs port 25). |
fromEmail | string | Sender address used during SMTP probing. Use a domain you control. |
maxConcurrent | integer | Parallel checks (1–50). Default 10. |
Example input
{"emails": ["support@apify.com","totallyfake_zzz999@gmail.com","notanemail","test@mailinator.com"]}
Output
One record per address:
{"email": "support@apify.com","status": "risky","score": 50,"reason": "role_based_address","syntax_valid": true,"domain": "apify.com","mx_found": true,"mx_host": "aspmx.l.google.com","is_disposable": false,"is_role": true,"is_free": false}
Status values:
valid— clean syntax, live mail domain, not disposable/role. Safe to send.risky— deliverable but lower-quality (disposable, role-based, or catch-all domain). Send with caution.undeliverable— invalid syntax, no mail server, or the mailbox was rejected. Remove these.
How to use the results
Filter to status == "valid" for your safest sending list, keep risky for a separate lower-priority segment, and drop everything undeliverable. Export to CSV, JSON, or Excel from the Apify dataset, or pull it via the API into your own pipeline.
FAQ
Does it really connect to mail servers? It always checks syntax and live MX records. The full SMTP mailbox probe is optional and only works where outbound port 25 is open (most cloud platforms, including Apify, block it), so it's off by default.
How fast is it? Hundreds to thousands of addresses per run, controlled by maxConcurrent.
Do I need an account or API key? No. Just provide your list and run.