# SPF, DMARC & DKIM Checker (Bulk Domains) (`proper_ecosystem_cie/dns-email-auth-checker`) Actor

Audit email authentication for many domains: SPF, DMARC, DKIM, MX, MTA-STS and BIMI records, with an A-F grade and plain-English fixes.

- **URL**: https://apify.com/proper_ecosystem_cie/dns-email-auth-checker.md
- **Developed by:** [Proper Ecosystem Tools](https://apify.com/proper_ecosystem_cie) (community)
- **Categories:** Developer tools, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$3.00 / 1,000 domain checkeds

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

## SPF, DMARC & DKIM Checker (Bulk Email Authentication Audit)

Check email authentication for hundreds of domains at once. For each domain you get the **SPF**, **DMARC**, **DKIM**, **MX**, **MTA-STS**, and **BIMI** records, a simple **A to F grade**, and a plain-English list of what to fix. Useful since Google and Yahoo's bulk-sender rules require SPF, DKIM, and DMARC.

### What it checks

- **SPF**: present, single record, `all` qualifier (`-all`, `~all`, `?all`, `+all`), top-level DNS-lookup count vs. the 10-lookup limit
- **DMARC**: policy (`none` / `quarantine` / `reject`), subdomain policy, `pct`, aggregate report address (`rua`)
- **DKIM**: probes about 17 common selectors (google, selector1, selector2 for Microsoft 365, k1 for Mailchimp, s1/s2, and more) plus any you add
- **MX**, **nameservers**, **MTA-STS**, and **BIMI** records

All lookups go through public DNS-over-HTTPS resolvers. Only public DNS data is read; nothing is sent to the domain.

### Input

| Field | Description |
|---|---|
| `domains` | Domains or URLs, one per line |
| `dkimSelectors` | Extra DKIM selectors to probe (optional) |
| `concurrency` | Domains in parallel (default 10) |

### Output (illustrative example, one item per domain)

```json
{"domain": "example.com", "grade": "B", "score": 85,
 "issues": ["DMARC p=none only monitors; move to quarantine or reject"],
 "spf": {"present": true, "record": "v=spf1 include:_spf.google.com ~all", "allQualifier": "~all", "lookupTerms": 1},
 "dmarc": {"present": true, "policy": "none", "rua": "mailto:dmarc@example.com"},
 "dkim": {"selectorsFound": ["google"]}, "mxRecords": ["1 smtp.google.com"]}
```

### Pricing

Pay per domain checked. Lookups that fail on a temporary DNS error come back free with an `error` field.

### Use cases

Deliverability audits for agencies, lead qualification (domains with no DMARC are prospects for email security services), vendor security questionnaires, and monitoring your own domains on a schedule.

# Actor input Schema

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

Domains or URLs, one per line.

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

Selectors to check besides the common built-in list (google, selector1, selector2, k1, s1 ...).

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

Domains checked in parallel.

## `maxItems` (type: `integer`):

Stop after this many unique domains.

## Actor input object example

```json
{
  "domains": [
    "apify.com",
    "example.com"
  ],
  "dkimSelectors": [],
  "concurrency": 10,
  "maxItems": 50000
}
```

# Actor output Schema

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

Dataset with one row per input item

## `runStats` (type: `string`):

Summary counts for the run

# 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": [
        "apify.com",
        "example.com"
    ],
    "dkimSelectors": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("proper_ecosystem_cie/dns-email-auth-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": [
        "apify.com",
        "example.com",
    ],
    "dkimSelectors": [],
}

# Run the Actor and wait for it to finish
run = client.actor("proper_ecosystem_cie/dns-email-auth-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": [
    "apify.com",
    "example.com"
  ],
  "dkimSelectors": []
}' |
apify call proper_ecosystem_cie/dns-email-auth-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,proper_ecosystem_cie/dns-email-auth-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/RwcX2HsUUgzevN81L/builds/KYdFv72pnrEGBHVIR/openapi.json