# Email Deliverability & Domain Audit - SPF, DKIM, DMARC, MX (`siteprobe/domain-email-audit`) Actor

Bulk-audit domains: email provider (Google Workspace, Microsoft 365...), SPF, DKIM, DMARC policy, MX, DNS host, SSL expiry, security headers and SaaS tools revealed by DNS. Deliverability score per domain.

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

## Pricing

$4.00 / 1,000 domain auditeds

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 & Domain Audit – SPF, DKIM, DMARC, MX

Audit **thousands of domains at once**: which **email provider** they use (Google Workspace, Microsoft 365, Zoho, Proofpoint…), whether **SPF, DKIM and DMARC** are set up correctly, where their **DNS is hosted**, when their **SSL certificate expires**, and which **SaaS tools** their DNS records reveal (HubSpot, Salesforce, Atlassian, Stripe, DocuSign, Zoom, OpenAI…).

### Who it's for

- **Cold email and outbound teams:** segment prospects by email provider (Google vs Outlook), check your own sending domains, and avoid bounces.
- **Agencies and MSPs:** find prospects with missing DMARC or weak SPF and offer them a fix.
- **Sales intelligence:** detect which SaaS vendors a company uses from its DNS verification records.
- **Security and IT:** monitor SSL expiry and security headers across a portfolio of domains.

### What you get for each domain

- **Email provider** detected from MX records, plus the full MX list.
- **SPF:** the record, its policy (`-all`, `~all`, …) and the email services it includes (SendGrid, Mailchimp, HubSpot, Amazon SES, Klaviyo…).
- **DMARC:** the record, policy (`none`, `quarantine` or `reject`), `pct` and `rua`.
- **DKIM:** keys found on 18 common selectors (google, selector1/2, k1, s1…).
- **MTA-STS, TLS-RPT, BIMI and CAA** records.
- **DNS host:** Cloudflare, Route 53, GoDaddy, OVHcloud, and others.
- **SaaS detected from DNS**, using 50+ verification patterns.
- **Email security score** (0–100) with a plain-English list of issues.
- **Optional:** SSL issuer and days until expiry, TLS version, HTTPS redirect, and security headers (HSTS, CSP, X-Frame-Options…).

### Example output

```json
{
  "domain": "stripe.com",
  "emailProvider": "Google Workspace",
  "dnsProvider": "Amazon Route 53",
  "spf": {"allMechanism": "softfail", "includedSenders": []},
  "dmarc": {"policy": "reject", "pct": "100"},
  "dkimSelectorsFound": ["google", "s1", "s2", "mandrill"],
  "saasDetectedFromDns": ["Atlassian", "DocuSign", "Linear", "OpenAI", "Stripe", "Vercel"],
  "emailSecurityScore": 100,
  "issues": [],
  "charged": true
}
```

### Pricing

- **$0.004 per audited domain** ($4 per 1,000). No subscription.
- **Domains with no DNS records are free.**
- Set a maximum cost per run and the Actor stops cleanly when it is reached.

### Notes

- DNS is queried over encrypted DNS-over-HTTPS resolvers, with automatic failover.
- DKIM can only be checked on known selectors. A domain that uses a custom selector may show "no DKIM found" even though DKIM is configured.
- Only public DNS and website metadata is collected. No personal data is extracted.

### Support

Open an issue in the **Issues** tab with a domain and the expected result. Fixes are shipped quickly.

# Actor input Schema

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

Domains to audit (example.com). URLs and emails' domains also work: the host name is extracted.

## `checkWebsite` (type: `boolean`):

Adds SSL certificate validity/expiry, HTTPS redirect and HTTP security headers. Disable for pure DNS/email audits (faster).

## `maxConcurrency` (type: `integer`):

How many domains are processed in parallel.

## Actor input object example

```json
{
  "domains": [
    "stripe.com",
    "lemonde.fr",
    "gymshark.com"
  ],
  "checkWebsite": true,
  "maxConcurrency": 20
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

## `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": [
        "stripe.com",
        "lemonde.fr",
        "gymshark.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("siteprobe/domain-email-audit").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": [
        "stripe.com",
        "lemonde.fr",
        "gymshark.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("siteprobe/domain-email-audit").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": [
    "stripe.com",
    "lemonde.fr",
    "gymshark.com"
  ]
}' |
apify call siteprobe/domain-email-audit --silent --output-dataset

```

## MCP server setup

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

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/qPRAQOOAQzRVDhEON/builds/6MsNpOAHMgTxfMHsn/openapi.json