Disposable Email Checker
Under maintenancePricing
$1.00 / 1,000 email checks
Disposable Email Checker
Under maintenanceDetect 1M+ disposable, temporary and throwaway emails across Gmail, Outlook, Hotmail, Yahoo, education and private domains. Single and bulk checks with hourly updates. Global edge API: warm p95 latency <20 ms across four benchmarked regions.
Pricing
$1.00 / 1,000 email checks
Rating
5.0
(1)
Developer
Irondome Dev
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
Detect disposable, temporary and throwaway email addresses with single or bulk email checks. IronDome covers more than 1 million disposable email addresses across Gmail, Outlook, Hotmail, Yahoo, education and private domains. Detection data updates every hour.
The global edge API achieved warm p95 latency below 20 ms in all four tested regions in the published benchmarks, using reused connections. These are API measurements; total Actor runtime also includes Apify startup, storage and billing.
The Actor returns a disposable-email flag, provider, syntax validity, and reason. It does not verify that a mailbox exists or that a message will be delivered.
Pricing and limits
- $0.001 per successful email check ($1 per 1,000), including Apify platform usage. Disposable addresses and duplicates count as successful checks. Invalid-email results are not charged.
- Free Apify plans: up to 10 attempted addresses per run. Paid plans support up to 10,000 addresses per run, subject to your run budget.
- Choose a maximum run charge before starting. The Actor stops at the budget or plan limit and may return partial results.
No IronDome API key is required.
Input
Provide exactly one of email or emails.
One address:
{"email":"person@example.com"}
A list:
{"emails":["person@example.com","another@gmail.com","not-an-email"]}
Lists support up to 10,000 addresses, processed through IronDome's bulk endpoint in batches of up to 100. Order and duplicates are preserved. Each address must contain 1-254 UTF-8 bytes, with no control characters. The total input limit is 3 MB. Other invalid syntax is reported as an invalid-email result.
Results
Results appear in the run's default dataset. A completed check looks like this:
{"index":0,"email":"person@example.com","provider":"custom","valid":true,"disposable":false,"reason":"not_listed"}
An invalid address produces an uncharged row:
{"index":2,"email":"not-an-email","error":{"code":"invalid_email","message":"Provide a syntactically valid email address."}}
index is the zero-based input position. valid describes syntax, not mailbox
existence or deliverability.
Budgets and partial results
The Actor stops at the run budget or the 10-address per-run free-plan allowance. It can finish successfully with partial results. The budget bounds attempted addresses: USD 0.01 allows at most ten attempts. Invalid results are not charged, but do not free up additional attempt slots.
For runs that process input, open IRONDOME-STATE in the default key-value store
(or the run's state output link). Check processed, completed, invalid, and
stoppedAtLimit before assuming the whole list was checked. A free-plan rejection
produces no dataset rows or state record; use its run status message instead.
If a service or storage failure interrupts a run, earlier results and charges
can remain. Inspect the state and charge ledger before starting another run.
Do not resurrect a failed run: automatic resume is not supported. If a charge
succeeded but dataset delivery failed, saved batch results can be recovered from
the default key-value store using the state's batchKey.
Email addresses are sent to IronDome for classification and stored in the run's input and results. Use appropriate Apify access and retention settings.