Email Verifier — syntax + MX + disposable/role heuristics avatar

Email Verifier — syntax + MX + disposable/role heuristics

Under maintenance

Pricing

from $0.10 / 1,000 email verifieds

Go to Apify Store
Email Verifier — syntax + MX + disposable/role heuristics

Email Verifier — syntax + MX + disposable/role heuristics

Under maintenance

Bulk email verification and list cleaning: syntax, DNS MX, disposable-domain and role-account detection, optional SMTP RCPT probe with catch-all detection, 0-100 deliverability score. Pay per decisive result, $0.125 per 1,000. No third-party validation service, no email retention.

Pricing

from $0.10 / 1,000 email verifieds

Rating

0.0

(0)

Developer

Karl Sundström

Karl Sundström

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

3 days ago

Last modified

Categories

Share

Email Verifier: deliverability, catch-all and risk score

Bulk email verification for list cleaning before a campaign: syntax check, DNS MX lookup, disposable-domain and role-account detection, an optional SMTP RCPT probe with catch-all detection, and a 0-100 deliverability score per address. No third-party validation services in the chain. No email retention: addresses exist only for the duration of the run.

Pricing

You are charged per decisive result, not per address scanned. Unknown and catch-all-uncertain outcomes are free.

ItemPrice
Run start$0.002
Decisive result (valid, invalid or disposable)$0.00125 ($1.25 per 1,000)
Unknown or catch-all-uncertain result$0
Max spend per run$5

Comparison

FeatureEmail Verifier (this actor)BounceVerifyEmail Verifier & ValidatorMillion Verifier wrapper
Price$1.25 / 1k decisive results$0.89 / 1k emails$1 / 1k emails$1 / 1k decisive results
Pay per uncertain resultNo (unknown results are free)YesYesNo (decisive only)
Catch-all detectionYes (random-mailbox probe)YesYesYes
Risk score (0-100)YesNoNoNo
Disposable-domain detectionYesYesYesYes
Role-account detectionYesYesYesYes
SMTP RCPT probeOptional, runs in your runService-sideService-sideThird-party service
Third-party verification service in the chainNoneNoneNoneMillion Verifier
Email retentionNot retainedPer provider policyPer provider policyRetained by Million Verifier
Per-run spend cap$5Per-provider billingPer-provider billingPer-provider billing

This actor runs its own DNS and SMTP logic inside your Apify run. Addresses are not sent to any verification service and are not stored after the run.

What data you get

FieldDescription
emailThe address checked (lowercased, trimmed)
statusgood, risky, bad or unknown
score0-100 deliverability score
validDerived boolean (syntax + MX pass, nothing invalidates)
syntaxValidSyntax-level result
mxFoundDNS MX record present
disposableDisposable-domain heuristic hit
roleAccountRole-account heuristic hit (info@, admin@, ...)
freeProviderKnown consumer mailbox provider
catchAllTrue when the domain accepts any mailbox (probe mode)
smtpResultvalid, risky, unknown, invalid or null (probe mode)
technicalReasonSMTP reply code with plain-text DSN meaning
didYouMeanSuggested correction for a likely domain typo
reasonHuman-readable summary of the verdict

How to use

  1. Add the actor to your Apify account and click Run.
  2. Paste addresses into emails. Duplicates are removed automatically and you are charged once per unique address.
  3. Optionally enable smtpProbe for mailbox-level checks.
  4. Export results as JSON, CSV or Excel.

Input

{
"emails": ["karl@example.se", "info@example.org"],
"smtpProbe": false
}

Limitations

These are plain facts about how the checks behave:

  • Datacenter IPs receive greylisting; some servers return unknown rather than a verdict. The actor reports unknown and does not charge for it.
  • On catch-all (accept-all) domains a 250 reply does not prove the mailbox exists. Such results are marked catchAll=true and reported as risky, and are not charged.
  • The disposable-domain list is a static snapshot of the most common disposable providers, not an exhaustive one. disposable=true is reliable; disposable=false does not guarantee a non-disposable domain.
  • Some servers block or rate-limit port 25 probes from datacenter ranges. When the probe cannot connect, the actor reports smtpResult=null with a reason and falls back to DNS-layer checks.
  • Without the probe, the verdict rests on syntax, MX and heuristics. It does not confirm the mailbox exists.
  • did_you_mean suggestions come from a small list of common providers plus domains observed in the run, using a levenshtein distance of 2 or less.