Email Deliverability Checker

What does Email Deliverability Checker do?

Email Deliverability Checker audits any list of sending domains for inbox-readiness in a single run. It checks SPF, DMARC, DKIM and DNSSEC records, MX configuration, and domain blacklist status. Each result rolls up into an A–F deliverability grade with a 0-100 score and actionable flags. Paste bare domains or full URLs — they're auto-cleaned to the apex. Turn on monitoring to catch DMARC drift, blacklist appearances and DNS changes before they cost you the inbox. SSL, WHOIS and HTTP checks are available too for a full domain audit.

New to Apify? Sign up free and use the included $5 monthly platform credit to test this actor.

Key features

• 📧 A–F deliverability grade — SPF, DMARC, DKIM and DNSSEC parsed into pass/warn/fail verdicts and a single inbox-readiness grade, the signal cold-email, RevOps and ESP teams actually need before a send.
• 🛡️ SPF / DMARC / DKIM / DNSSEC verdicts — policy qualifiers (-all/~all), DMARC policy (none/quarantine/reject) + pct + rua, DKIM selector discovery, and DNSSEC presence — the exact misconfigurations that land mail in spam.
• 📮 MX + mail configuration — verifies the domain can actually send and receive mail, with the full MX record set.
• 🚫 Domain blacklist check — checks each domain's resolved IP and name against major DNSBLs so you catch reputation damage early.
• ♻️ Deliverability monitoring — incremental mode flags NEW / UPDATED domains and detects DMARC drift, blacklist appearances and DNS changes since the previous run.
• 🌐 Full audit option — enable SSL/TLS, WHOIS and HTTP checks for complete DNS, certificate and registration data alongside the email signals.
• 🔔 Notifications — push new findings to Telegram, Discord, Slack, WhatsApp or a generic webhook (n8n / Make / Zapier).
• 📦 Compact + MCP output — a compact at-a-glance mode and MCP-connector export for AI-agent and automation workflows.

What data can you get for each domain?

Each result includes Core domain fields (domain, inputUrl, securityScore, flags, dns, whois, ssl, and http, and more) and contact information (emailGrade and emailAuth). In standard mode, all fields are always present — unavailable data points are returned as null, never omitted. In compact mode, only core fields are returned.

Input

Configure the actor through the input schema in Apify Console.

Key parameters:

• domains — Domains or full URLs to inspect — one per line, or paste a JSON array. Full URLs are auto-cleaned to the apex domain (https://www.example.com/path → example.com).
• checks — Which inspections to run per domain. Defaults to the email-deliverability set (DNS/MX, SPF/DMARC/DKIM, blacklist); enable SSL/WHOIS/HTTP too for a full audit. (default: ["dns","emailAuth","blacklist"])
• recordTypes — Which DNS record types to resolve when the DNS check is enabled. (default: ["A","AAAA","MX","TXT","CNAME","NS","SOA","CAA"])
• dkimSelectors — DKIM cannot be enumerated, so common selectors (default, google, selector1/2, k1…) are probed automatically. Add your ESP's selector here to catch custom setups. (default: [])
• compact — At-a-glance verdict only (domain, security score, email grade, flags) — drops the raw record blocks. Ideal for AI-agent / MCP workflows. (default: false)
• excludeEmptyFields — Drop null, empty-string, and empty-array fields from each record before push. Smaller payloads for AI agents and dashboards. (default: false)
• incrementalMode — Compare each domain against the previous run and flag changes (NEW / UPDATED / UNCHANGED). Detects cert renewals, WHOIS expiry, DNS changes, email-auth drift and blacklist appearances over time. stateKey is optional — defaults to a stable key derived from the domain list + checks. (default: false)
• stateKey — Optional. Stable identifier for the monitored domain set. Leave empty to auto-generate from the domain list + checks.
• emitUnchanged — When monitoring, also output domains whose signals did not change since the last run. Off = only NEW and UPDATED domains are emitted. (default: false)
• telegramToken — Telegram bot token (from @BotFather). Required for Telegram notifications.
• telegramChatId — Telegram chat or channel ID (e.g. "-100123456789"). Required when telegramToken is set.
• ...and 12 more parameters

Input examples

Basic search — Pick one or more checks from the supported taxonomy.

→ Full payload per result — all standard fields populated where the source provides them.

{
  "checks": [
    "dns"
  ]
}

Incremental tracking — Only emit domains that changed since the previous run with this stateKey.

→ First run builds the baseline state. Subsequent runs emit only records that are new or whose tracked content changed. Set emitUnchanged: true to include unchanged records as well.

{
  "checks": [
    "dns"
  ],
  "incrementalMode": true,
  "stateKey": "dns-tracker"
}

Compact output for AI agents — Return only core fields for AI-agent and MCP workflows.

→ Small payload with the most important fields — ideal for piping into LLMs without token overhead.

{
  "checks": [
    "dns"
  ],
  "compact": true
}

Output

Each run produces a dataset of structured domain records. Results can be downloaded as JSON, CSV, or Excel from the Dataset tab in Apify Console.

Example domain record

{
  "domain": "stripe.com",
  "inputUrl": "stripe.com",
  "securityScore": 93,
  "emailGrade": "A",
  "dns": {
    "records": {
      "A": [
        "198.137.150.161",
        "198.202.176.161"
      ],
      "NS": [
        "ns-1882.awsdns-43.co.uk",
        "ns-423.awsdns-52.com",
        "ns-705.awsdns-24.net",
        "ns-1087.awsdns-07.org"
      ],
      "SOA": [
        {
          "nsname": "ns-1882.awsdns-43.co.uk",
          "hostmaster": "awsdns-hostmaster.amazon.com",
          "serial": 1,
          "refresh": 900,
          "retry": 900,
          "expire": 1209600,
          "minttl": 3600
        }
      ],
      "CAA": [
        {
          "critical": 0,
          "iodef": "mailto:caa-violations@stripe.com"
        },
        {
          "critical": 0,
          "issue": "amazon.com"
        },
        {
          "critical": 0,
          "issue": "digicert.com"
        },
        {
          "critical": 0,
          "issue": "visa.com"
        }
      ],
      "MX": [
        {
          "priority": 10,
          "exchange": "aspmx.l.google.com"
        },
        {
          "priority": 20,
          "exchange": "alt1.aspmx.l.google.com"
        },
        {
          "priority": 20,
          "exchange": "alt2.aspmx.l.google.com"
        },
        {
          "priority": 30,
          "exchange": "aspmx2.googlemail.com"
        },
        {
          "priority": 30,
          "exchange": "aspmx3.googlemail.com"
        }
      ],
      "TXT": [
        "google-site-verification=ZgGi2-xDdfnaWxdfjn5AqtUS11jKWqSXAV_EHODFzdE",
        "google-site-verification=hPfjsDwiisKJ4RP1ExOst9gAOD_0P8Q7-kxdcKUvEcc",
        "google-site-verification=pmz8ueKvWMPxNlwUDcVroF91-tq6I9VM6wSO_0i7-wc",
        "google-site-verification=qjP3OAiraClha_40cX9Z9FrG5q3O_0InXSamXOswY-s",
        "liveramp-site-verification=7gyFkTwGYsvgd7IUQwyAOfImETwR06wgKjKiXq90KEY",
        "... 26 more items"
      ]
    },
    "dnssec": false,
    "errors": {
      "AAAA": "ENODATA",
      "CNAME": "ENODATA"
    }
  },
  "emailAuth": {
    "hasMx": true,
    "spf": {
      "found": true,
      "record": "v=spf1 ip4:198.2.180.60/32 ip4:13.111.2.227/32 include:spf1.stripe.com include:greenhouse-outbound-mail.stripe.com include:_spf.qualtrics.com ~all",
      "all": "~all",
      "includes": [
        "spf1.stripe.com",
        "greenhouse-outbound-mail.stripe.com",
        "_spf.qualtrics.com"
      ],
      "verdict": "pass"
    },
    "dmarc": {
      "found": true,
      "record": "v=DMARC1; p=reject; pct=100; fo=1; rua=mailto:dmarc-reports@stripe.com; ruf=mailto:dmarc-forensics@stripe.com;",
      "policy": "reject",
      "pct": 100,
      "rua": [
        "mailto:dmarc-reports@stripe.com"
      ],
      "verdict": "pass"
    },
    "dkim": {
      "selectorsChecked": [
        "default",
        "google",
        "selector1",
        "selector2",
        "k1",
        "... 8 more items"
      ],
      "found": [
        "google",
        "mandrill"
      ],
      "verdict": "pass"
    },
    "dnssec": false,
    "score": 90,
    "grade": "A"
  },
  "blacklist": {
    "ip": "198.137.150.161",
    "checked": [
      "zen.spamhaus.org",
      "b.barracudacentral.org",
      "dnsbl.sorbs.net",
      "dbl.spamhaus.org"
    ],
    "note": "best-effort; datacenter resolvers may be refused by some zones"
  },
  "checkedAt": "2026-07-18T12:54:02.697Z",
  "source": "email-deliverability"
}

Incremental fields

When incremental mode is on, each record also carries:

• changeType — one of NEW, UPDATED, UNCHANGED, REAPPEARED, EXPIRED. Default output covers NEW / UPDATED / REAPPEARED; set emitUnchanged: true to opt into the others.

How to audit domains

1. Go to Email Deliverability Checker in Apify Console.
2. Configure the input.
3. Set maxResults to control how many results you need.
4. Click Start and wait for the run to finish.
5. Export the dataset as JSON, CSV, or Excel.

Use cases

• Score a list of sending domains for SPF / DMARC / DKIM before a cold-email or newsletter campaign, so mail lands in the inbox not spam.
• Monitor your sending domains for DMARC policy drift and blacklist appearances, and get alerted the moment deliverability degrades.
• Audit prospect or partner domains for email-authentication maturity as a data point for lead qualification.
• Run a pre-send deliverability check across an entire ESP tenant or agency client list in one pass.
• Combine with SSL/WHOIS/HTTP checks for a full security-and-deliverability posture review of a domain portfolio.

How much does it cost to audit domains?

Email Deliverability Checker uses pay-per-event pricing. You pay a small fee when the run starts and then for each result that is actually produced.

• Run start: $0.00005 per run
• Per result: $0.001 per domain record

Example costs:

• 10 results: $0.01
• 25 results: $0.025
• 100 results: $0.1
• 200 results: $0.2
• 500 results: $0.5

Example: recurring monitoring savings

These examples compare full re-scrapes with incremental runs at different churn rates. Churn is the share of domains that are new or whose tracked content changed since the previous run. Actual churn depends on your query breadth, source activity, and polling frequency — the scenarios below are examples, not predictions.

Example setup: 250 results per run, daily polling (30 runs/month). Event-pricing examples scale linearly with result count.

Churn rate	Full re-scrape run cost	Incremental run cost	Savings vs full re-scrape	Monthly cost after baseline
5% — stable niche query	$0.25	$0.01	$0.24 (95%)	$0.38
15% — moderate broad query	$0.25	$0.04	$0.21 (85%)	$1.13
30% — high-volume aggregator	$0.25	$0.08	$0.17 (70%)	$2.25

Full re-scrape monthly cost at daily polling: $7.50. First month with incremental costs $0.61 / $1.34 / $2.43 for the 5% / 15% / 30% scenarios because the first run builds baseline state at full cost before incremental savings apply.

Platform usage is included in the per-result fee shown above.

FAQ

How many domains can I check per run?

Every domain in your input list is checked — there is no fixed cap, so the number of domains per run is limited only by your list size and the run's time budget.

Does Email Deliverability Checker support recurring monitoring?

Yes. Enable incremental mode to only receive new or changed domains on subsequent runs. This is ideal for scheduled monitoring where you want to track changes over time without re-processing the full dataset.

Can I integrate Email Deliverability Checker with other apps?

Yes. Email Deliverability Checker works with Apify's integrations to connect with tools like Zapier, Make, Google Sheets, Slack, and more. You can also use webhooks to trigger actions when a run completes.

Can I use Email Deliverability Checker with the Apify API?

Yes. You can start runs, manage inputs, and retrieve results programmatically through the Apify API. Client libraries are available for JavaScript, Python, and other languages.

Can I use Email Deliverability Checker through an MCP Server?

Yes. Apify provides an MCP Server that lets AI assistants and agents call this actor directly. Use compact mode and excludeEmptyFields to keep payloads manageable for LLM context windows.

Is it legal to audit domains?

This actor queries publicly available DNS, WHOIS, certificate and reputation data for the domains you provide. Looking up public domain data is generally legal, but you should ensure your use complies with applicable laws and the queried services' terms, including GDPR where relevant.

Your feedback

If you have questions, need a feature, or found a bug, please open an issue on the actor's page in Apify Console. Your feedback helps us improve.

You might also like

• Domain Intelligence Scraper — All-in-one domain audit: DNS, WHOIS, SSL, HTTP, email authentication and blacklist checks with a.
• SSL Certificate Monitor — Bulk SSL/TLS certificate check: issuer, expiry, chain validity and SANs with expiring-soon alerts.
• DNS Lookup — Bulk DNS record lookup: A, AAAA, MX, TXT, CNAME, NS, SOA, CAA and DNSSEC per domain.

Getting started with Apify

New to Apify? Create a free account with $5 credit — no credit card required.

1. Sign up — $5 platform credit included
2. Open this actor and configure your input
3. Click Start — export results as JSON, CSV, or Excel

Need more later? See Apify pricing.