# Bulk Email Domain Validator (`gifted_wagon/bulk-email-domain-validator`) Actor

Validate email syntax and mail domains with MX evidence, disposable-domain and role-address flags, transparent risk labels, and no SMTP messages.

- **URL**: https://apify.com/gifted\_wagon/bulk-email-domain-validator.md
- **Developed by:** [Michael Olmos](https://apify.com/gifted_wagon) (community)
- **Categories:** Lead generation, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.42 / 1,000 email validateds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Bulk Email Domain Validator

Validate email syntax and mail-domain configuration with transparent evidence. The Actor normalizes addresses, checks MX and fallback address DNS, and flags known disposable domains and role-based local parts.

### What the result means

- `valid`: syntax is valid and MX records are present without configured risk flags.
- `risky`: syntax is valid but a disposable, role-based, or address-only delivery signal applies.
- `invalid`: syntax is invalid or the domain has no observed mail/address DNS.
- `unknown`: DNS returned a temporary error or timeout.

This is deliberately honest: it does **not** send SMTP messages and does not claim mailbox existence, inbox placement, or catch-all status.

Provide inline `emails` or an Apify `datasetId` plus `emailField`. Duplicate values are validated once.

### Quick start

```json
{
  "emails": [
    "hello@apify.com",
    "support@example.invalid",
    "not-an-email"
  ],
  "checkMx": true,
  "flagDisposable": true,
  "flagRoleBased": true,
  "maxEmails": 500
}
```

For an existing Apify dataset, set `datasetId` and `emailField` instead of copying addresses into the input. `maxEmails` is a hard batch limit, while `concurrency` lets you tune DNS throughput.

### Output

Each unique address produces one dataset row with its normalized address and domain, syntax status, MX/address DNS evidence, disposable and role-based flags, final status, risk labels, and an explicit error when DNS is temporarily unavailable. The `OUTPUT` key-value-store record summarizes valid, risky, invalid, unknown, duplicate, and budget-limited counts.

Common workflows include cleaning CRM imports, checking consented outreach lists, validating account-registration data, and adding a deterministic email-quality step to n8n or Make.

### API and automation

```bash
curl -X POST \
  "https://api.apify.com/v2/acts/gifted_wagon~bulk-email-domain-validator/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"emails":["hello@apify.com"],"checkMx":true}'
```

Save a tested input as an Apify task for repeat jobs. In n8n or Make, send JSON to the same endpoint and route `valid`, `risky`, `invalid`, and `unknown` rows separately.

### Pricing

The primary `email-validated` event starts at **$0.0006 per unique completed validation**. The `OUTPUT` summary is uncharged. A small Actor-start event covers startup.

### Responsible use

Use results for legitimate data quality and consented communications. Validation is not permission to send email; comply with applicable privacy, marketing, and anti-spam laws.

### FAQ and limitations

- **Does `valid` prove the mailbox exists?** No. It confirms syntax and observable mail-domain configuration only.
- **Does the Actor send email or probe SMTP servers?** No.
- **Why can a result be `unknown`?** DNS services can time out or return temporary errors; retry those rows later.
- **Are duplicate addresses charged twice?** No. Normalized duplicates are processed once.

# Actor input Schema

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

Inline email strings. Duplicate normalized inputs are checked once.

## `datasetId` (type: `string`):

Optional Apify dataset containing an email field.

## `emailField` (type: `string`):

Top-level dataset field containing the email string.

## `maxEmails` (type: `integer`):

Hard cap across inline and dataset values.

## `checkMx` (type: `boolean`):

Resolve MX records and use address DNS only as a transparent fallback signal.

## `flagDisposable` (type: `boolean`):

Mark addresses on the Actor's maintained disposable-domain list as risky.

## `flagRoleBased` (type: `boolean`):

Mark common role local parts such as support, sales, and admin as risky.

## `concurrency` (type: `integer`):

Bounded DNS worker count for throughput control.

## Actor input object example

```json
{
  "emails": [
    "hello@apify.com",
    "support@example.invalid",
    "not-an-email"
  ],
  "emailField": "email",
  "maxEmails": 5000,
  "checkMx": true,
  "flagDisposable": true,
  "flagRoleBased": true,
  "concurrency": 25
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `summary` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("gifted_wagon/bulk-email-domain-validator").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("gifted_wagon/bulk-email-domain-validator").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 '{}' |
apify call gifted_wagon/bulk-email-domain-validator --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,gifted_wagon/bulk-email-domain-validator"
        }
    }
}

```

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/DssPqYt6qWDPTaB3r/builds/OK6MFPyeDfs6esSTr/openapi.json