Bulk Email Deliverability Auditor - SPF, DKIM, DMARC

Audit the DNS records that decide whether your email lands, across thousands of domains at once — with a graded score and a plain-English list of what is broken.

Everything here is a DNS lookup: no HTTP, no browser, no API key. That is why a full four-record audit costs a fraction of a cent per domain.

What you get

{
  "domain": "stripe.com",
  "grade": "A",
  "deliverabilityScore": 100,
  "acceptsEmail": true,
  "mxProvider": "Google Workspace",
  "hasSpf": true,
  "spfPolicy": "fail",
  "hasDmarc": true,
  "dmarcPolicy": "reject",
  "hasDkim": true,
  "issues": [],
  "spf": { "includes": ["_spf.google.com"], "dnsLookupCount": 4, "exceedsLookupLimit": false },
  "dmarc": { "policy": "reject", "percentage": 100, "rua": "mailto:dmarc@stripe.com" },
  "dkimSelectorsFound": ["google"]
}

Main use cases

• Lead-list hygiene. Drop domains with no MX before you send — they cannot receive mail at all.
• Cold outreach QA. Check your own sending domains before a campaign.
• Security and M&A due diligence. A domain with no DMARC is trivially spoofable.
• Agency audits. Grade a whole client portfolio in one run and export the problems as CSV.
• Monitoring. Schedule it to catch the day someone edits an SPF record and breaks sending.

What it actually checks

Record	Why it matters
MX	Whether the domain can receive mail at all, plus which provider runs it
SPF	Which servers may send as the domain. Flags +all (anyone may send) and the 10-lookup limit, past which receivers return permerror and SPF silently stops working
DMARC	What receivers should do on failure. Flags p=none (monitoring only), partial pct=, and a missing rua reporting address
DKIM	Signing keys, probed across the selectors Google, Microsoft, Zoho, Proton, Mailchimp and others use

The SPF 10-lookup check is the one most tools miss — a record can look perfect and still fail in production because it needs 11 lookups.

Pricing

Event	Price	When
Domain audited	$0.0015	One domain with all four record types checked

Not charged for: unparseable input, or domains where every DNS lookup failed.

1,000 domains = $1.50.

Input

Field	Type	Default	Notes
domains	array	required	Domain, URL or email address — all accepted. Up to 5,000.
dkimSelectors	array	14 common ones	DNS cannot enumerate selectors, so we probe known ones. Add yours if you know them.
concurrency	integer	8	Parallel lookups.

Limitations

• DKIM detection is best-effort. DNS provides no way to list a domain's selectors, so a domain using a custom selector will show hasDkim: false even though DKIM works. Supply your selector to confirm.
• This audits configuration, not reputation. It does not check blocklists, IP reputation or inbox placement, and cannot promise your mail reaches the inbox.
• Records are read live from public resolvers (1.1.1.1, 8.8.8.8); very recent DNS edits may still be cached upstream.

Related Actors

• Website Brand & Favicon Extractor — enrich the same domain list with brand assets.
• SSL Certificate & Security Header Audit — the TLS half of the same due-diligence job.

Reliability

• Retries on 429 and 5xx with exponential backoff; permanent 4xx errors are not retried.
• Bad input is reported and skipped, never charged.
• One failing target never aborts the rest of the run.
• Concurrency is bounded and configurable — this work is network-bound, so parallel requests, not memory, are what control speed.

Data source and responsible use

Reads only publicly available data. No authentication bypass, no CAPTCHA circumvention, no browser automation.

Not affiliated with any of the services checked.

How to use Bulk Email Deliverability Auditor

1. Open Bulk Email Deliverability Auditor on Apify Store and click Try for free.
2. Fill in the input (the form is prefilled with a working example) and click Start.
3. Watch results appear in the Output tab, then download them as JSON, CSV, Excel or HTML, or read them through the API.
4. Optional: save the input as a task and add a schedule to run it automatically, or connect it to your tools with integrations and webhooks.

Output example

Each result is one dataset item. A real item from a test run (long fields shortened):

{
  "domain": "github.com",
  "grade": "A",
  "deliverabilityScore": 100,
  "acceptsEmail": true,
  "mxProvider": "Microsoft 365",
  "hasSpf": true,
  "spfPolicy": "softfail",
  "hasDmarc": true,
  "dmarcPolicy": "quarantine",
  "hasDkim": true,
  "issues": [],
  "mxRecords": [
    {
      "exchange": "github-com.mail.protection.outlook.com",
      "priority": 0
    }
  ]
}

Use Bulk Email Deliverability Auditor with AI agents (MCP)

Give Claude, ChatGPT, Cursor, VS Code or any MCP client this Actor as a tool through the hosted Apify MCP server. The agent sees the input fields with descriptions and example values, runs the Actor, and reads the results.

MCP server URL (this Actor only):

https://mcp.apify.com/?tools=technicaldost/bulk-email-deliverability-auditor

Claude Code:

$claude mcp add --transport http apify "https://mcp.apify.com/?tools=technicaldost/bulk-email-deliverability-auditor" --header "Authorization: Bearer YOUR_APIFY_TOKEN"

Cursor, VS Code, Claude Desktop and other clients (mcp.json or the client's MCP settings):

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com/?tools=technicaldost/bulk-email-deliverability-auditor",
      "headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" }
    }
  }
}

Clients that support sign-in (such as Claude.ai connectors) can use the URL without a token and log in to Apify instead. Get your token in Apify Console → Settings → API & Integrations, or generate a ready config for your client at mcp.apify.com. In the agent the tool is named technicaldost--bulk-email-deliverability-auditor; ask it, for example, to "run Bulk Email Deliverability Auditor with {"domains": ["google.com", "github.com"]}".

AI agents without an Apify account can also run and pay for this Actor per request with x402 agentic payments.

Run Bulk Email Deliverability Auditor via API

Run the Actor and get its results in one call (replace YOUR_APIFY_TOKEN):

curl -X POST "https://api.apify.com/v2/acts/technicaldost~bulk-email-deliverability-auditor/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"domains": ["google.com", "github.com"]}'

Python (pip install apify-client):

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("technicaldost/bulk-email-deliverability-auditor").call(run_input={"domains": ["google.com", "github.com"]})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

JavaScript / TypeScript (npm install apify-client):

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'YOUR_APIFY_TOKEN' });
const run = await client.actor('technicaldost/bulk-email-deliverability-auditor').call({"domains": ["google.com", "github.com"]});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Long runs: start them with POST /v2/acts/technicaldost~bulk-email-deliverability-auditor/runs and fetch the dataset when the run finishes, or receive a webhook.

Integrations

Bulk Email Deliverability Auditor works with Make, Zapier, n8n, LangChain, Google Sheets, Slack, GitHub and webhooks. Schedule runs in Apify Console and send new results straight to your apps, spreadsheets or AI pipelines.

FAQ

Can I use Bulk Email Deliverability Auditor with AI agents like Claude or ChatGPT?

Yes. Connect the Apify MCP server with ?tools=technicaldost/bulk-email-deliverability-auditor (see above) and the agent can run the Actor and read its results on its own.

Can I call Bulk Email Deliverability Auditor from my own code?

Yes. Use the REST API, or the official Python and JavaScript clients shown above. Results are available as JSON, CSV, Excel, XML or HTML.

How do I run it on a schedule?

Save your input as a task in Apify Console and add a schedule (for example, daily). Use webhooks or integrations to send each run's results onward.

Is it legal to use this Actor?

It works with publicly available data. Make sure your use complies with the source website's terms and with data protection laws such as GDPR, especially for personal data.

Something doesn't work or I need a feature. What should I do?

Open an issue in the Issues tab on this Actor's page with an example input, and we'll look into it.