Disposable Email Validator
Pricing
Pay per usage
Disposable Email Validator
Under maintenanceValidate email addresses via syntax, MX, SMTP RCPT probe, disposable-domain list, free-mail flag, role-account flag, and catch-all detection. Self-contained — no upstream paid API.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
jts
Actor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
What this Actor does
Validate email addresses via syntax, MX, SMTP RCPT probe, disposable-domain list, free-mail flag, role-account flag, and catch-all detection. Self-contained — no upstream paid API.
Input example
{"emails": ["founder@linear.app","user@mailinator.com","info@example.com"],"checkSmtp": true,"smtpTimeoutMs": 5000,"treatCatchAllAsValid": false}
Input fields
Provide a list of email addresses to validate. Each email is checked for syntax, MX records, optional live SMTP RCPT probe, disposable-domain blocklist, free-mail providers, and role accounts.
emails(array, user input): Email addresses to validate. Each address is normalized (lowercased, trimmed) and checked independently.checkSmtp(boolean, user input): When true, the actor opens a TCP connection to the recipient MX host on port 25 and runs HELO / MAIL FROM / RCPT TO / QUIT. Many cloud providers block outbound port 25; in that case smtpValid is null with reason smtp_blocked.smtpTimeoutMs(integer, user input): Per-connection timeout in milliseconds for the SMTP probe.treatCatchAllAsValid(boolean, user input): If a domain accepts mail for a known-bogus probe address, it is a catch-all and the target mailbox cannot be confirmed. When true the result is still marked valid; when false catch-all results are marked unknown.
Output dataset
Each successful upstream response is written to the default dataset.
input: Original input value submitted to the upstream API.result: Full upstream API response.
Developer notes
Set DISPOSABLE_EMAIL_VALIDATOR_API_KEY as an Apify secret environment variable. The Actor forwards it as X-API-Key to the upstream API.
Use apiBaseUrl only for local or staging QA. Production runs default to the deployed API base URL from service.json.
For advanced testing, a requests array can call explicit API paths; normal users should use the service-specific fields above.
Run locally
$apify run
Deploy
$apify push