# Email Authentication & Deliverability Security Monitor (`quanmatrix/email-security-dns-auditor`) Actor

Monitor SPF, DMARC, DKIM, MX, MTA-STS, TLS-RPT and BIMI across domains, detect authentication drift, regressions and deliverability risks.

- **URL**: https://apify.com/quanmatrix/email-security-dns-auditor.md
- **Developed by:** [Rafael Barreto Haddad](https://apify.com/quanmatrix) (community)
- **Categories:** Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.94 / 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.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 Authentication & Deliverability Security Monitor

Monitor SPF, DMARC, DKIM, MX, MTA-STS, TLS-RPT and BIMI across domains, detect authentication drift, regressions and deliverability risks.

### Why use this Actor

Email security and deliverability teams need continuous detection of authentication-policy drift and regressions that can weaken anti-spoofing controls or disrupt legitimate delivery.

### Key features

- Buyer-native inputs aligned to **email authentication**.
- Predictable structured output in the default Apify Dataset.
- Pay Per Event pricing tied to measurable result rows or reports.
- Optional MCP connector delivery for downstream automation and AI agents.

### Quick start

Start with this working example and replace the target values with your own:

```json
{
  "domains": [
    "example.com",
    "google.com"
  ]
}
```

The Actor writes structured results to the default Apify Dataset and can be used from the Store, API, schedules, Tasks, automations and MCP-compatible AI workflows.

### Input

- `domains` — Domains: Public domains to audit.
- `dkimSelectors` — DKIM selectors: Optional selectors to probe.
- `previousSnapshots` — Previous authentication snapshots: Prior snapshots keyed by domain for drift detection.
- `failRunOnRegression` — Fail on security regression: Configure Fail on security regression for this Actor run.
- `maxDomains` — Maximum domains: Configure Maximum domains for this Actor run.

All integration and advanced analysis fields are optional. The default example is intentionally runnable without configuring MCP or a previous-run baseline.

### Output

The Dataset exposes predictable machine-readable output. Representative fields include `dataset`.

### Pricing

This Actor uses Pay Per Event. The current factory base price is **$0.001200 per result event**. The Apify Store remains the source of truth for the price and plan/tier details shown to the buyer.

### Use cases

- Run the buyer-ready workflows exposed as Apify Tasks without preparing a custom integration first.
- Use the Actor from API or schedules for recurring collection, comparison or monitoring.
- Feed the structured Dataset output into spreadsheets, databases, automations or AI agents.
- Compare repeat runs when the product supports snapshots or previous-run inputs.

### Automation and AI

Use the same Actor through Apify API, schedules, public Tasks and the Apify MCP server. Outputs are structured for downstream workflows and AI agents rather than requiring manual copy/paste.

### Limitations

- Public websites and upstream APIs can change markup, access rules, rate limits or field availability without notice.
- Fields that are not publicly available are returned as unavailable or omitted rather than fabricated.
- Analytical outputs depend on the quality and coverage of the supplied or collected source data.
- Treat marketplace, reputation, workforce, safety or commercial signals as decision support and validate material decisions against the underlying source evidence.

### Detailed documentation

### Detailed documentation

### Detailed documentation

Audit public email-authentication and transport-policy DNS with repeatable posture and regression evidence.

### Why use this Actor

Email security is not one DNS record. A domain can publish SPF while leaving DMARC in monitoring mode, route mail correctly while missing transport-policy signals, or silently change authentication records during a provider migration. This Actor combines the public DNS evidence most useful to security, deliverability, domain-portfolio, and migration workflows into one normalized record per domain. It is designed for recurring monitoring as well as one-time audits.

### Key features

- Detects SPF records and flags missing or multiple SPF policies.
- Reads DMARC, classifies `p=` policy, and evaluates partial enforcement through `pct=`.
- Collects MX hosts and priorities.
- Probes caller-supplied DKIM selectors without guessing private selector names.
- Checks public MTA-STS, TLS-RPT, and BIMI TXT signals.
- Produces a deterministic posture score and explicit issue codes.
- Emits a normalized authentication snapshot and fingerprint.
- Compares prior snapshots and flags authentication regressions across runs.
- Supports fail-after-evidence behavior for automated regression gates.

### Input

Provide a `domains` array. Optional `dkimSelectors` controls which public DKIM names are probed. `previousSnapshots` enables change detection, while `failRunOnRegression` can be used in CI or monitoring pipelines. `maxDomains` limits batch size.

### Output

Each domain returns SPF presence and raw evidence, DMARC policy and percentage, MX inventory, DKIM selector matches, MTA-STS, TLS-RPT, BIMI, posture score, fingerprint, changed fields, regression state, issue codes, and an `agentAction` indicating the next operational step.

### Example

```json
{
  "domains": ["example.com", "google.com"],
  "dkimSelectors": ["default", "selector1"],
  "previousSnapshots": {},
  "failRunOnRegression": false
}
```

### Use cases

- DMARC rollout and enforcement projects.
- Deliverability operations.
- Domain portfolio monitoring.
- Mail-provider migration validation.
- Vendor and acquisition due diligence.
- MSP or agency client audits.

### Pricing

Billing is pay per audited domain result. The Actor uses public DNS directly and does not require a paid deliverability API or mailbox access.

### Limitations

DKIM requires selectors supplied by the user; absence on tested selectors does not prove a domain has no DKIM. The Actor does not send email, verify mailbox existence, test SMTP reputation, or guarantee deliverability. DNS values can temporarily differ during propagation.

### Privacy and permissions

Only public DNS is queried. No mailbox credentials, messages, contact lists, or private authentication material are accessed.

# Changelog

This Actor's version history is a separate document: https://apify.com/quanmatrix/email-security-dns-auditor/changelog.md

# Actor input Schema

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

Public domains to audit.

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

Optional selectors to probe.

## `previousSnapshots` (type: `object`):

Prior snapshots keyed by domain for drift detection.

## `failRunOnRegression` (type: `boolean`):

Configure Fail on security regression for this Actor run.

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

Configure Maximum domains for this Actor run.

## `mcpConnectors` (type: `array`):

Optional MCP connectors authorized in your Apify account. Use them to send or write this Actor result to tools such as Slack, Notion, GitHub, Sentry, Supabase, or another compatible MCP service.

## `mcpToolName` (type: `string`):

Optional exact MCP tool name. Leave blank to let the selected MCP action preset discover a compatible tool automatically.

## `mcpToolArguments` (type: `object`):

JSON object passed to the selected MCP tool. String values may use {{actor_title}}, {{result_summary}}, or {{result_json}} placeholders.

## `mcpFailOnError` (type: `boolean`):

When enabled, an MCP delivery error fails the Actor run. Disabled by default so data extraction and intelligence results remain available even if the external destination is unavailable.

## `mcpActionPreset` (type: `string`):

Choose a safe action pattern. AUTO_SAFE_WRITE discovers a compatible non-destructive write tool automatically; use a specific preset for Slack, GitHub, Notion, or database delivery.

## Actor input object example

```json
{
  "domains": [
    "example.com",
    "google.com"
  ],
  "dkimSelectors": [
    "default",
    "selector1",
    "selector2"
  ],
  "previousSnapshots": {},
  "failRunOnRegression": false,
  "maxDomains": 100,
  "mcpToolName": "",
  "mcpToolArguments": {},
  "mcpFailOnError": false,
  "mcpActionPreset": "AUTO_SAFE_WRITE"
}
```

# Actor output Schema

## `dataset` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("quanmatrix/email-security-dns-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("quanmatrix/email-security-dns-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 '{}' |
apify call quanmatrix/email-security-dns-auditor --silent --output-dataset

```

## MCP server setup

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