# Email Domain Auth Auditor: SPF, DKIM, DMARC, MX, BIMI (`sea_sorghum/email-domain-auth-auditor`) Actor

Bulk-check SPF, DKIM, DMARC, MX, MTA-STS, TLS-RPT and BIMI for any list of domains. Get a 0-100 score, an A-F grade and plain-English fixes.

- **URL**: https://apify.com/sea_sorghum/email-domain-auth-auditor.md
- **Developed by:** [Bader Aloqily](https://apify.com/sea_sorghum) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.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 Domain Auth Auditor – SPF, DKIM, DMARC, MX & BIMI Bulk Checker

Check **SPF, DKIM, DMARC, MX, MTA-STS, TLS-RPT and BIMI** for hundreds of domains in one run. Each domain gets a **0–100 score, an A–F grade, a list of problems and plain-English fixes**. Use it as a bulk **DMARC checker**, **SPF lookup-limit checker** and **email deliverability audit** for cold-email lists, agencies, MSPs and security teams.

No login, no browser, no proxy, no API key. It reads public DNS records over DNS-over-HTTPS (Cloudflare, with Google as fallback), so runs are fast and cost very little.

### What you get for every domain

- **SPF:** record, ending qualifier (`-all`, `~all`, `+all`), included services, and the real **DNS lookup count** (the 10-lookup limit that silently breaks SPF).
- **DMARC:** policy (`none`/`quarantine`/`reject`), subdomain policy, `pct`, report addresses (`rua`, `ruf`).
- **DKIM:** probes about 30 common selectors (Google, Microsoft 365, Mailchimp/Mandrill, SendGrid, Zoho, Proton, HubSpot and more). Add your own selectors if needed.
- **MX:** records plus detected mail provider (Google Workspace, Microsoft 365, Proofpoint, Mimecast, Zoho...).
- **MTA-STS, TLS-RPT, BIMI** presence.
- **Score, grade, issues (high/medium/low) and recommended fixes.**

### Use cases

- Audit a **prospect list before cold outreach** and drop domains with no authentication.
- Agency or MSP **security reports** for clients.
- Monitor your own domains on a schedule and alert on regressions (grade drops, SPF over 10 lookups).
- Enrich leads with mail provider and email-security posture.
- Find **spoofable domains** (no DMARC, `p=none`, `+all`).

### Input

| Field | Description | Default |
| --- | --- | --- |
| `domains` | Domains, URLs or email addresses (domain is extracted) | required |
| `checkDkim` | Probe common DKIM selectors | true |
| `extraDkimSelectors` | Your own selectors | none |
| `checkMtaSts` | Look for MTA-STS | true |
| `maxDomains` | Cap per run (also caps cost) | 1000 |
| `concurrency` | Parallel domains | 10 |

```json
{ "domains": ["example.com", "ceo@yourclient.com", "https://www.acme.io"], "extraDkimSelectors": ["mail2026"] }
```

### Output (one item per domain)

```json
{
  "domain": "cloudflare.com",
  "score": 100,
  "grade": "A",
  "hasMx": true,
  "mxProvider": "Other / self-hosted",
  "spf": { "found": true, "allQualifier": "-", "dnsLookups": 7, "includes": ["..."] },
  "dmarc": { "found": true, "policy": "reject", "pct": 100, "rua": ["mailto:..."] },
  "dkim": { "checked": true, "selectorsFound": ["k1", "s1"] },
  "mtaSts": true, "tlsRpt": true, "bimi": false,
  "issues": [], "recommendations": []
}
```

Download as JSON, CSV or Excel, or call it through the Apify API.

### Pricing

Pay per event: you are charged per **domain audited** (one default dataset-item "result" event each), plus a tiny start fee. Domains that fail to process are listed in the ERRORS record and not charged.

### Good to know

- **DKIM selectors cannot be listed by design.** A miss on the common selectors does not prove DKIM is off; add your provider's selector in `extraDkimSelectors`. Some large senders (for example Google) use date-based selectors.
- The audit is passive: it only queries public DNS and never contacts the domain's mail servers.
- Scores are guidance based on widely used best practice, not a compliance certificate.

### FAQ

**Is this legal?** Yes. It only reads public DNS records that every mail server queries.
**Does it send email?** No.
**How many domains can I check?** Up to 10,000 per run.

# Actor input Schema

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

Domains to audit. You can also paste email addresses or URLs; the domain is extracted automatically.

## `checkDkim` (type: `boolean`):

Look for DKIM public keys on ~30 common selectors (google, selector1, k1, s1, default...). DKIM selectors are not discoverable by design, so a miss does not prove DKIM is off.

## `extraDkimSelectors` (type: `array`):

Add custom selectors your provider uses (for example 'mail2026').

## `checkMtaSts` (type: `boolean`):

Look for the \_mta-sts TXT record.

## `maxDomains` (type: `integer`):

Upper bound on domains audited per run. This also caps your cost.

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

Domains audited in parallel.

## Actor input object example

```json
{
  "domains": [
    "google.com",
    "github.com",
    "example.com"
  ],
  "checkDkim": true,
  "extraDkimSelectors": [],
  "checkMtaSts": true,
  "maxDomains": 1000,
  "concurrency": 10
}
```

# Actor output Schema

## `results` (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 = {
    "domains": [
        "google.com",
        "github.com",
        "example.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("sea_sorghum/email-domain-auth-auditor").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",
        "example.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("sea_sorghum/email-domain-auth-auditor").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",
    "example.com"
  ]
}' |
apify call sea_sorghum/email-domain-auth-auditor --silent --output-dataset

```

## MCP server setup

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

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/dDGn1dQhNMdEZdv7g/builds/9A1oPD8a36lRvLc3e/openapi.json