Email Verifier — Honest Grades, No False Certainty
Pricing
from $4.00 / 1,000 results
Email Verifier — Honest Grades, No False Certainty
Verify email lists without sending mail. Syntax, MX records, disposable domains, role accounts and typo detection. Every result explains its verdict.
Pricing
from $4.00 / 1,000 results
Rating
0.0
(0)
Developer
alaudin burki
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
2 days ago
Last modified
Categories
Share
Verify email lists without sending mail. Syntax, MX records, disposable domains, role accounts and typo detection. Every result explains its verdict.
Built reliability-first: every row reports what was found and what was missing — you never get a silent blank, and a run summary tells you exactly what happened.
What you get
| Field | Description |
|---|---|
email | |
status | Status |
confidence | Confidence |
reason | Reason |
domain | Domain |
isDisposable | Is Disposable |
isRoleAccount | Is Role Account |
mailServer | Mail Server |
suggestedCorrection | Suggested Correction |
How to use it
- Fill in the input (see the example below).
- Run it once for a snapshot, or schedule it to keep the data fresh.
- Export to CSV/JSON/Excel, or push straight to Google Sheets, Notion, Airtable, Zapier, Make, or n8n.
Input
{"emails": ["john.smith@gmail.com","info@stripe.com","test@mailinator.com","ceo@gmial.com"],"onlyStatus": "all","maxItems": 1000,"concurrency": 10}
Sample output
[{"email": "name@example.com","status": "ok","confidence": "EX12345","reason": "example","domain": "example","isDisposable": true,"isRoleAccount": 1284,"mailServer": "example","suggestedCorrection": "example"}]
Typical uses
- Schedule it and feed the output straight into your sheet, database, or app.
- Pair it with the related actors below to build a complete pipeline.
The 0-100 score
Every address gets a single score and a scoreBand, because that is the metric this market compares on.
| Band | Score | Meaning |
|---|---|---|
safe | 85-95 | A mail server actually confirmed the recipient |
probably_safe | 60-84 | Valid syntax, live mail server, no red flags |
risky | 35-59 | Role account, or a catch-all domain where nothing can be proven |
very_risky | 10-34 | Disposable address, or a near-miss typo of a real domain |
undeliverable | 0-9 | Dead domain, no mail server, or the server rejected it |
Nothing ever scores 100. An address can bounce for reasons no probe can see — a full mailbox, a filter, an employee who left last week. The scale tops out at 95 and that is deliberate.
Scores above 85 require a mail server to have actually answered. Everything below is inference, and the score says so.
Catch-all detection — and an honest warning about it
A catch-all domain accepts mail for every address, real or not. On such a domain "the server
accepted it" proves nothing, and this is the single biggest reason "verified" lists still bounce.
Turn on catchAllCheck and one probe per domain marks these as risky instead of quietly calling
them valid.
Read this before you rely on it: both catchAllCheck and smtpCheck need outbound port 25,
and Apify — like most cloud platforms — blocks it. Verified on the platform: these checks return
smtp_blocked or smtp_timeout, never a false verdict.
So on Apify these two options will usually tell you nothing was learned, and the score correctly stays in the inference range. That is the honest outcome, and it is reported as its own state rather than being folded into "invalid". Competitors that claim SMTP verification from cloud infrastructure are either using relays you are not told about, or guessing.
Everything else — syntax, MX, mail provider, disposable, role, typo correction — works fully and needs no special ports.
Mail provider
mailProvider is read from the MX records: google, microsoft, zoho, proofpoint, mimecast,
proton, amazon-ses, godaddy and others. Useful beyond verification — knowing a prospect runs
Google Workspace vs Microsoft 365 is a real segmentation signal, and it comes free with the lookup.
Pricing
$4.00 / 1,000 results ($0.004 per result), plus a near-zero start fee. You are never charged beyond your limit, and blocked or
failed items are reported honestly — not billed as data.
FAQ & limitations
- Public data only — no login walls, no cookies required.
- Rate limits on the source may require the proxy or a retry on very large pulls.
- Every row reports its own status, so partial results are always labeled, never faked.
- Integrations: output works with Zapier, Make, n8n, and any webhook via Apify's integrations.
- Formats: results export as JSON, CSV, Excel, or HTML from the dataset.
Related actors
- Email Verifier
- Lead List Deduplicator
- Website Contact Finder