# Email Validator & Domain Email Health (MX, SPF, DMARC, DKIM) (`calcio_you/email-domain-check`) Actor

Validate email addresses without sending mail (syntax, MX, disposable, free webmail, role account) and audit a domain's email authentication (SPF, DMARC, DKIM, MTA-STS, BIMI) with an A-F grade. Built for AI agents and lead cleaning. Pay per check.

- **URL**: https://apify.com/calcio_you/email-domain-check.md
- **Developed by:** [Novarithm](https://apify.com/calcio_you) (community)
- **Categories:** Lead generation, AI, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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

## Email Validator & Domain Email Health (MX, SPF, DMARC, DKIM)

Two tools in one Actor, for **AI agents**, lead-list cleaning, signup forms and email deliverability audits:

1. **Email check**: is this address worth sending to? Syntax, domain existence, MX / null MX / A-record fallback, **disposable domain** (open list of 4,000+ throwaway domains), free webmail, **role account** (info@, sales@...), SPF and DMARC presence. Verdict `deliverable` / `risky` / `undeliverable` / `invalid`, a 0-100 score and the reasons.
2. **Domain email health**: full email-authentication audit of a domain: MX and mail provider, **SPF** (all mechanism, DNS lookups), **DMARC** policy and reporting, **DKIM** on 20 common selectors (wildcard-aware), **MTA-STS**, **TLS-RPT**, **BIMI**, domain registration date (RDAP). Grade **A to F** with concrete fixes.

**No email is ever sent and no SMTP probe is made**: only public DNS and RDAP lookups. Safe for your IPs and your sender reputation.

### Use cases

- An AI SDR agent cleans a lead list before an outreach sequence (drop disposable, invalid and dead domains).
- A signup form blocks throwaway addresses.
- An agency audits a prospect's SPF/DMARC/DKIM setup and sends them the fixes.
- A CRM enrichment step tags role accounts and free webmail addresses.

### Input

| Field | What it does |
|---|---|
| `emails` | List of email addresses to validate. |
| `domains` | List of domains (or URLs) to audit. |
| `queries` | Advanced: `[{"endpoint": "email_check", "params": {"email": "..."}}, {"endpoint": "domain_email_health", "params": {"domain": "..."}}]` |
| `maxQueries` | Safety cap on checks per run (default 1000). |

Example:

```json
{
  "emails": ["sales@stripe.com", "test@mailinator.com"],
  "domains": ["bbc.co.uk"]
}
```

### Output

One dataset item per check. Shortened examples from a real run:

```json
{
  "endpoint": "email_check",
  "input": {"email": "sales@stripe.com"},
  "ok": true,
  "result": {
    "verdict": "deliverable",
    "score": 85,
    "reasons": ["role_account"],
    "disposable": false,
    "free_provider": false,
    "role_account": true,
    "mx_found": true,
    "spf": true,
    "mailbox_verified": false,
    "note": "No SMTP probe is performed: the domain can receive mail, the individual mailbox is not verified."
  },
  "charged_event": "email-check",
  "price_usd": 0.003
}
```

- `test@mailinator.com` → `"verdict": "risky"`, reason `disposable_domain`.
- `bbc.co.uk` (domain audit) → grade **B**, DMARC policy `reject`, with the list of recommendations.

### Pricing (pay per event)

| Event | Price |
|---|---|
| Email address checked | $0.003 |
| Domain audited | $0.01 |

No start fee. **Not charged**: addresses with invalid syntax, domain audits of domains that do not exist, invalid input, DNS/source outages and internal errors (the item says `"ok": false` or `"verdict": "invalid"` and why).

### Honest limits

- **No mailbox verification**: we know whether the domain accepts mail, not whether the exact mailbox exists, and catch-all domains are not detected. This is deliberate (no SMTP probing).
- DKIM is tested on 20 common selectors: a custom selector can exist without being seen.
- RDAP registration data is unavailable for some country domains (e.g. .sn, .ci): the domain age is then `null`.
- Disposable-domain detection relies on an open community list (CC0); brand-new throwaway domains may not be on it yet.

### Data sources

- Public DNS (MX, TXT, A records), queried live
- RDAP (RFC 9083) for domain registration data
- [disposable-email-domains](https://github.com/disposable-email-domains/disposable-email-domains), CC0 1.0

Made by Novarithm, AI agents and automation. Contact: contact@novarithm.com

***

Want this whole store under your brand? → https://gogeta2-u35175.vm.elestio.app/agents/clones/en/cases/api-store-for-ai-agents/

# Actor input Schema

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

One charged check per syntax-valid address. No email is sent and no SMTP probe is made.

## `domains` (type: `array`):

Domains (or URLs) for a full email-authentication audit with grade A-F.

## `queries` (type: `array`):

e.g. \[{"endpoint": "email_check", "params": {"email": "a@b.com"}}, {"endpoint": "domain_email_health", "params": {"domain": "b.com"}}]

## `maxQueries` (type: `integer`):

Safety cap: only the first N checks of the input are processed.

## Actor input object example

```json
{
  "emails": [
    "sales@stripe.com",
    "test@mailinator.com"
  ],
  "domains": [
    "bbc.co.uk"
  ],
  "maxQueries": 1000
}
```

# Actor output Schema

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

All result items in the default dataset (JSON).

# 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 = {
    "emails": [
        "sales@stripe.com",
        "test@mailinator.com"
    ],
    "domains": [
        "bbc.co.uk"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("calcio_you/email-domain-check").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 = {
    "emails": [
        "sales@stripe.com",
        "test@mailinator.com",
    ],
    "domains": ["bbc.co.uk"],
}

# Run the Actor and wait for it to finish
run = client.actor("calcio_you/email-domain-check").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 '{
  "emails": [
    "sales@stripe.com",
    "test@mailinator.com"
  ],
  "domains": [
    "bbc.co.uk"
  ]
}' |
apify call calcio_you/email-domain-check --silent --output-dataset

```

## MCP server setup

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

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/SgH0gfeCEziJba2g1/builds/5RfuLf8pZtwcKVLXd/openapi.json