# Bulk Email Deliverability Checker (MX/SPF/DMARC/DKIM) (`weiseer/email-deliverability-checker`) Actor

Bulk-check domains for email setup & authentication over DNS: MX + provider, SPF, DMARC policy, DKIM selectors, with a deliverability score. One JSON row per domain.

- **URL**: https://apify.com/weiseer/email-deliverability-checker.md
- **Developed by:** [wei seer](https://apify.com/weiseer) (community)
- **Categories:** Developer tools, Lead generation, SEO tools
- **Features:** Limited permissions
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$10.00 / 1,000 results

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 Deliverability & DNS Auth Checker — Bulk MX / SPF / DMARC / DKIM

Check a whole list of domains for email setup and authentication in one run —
entirely over DNS, so it's fast, never blocked, and low-maintenance. One JSON row
per domain with a deliverability score and verdict.

Great for **email-list hygiene**, **deliverability audits**, **lead-list scoring**,
and **security posture checks** across many domains at once.

### What you get per domain

| Check | Fields |
|---|---|
| **MX** | `has_mx`, `mx_hosts`, `mx_provider` (Google Workspace / Microsoft 365 / Zoho / SES / Tencent / Alibaba / …) |
| **SPF** | `spf_found`, `spf_record`, `spf_qualifier` (`-all` / `~all` / `?all`) |
| **DMARC** | `dmarc_found`, `dmarc_policy` (`none` / `quarantine` / `reject`) |
| **DKIM** | `dkim_selectors_found` (which common selectors publish a key) |
| **Verdict** | `auth_score` (x/5), `verdict` (strong / partial / weak), `looks_disposable` |

### Input

```json
{ "domains": ["stripe.com", "user@acme.com", "https://globex.com"], "dkimSelectors": ["google", "default", "selector1", "k1"] }
```

Email addresses and URLs are reduced to the domain. Leave `domains` empty to run
the built-in sample.

### Output (one item per domain)

```json
{
  "domain": "github.com",
  "has_mx": true,
  "mx_provider": "Google Workspace",
  "spf_found": true, "spf_qualifier": "~all",
  "dmarc_found": true, "dmarc_policy": "reject",
  "dkim_selectors_found": ["google"],
  "auth_score": "5/5", "verdict": "strong",
  "looks_disposable": false
}
```

Export as JSON/CSV/Excel or pull via the Apify API.

### Why DNS-only

It reads MX, SPF/TXT, `_dmarc`, and `<selector>._domainkey` records — no SMTP
probing (which mail servers block) and no scraping. That makes results stable and
the Actor low-maintenance. Note: it verifies a domain's *email authentication
setup*, not whether a specific mailbox exists.

### Pricing

Pay per result: **$0.01 per domain checked**. No rental, no subscription.

### Pairs with

- [Domain Intelligence](https://apify.com/weiseer/domain-intel-scraper) — DNS/WHOIS/SSL
- [Website Metadata & Tech Profiler](https://apify.com/weiseer/website-metadata-tech-profiler) — HTTP metadata + tech + security headers

***

Apache-2.0 · by [weiseer](https://github.com/weiseer)

# Actor input Schema

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

Domains to check (e.g. example.com). Email addresses and URLs are accepted and reduced to the domain.

## `dkimSelectors` (type: `array`):

Selectors to test at <selector>.\_domainkey.<domain>. Defaults to common ones (google, default, selector1, k1, …).

## `resolvers` (type: `array`):

Public DNS resolver IPs. Defaults to Cloudflare + Google for deterministic results.

## Actor input object example

```json
{
  "domains": [
    "google.com",
    "github.com"
  ],
  "dkimSelectors": [
    "google",
    "default",
    "selector1",
    "k1"
  ],
  "resolvers": [
    "1.1.1.1",
    "8.8.8.8"
  ]
}
```

# 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 = {
    "domains": [
        "google.com",
        "github.com"
    ],
    "dkimSelectors": [
        "google",
        "default",
        "selector1",
        "k1"
    ],
    "resolvers": [
        "1.1.1.1",
        "8.8.8.8"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("weiseer/email-deliverability-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 = {
    "domains": [
        "google.com",
        "github.com",
    ],
    "dkimSelectors": [
        "google",
        "default",
        "selector1",
        "k1",
    ],
    "resolvers": [
        "1.1.1.1",
        "8.8.8.8",
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("weiseer/email-deliverability-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 '{
  "domains": [
    "google.com",
    "github.com"
  ],
  "dkimSelectors": [
    "google",
    "default",
    "selector1",
    "k1"
  ],
  "resolvers": [
    "1.1.1.1",
    "8.8.8.8"
  ]
}' |
apify call weiseer/email-deliverability-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,weiseer/email-deliverability-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/TeTWu4ppGBqOR8PCG/builds/HFuECHTUrwILyUDdT/openapi.json