# Disposable Email Checker (`irondome-dev/disposable-email-checker`) Actor

Detect 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.

- **URL**: https://apify.com/irondome-dev/disposable-email-checker.md
- **Developed by:** [Irondome Dev](https://apify.com/irondome-dev) (community)
- **Stats:** 1 total users, 1 monthly users, 12.5% runs succeeded, 0 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

$1.00 / 1,000 email checks

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

Detect disposable, temporary and throwaway email addresses with single or bulk
email checks. [IronDome](https://irondome.dev) 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](https://irondome.dev/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:

```json
{"email":"person@example.com"}
```

A list:

```json
{"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:

```json
{"index":0,"email":"person@example.com","provider":"custom","valid":true,"disposable":false,"reason":"not_listed"}
```

An invalid address produces an uncharged row:

```json
{"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.

### API documentation

- [IronDome single email check](https://irondome.dev/docs/api/check)
- [IronDome bulk email check](https://irondome.dev/docs/api/bulk)

# Actor input Schema

## `emails` (type: `array`):

Check 1-10,000 addresses in batches of up to 100. Leave email unset. At most 254 UTF-8 bytes per address. Order and duplicates are preserved. Free Apify plans allow up to 10 attempted addresses per run, not per user. A finite run budget is required and may lower this limit.

## `email` (type: `string`):

Check one address. Leave emails unset. Free Apify plans allow up to 10 attempts per run; a finite run budget is required.

## Actor input object example

```json
{
  "email": "quality-check@example.com"
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `state` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "email": "quality-check@example.com"
};

// Run the Actor and wait for it to finish
const run = await client.actor("irondome-dev/disposable-email-checker").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "email": "quality-check@example.com" }

# Run the Actor and wait for it to finish
run = client.actor("irondome-dev/disposable-email-checker").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "email": "quality-check@example.com"
}' |
apify call irondome-dev/disposable-email-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,irondome-dev/disposable-email-checker"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/gda1OhhoU08fZLL8S/builds/tBYBBlEBQDzCXrXtu/openapi.json