Bulk Email Deliverability Checker — MX, SPF, DKIM, DMARC & BIMI avatar

Bulk Email Deliverability Checker — MX, SPF, DKIM, DMARC & BIMI

Pricing

from $3.50 / 1,000 results

Go to Apify Store
Bulk Email Deliverability Checker — MX, SPF, DKIM, DMARC & BIMI

Bulk Email Deliverability Checker — MX, SPF, DKIM, DMARC & BIMI

Check email deliverability for thousands of domains in bulk. Verifies MX records, parses SPF policies, discovers DKIM selectors, parses DMARC tags and checks BIMI. Returns a detailed deliverability score per domain. No API key — ideal for cold email campaigns and email marketing audits.

Pricing

from $3.50 / 1,000 results

Rating

0.0

(0)

Developer

Logiover

Logiover

Maintained by Community

Actor stats

0

Bookmarked

5

Total users

0

Monthly active users

5 days ago

Last modified

Features

Limited permissions

Share

Bulk Email Deliverability Checker — MX, SPF, DKIM, DMARC & BIMI Audit (No API)

Apify Actor No API key Pay per result Email Deliverability Export

Check the email deliverability of thousands of domains in a single run. This bulk email deliverability checker queries every domain's DNS for the five pillars of inbox placement — MX (mail servers), SPF (sender policy), DKIM (signing keys), DMARC (spoofing protection) and BIMI (brand logos) — and returns a detailed report for each domain: pass/fail per protocol, a parsed policy breakdown, a numeric 0–100 deliverability score, an A+ to F grade, and a plain-English list of issues. Paste a domain list and the Actor resolves every record for a domain in parallel, over direct DNS with DNS-over-HTTPS as an automatic fallback. Fast, no browser, no API key, no login.

🏆 Why this email deliverability checker?

5-protocol audit (MX · SPF · DKIM · DMARC · BIMI) · 29 fields per domain · 31 DKIM selectors probed · thousands of domains per run · weighted 0–100 score + A+→F grade · direct DNS-over-HTTPS (no browser, no API key) · export to JSON / CSV / Excel. The unofficial bulk SPF/DMARC audit tool and email authentication scanner for cold-email prep, deliverability consulting and brand protection.


✨ What this Actor does / Key features

  • 📬 5-protocol audit — MX, SPF, DKIM, DMARC and BIMI checked in a single pass per domain, the complete email-authentication stack.
  • 🎯 Numeric score (0–100) — each protocol carries a weight (MX = 25, SPF = 25, DMARC = 25, DKIM = 15, BIMI = 8, +2 redundancy bonus for ≥2 MX records). Every domain is graded A+, A, B, C, D or F.
  • 🧩 Deep SPF parse — extracts the enforcement policy (+all / ~all / -all / ?all), counts the DNS lookups the record triggers (the RFC 7208 limit is 10), and lists every include: mechanism.
  • 🔑 DKIM selector discovery — probes 31 common selectors (google, sendgrid, mailgun, amazonses, microsoft, docusign, protonmail, etc.) and reports which ones actually exist.
  • 📜 Full DMARC tag parse — p (policy), pct (percentage of mail enforced), rua (aggregate reports), ruf (forensic reports) and sp (subdomain policy).
  • 🖼️ BIMI check — queries default._bimi.<domain> and extracts the brand-logo SVG URL when present.
  • 📋 Human-readable issues list — plain-English problems per domain (e.g. "No DMARC record — no protection against domain spoofing", "SPF has 12 DNS lookups (RFC limit is 10)").
  • ⚡ High concurrency — configurable parallel DNS queries (default 10, up to 100) so large lists finish fast.
  • 🛰️ Resilient resolution — direct DNS first, then Cloudflare DNS-over-HTTPS and Google DNS as automatic fallbacks; the answering resolver is recorded per row.
  • 🔑 No API key, no login — uses public DNS only. Just an Apify account.

🚀 Quick start (3 steps)

  1. Configure — paste your list of domains into Domains, one per line (example.com or https://example.com — schemes and paths are stripped automatically).
  2. Run — click Start. The Actor resolves MX, SPF, DKIM, DMARC and BIMI for every domain in parallel and streams one report row per domain into your dataset.
  3. Get your data — open the Output tab and export to JSON, CSV, Excel or XML, or pull it via the Apify API. Sort by deliverabilityScore to surface the weakest domains first.

📥 Input

Give the Actor at least one entry in domains. Everything else is optional.

Example — audit a cold-email prospect list

{
"domains": ["stripe.com", "github.com", "mailchimp.com", "shopify.com"],
"maxConcurrency": 10,
"proxyConfiguration": { "useApifyProxy": true }
}

Example — bulk SPF/DMARC compliance scan of your own portfolio

{
"domains": [
"brand-main.com",
"brand-shop.com",
"brand-newsletter.com",
"brand-support.com"
],
"maxConcurrency": 20,
"proxyConfiguration": { "useApifyProxy": true }
}

Example — fast, high-concurrency scan of a large domain list

{
"domains": ["example1.com", "example2.com", "example3.com", "…thousands more…"],
"maxConcurrency": 100,
"proxyConfiguration": { "useApifyProxy": true }
}
FieldTypeDescription
domainsarrayDomains to check email deliverability for — one entry per domain (e.g. example.com). Schemes (https://) and paths are stripped automatically and duplicates are de-duplicated. Required.
maxConcurrencyintegerHow many domains to check in parallel. Higher is faster but may hit resolver rate limits. Default 10, minimum 1, maximum 100.
proxyConfigurationobjectApify Proxy settings used for the DNS-over-HTTPS fallback requests. Recommended (default: { "useApifyProxy": true }) to avoid rate limiting on large lists.

Tip: Run your own domain first to see what a "good" score looks like, then benchmark prospects, vendors and acquisition targets against it.

Additional input fields

These optional fields are also available in the input form and API:

FieldTypeDefaultDescription
maxResultsinteger1000Maximum number of domains to check in this run. Keeps empty/large inputs fast and cheap. Raise it to process more.
sortBystring"input"Order of the output rows.

📤 Output

One row per domain — 29 fields, exportable to JSON, CSV, Excel or XML. Here is a trimmed sample record:

{
"domain": "stripe.com",
"deliverabilityScore": "95",
"grade": "A+",
"hasMx": "true",
"mxRecords": "10 aspmx.l.google.com, 20 alt1.aspmx.l.google.com, 30 alt2.aspmx.l.google.com",
"mxCount": "3",
"hasSpf": "true",
"spfRaw": "v=spf1 include:_spf.google.com include:_spf.stripe.com -all",
"spfPolicy": "hardfail (-all)",
"spfIncludes": "_spf.google.com, _spf.stripe.com",
"spfLookupCount": "2",
"hasDmarc": "true",
"dmarcRaw": "v=DMARC1; p=reject; pct=100; rua=mailto:dmarc@stripe.com",
"dmarcPolicy": "reject",
"dmarcPct": "100",
"dmarcRua": "mailto:dmarc@stripe.com",
"dmarcRuf": null,
"dmarcSubdomainPolicy": null,
"hasDkim": "true",
"dkimSelectorsFound": "google, mailgun",
"hasBimi": "true",
"bimiSvgUrl": "https://bimi.stripe.com/logo.svg",
"passCount": "5",
"totalChecks": "5",
"issues": null,
"resolver": "cloudflare",
"checkedAt": "2026-07-06T12:00:00.000Z"
}

💡 Use cases

  • Cold email campaign prep — audit the email infrastructure of your prospect list before sending; flag domains with no MX or weak SPF so you skip risky sends and protect your sender reputation.
  • Email deliverability consulting — run bulk audits for clients, generate A+→F scorecards, and sell remediation plans off the issues column.
  • Brand protection — find domains in your portfolio that lack DMARC or run a weak p=none policy and are therefore exposed to exact-domain spoofing.
  • Google & Yahoo bulk-sender compliance — SPF, DKIM and DMARC are table stakes for bulk senders since 2024; grade every sending domain before it causes authentication failures.
  • M&A due diligence — assess the email-security posture of an acquisition target's entire domain portfolio in one run.
  • Domain broker / portfolio management — scan parked and managed domains for email readiness and resale value.

👥 Who uses it

Cold-email & lead-gen teams · email deliverability consultants & agencies · email-marketing and CRM operators · brand-protection and security teams · MSPs and IT admins · domain brokers & portfolio managers · M&A and due-diligence analysts.

💰 Pricing

This Actor runs on a simple pay-per-result model — you pay for the domain reports you generate, with no separate Apify platform fees to calculate. Try it on the free tier first, then scale up. See the Pricing tab on this page for the current rate.

❓ Frequently Asked Questions

Is it legal to check email deliverability for these domains? Yes. The Actor only reads publicly published DNS records (MX, SPF, DKIM, DMARC, BIMI) — the same data any mail server queries to route and authenticate email. You are responsible for using the results in compliance with applicable laws such as GDPR and the terms of the services involved.

Is there a public email deliverability API? Is this an API alternative? There is no single free public API that returns MX + SPF + DKIM + DMARC + BIMI parsed and scored together. This Actor works as that email authentication API alternative — it resolves all five record types over public DNS and returns a structured, scored report per domain with no API key.

Do I need an API key or a login? No. There is no account, login or API key for any third-party service required — only an Apify account. Resolution runs over public DNS, falling back to Cloudflare and Google DNS-over-HTTPS.

How do I check email deliverability for many domains at once? Paste your full domain list into Domains and run the Actor. It checks MX, SPF, DKIM, DMARC and BIMI for every domain in parallel and returns one scored row per domain.

How much data can I check / how many domains can I scan? You can scan thousands of domains per run. Throughput is governed by maxConcurrency (up to 100 parallel domains). Note that each domain triggers ~36 DNS queries (MX + SPF + DMARC + 31 DKIM selectors + BIMI), so keep the proxy enabled on very large lists to avoid resolver rate limits.

Can I export deliverability reports to CSV or JSON? Yes. Each domain is one row with columns for every protocol, the score, the grade and the parsed policies. Download the dataset as CSV, JSON, Excel or XML, or pull it through the Apify REST API.

Does it check individual email addresses or mailboxes? No — this is a domain-level email deliverability audit. It checks the DNS configuration that determines whether mail from (or to) a domain authenticates and gets delivered, not individual mailbox validity. For address-level checks, see our Bulk Email Verifier.

How do I bulk check SPF and DMARC records for a domain list?

Paste your domains into the input and the checker resolves SPF and DMARC (plus MX, DKIM and BIMI) for every domain in parallel over DNS-over-HTTPS, returning a parsed policy breakdown — SPF enforcement + lookup count, DMARC p/pct/rua/ruf/sp — for each one.

Which DKIM selectors are probed?

31 common selectors: google, default, dkim, selector1, selector2, mail, s1, s2, k1, k2, key1, key2, amazonses, sendgrid, mailgun, mandrill, sparkpost, postmark, mimecast, proofpoint, docusign, zendesk, hubspot, salesforce, pm, protonmail, protonmail2, protonmail3, ms365, microsoft, outlook. Custom selectors that don't match these common names won't be discovered — DKIM selectors are not enumerable from DNS by design.

What's the difference between this and a plain DNS lookup?

A raw DNS lookup just returns records. This Actor parses them: it decodes SPF policies and counts lookups, discovers DKIM selectors by probing, parses every DMARC tag, checks BIMI, computes a weighted 0–100 deliverability score with an A+→F grade, and flags specific issues in plain English. For raw records, use our Bulk DNS Records Lookup.

Does it meet the Google and Yahoo bulk-sender requirements check?

Yes. It verifies the SPF, DKIM and DMARC authentication that Google and Yahoo now require from bulk senders and grades each domain A+ to F, so you can fix gaps before they cause delivery failures.

How do I audit a cold-email prospect list before sending?

Run your prospect domains through the checker and sort by deliverabilityScore ascending to surface domains with no MX or weak SPF; filter dmarcPolicy: none to find spoofable domains. Skip or warm up the risky ones before you send.

🔗 More B2B, email & website data tools by logiover

Building a full outreach / domain-intelligence pipeline? Pair this checker with the rest of the email, DNS and website suite:

ActorWhat it does
Bulk DNS Records LookupRaw DNS resolver (A, AAAA, MX, TXT, NS, CNAME, SOA, CAA) over DNS-over-HTTPS
Bulk Email VerifierValidate individual email addresses — syntax, MX, SMTP, catch-all detection
Bulk SSL Certificate CheckerSSL/TLS certificate inspection, expiry and chain details for domains
Bulk WHOIS / RDAP LookupDomain registration, registrar, nameservers and expiry data
Bulk HTTP Security HeadersAudit HSTS, CSP, X-Frame-Options and other security headers in bulk
Bulk URL Status CheckerBulk HTTP status, redirect chains and response-time checks
Website Contact ScraperExtract emails, phones and social links from any list of websites
Subdomain FinderDiscover subdomains of a domain for full attack-surface / asset mapping
Certificate Transparency MonitorTrack newly issued TLS certificates for a domain via CT logs
B2B Lead ScraperBuild B2B company + contact lead lists by sector and country

👉 Browse all logiover scrapers on Apify Store — 180+ actors across real estate, jobs, crypto, social media & B2B data.

⏰ Scheduling & integration

Schedule this Actor on Apify to re-audit your sending domains or prospect lists daily or weekly and catch DMARC/SPF drift the moment it happens. Export results to JSON, CSV or Excel, sync to Google Sheets, or push to your database, BI tools and webhooks through the Apify API. Connect it to Make, n8n or Zapier to trigger alerts when a domain's deliverabilityScore drops or its dmarcPolicy weakens.

🤖 AI Agents, MCP & RAG Integration

Bulk Email Deliverability Checker works natively as an on-demand data tool for AI assistants and autonomous workflows.

Connect this Actor directly to Apify AI, Claude Desktop, Cursor, VS Code, Windsurf, LangChain, or LlamaIndex via the official Apify MCP Server — no custom wrapper code needed:

{
"mcpServers": {
"apify": {
"type": "http",
"url": "https://mcp.apify.com?tools=logiover/bulk-email-deliverability-checker"
}
}
}
  • Schema-typed inputs & outputs: Clean JSON records with explicit .actor/input_schema.json and .actor/output_schema.json definitions so LLM agents infer parameters and parse fields accurately without HTML noise.
  • Bounded & predictable runs: Built-in volume caps and pay-per-result budget guards prevent runaway agent tool loops.
  • RAG & automation ready: Stream run datasets straight into vector stores, n8n, Make, Zapier, or webhook pipelines.

💬 Support, Issues & Reviews

This Actor reads only publicly published DNS records and is intended for legitimate email-deliverability, security-research and lead-generation use. You are responsible for complying with GDPR, the terms of service of the services involved, and any applicable local laws when using the data.


This Actor is an independent tool. It is not affiliated with, endorsed by, or sponsored by Bulk Email Deliverability; Bulk Email Deliverability and all other trademarks mentioned here are the property of their respective owners.

Email Deliverability scraping — frequently asked questions

Do I need a Email Deliverability API key, account or login?

No. This Actor reads publicly available pages and feeds, so there is nothing to register for and no credentials to manage.

How do I export Email Deliverability data to CSV, Excel, JSON or Google Sheets?

Open the Storage tab after a run and pick the format you want — CSV, Excel, JSON, XML or an HTML table. For Google Sheets, Airtable or a database, use the dataset URL or the Apify API so the sheet refreshes itself on every run.

Can I schedule this Email Deliverability scraper to run daily or hourly?

Yes. Use the Schedules tab and pick a cadence. Daily is enough for most tracking work; pick hourly only if the rows you care about really do change that fast.

How many rows can I get, and what does it cost?

See the volume section above for a measured figure. Billing is per result, so you pay for the rows you actually receive and a run that finds nothing costs nothing.

This Actor collects only information that Email Deliverability publishes publicly. It does not log in, does not defeat access controls and does not touch private data. You remain responsible for how you use the output, including under GDPR and similar rules where personal data is involved.

What happens if Email Deliverability blocks the run or changes its layout?

A refused exit IP is swapped for a fresh one within a quarter of a second and retried, and rate limiting is waited out rather than fought. If nothing gets through, the run fails with the reason instead of reporting success with zero rows — so an empty result always means "no matches", never "the source would not answer".

Can I use this with an AI agent, LangChain or an MCP client?

Yes. The Actor is callable over the Apify API and through Apify's MCP server, so an agent can run it and read the dataset back as a tool call.

📝 Changelog

2026-11-14

  • Verified live production health run (2026-11-14): extracted 4 structured records in 1.9s with valid schema output.
  • Hardened internal proxy stall fallback and pay-per-event dataset instance budget protection.

2026-11-11

  • Added reliable terminal run status telemetry and structured Apify AI / MCP Server (mcp.apify.com) tool configuration.
  • Added direct Issues & Reviews support links and refreshed live maintenance verification.

2026-11-01

  • Monthly health check (2026-11-01): a live run on the current build completed successfully and returned data. Input options, output fields and pricing are unchanged.
  • README refreshed: 2 links to renamed Actors updated; independence disclaimer added; documented 2 additional input fields.

2026-10-15

  • Every request now has a hard time limit, so a proxy connection that stalls can no longer hold up the run or push it past its timeout.
  • A run that reaches its maximum cost per run now stops cleanly with its results saved and a status message, instead of ending as aborted.
  • A proxy group your account cannot use no longer stops the run at start-up; it falls back to the default Apify Proxy.
  • Memory is managed within the run's own limit, which removes a rare out-of-memory crash on large pages.

2026-09-23

  • Fleet-wide quality audit. Verified end to end against live data and re-checked the input schema, the output columns and the run configuration.
  • Output verified on a live run: 60 row(s) across 29 columns, 89.2% of cells populated.
  • Run reliability reviewed: 93.3% of public runs succeeded in the last 30 days.
  • Input schema, output schema and pricing configuration reviewed.

2026-09-01

  • Fixed the run overrunning the 5-minute limit: the 35 DNS lookups a domain needs (MX, SPF, DMARC, BIMI and 31 DKIM selectors) were issued one after another over proxied HTTPS. They now resolve over direct DNS and run in parallel — the default input went from ~316 s to ~3 s, with identical results.
  • DNS-over-HTTPS (Cloudflare, then Google) is now an automatic fallback rather than the only path, so resolution still works where direct DNS is unavailable.
  • Results are now written to the dataset as they are produced instead of only at the very end, so a run that is cut short still saves everything it checked.
  • The time budget is now enforced during a domain's checks, not only between domains — previously a run with fewer domains than workers could never stop itself.
  • A transient Apify Proxy error no longer aborts the run before the first domain is checked.
  • Shortened the per-request DNS-over-HTTPS timeout from 20 s to 8 s so one unresponsive resolver cannot stall a batch.

2026-07-18

  • Maintenance & reliability pass — re-verified end-to-end against live data via the Apify API; confirmed the Actor completes successfully and returns non-empty, well-formed results within the 5-minute quality window on its default input.
  • Refreshed build so the latest version is current; no change to inputs, output fields or scraping logic.

2026-07-12

  • Input is now fully optional — running with empty input checks a built-in set of well-known domains, so you always get results.
  • Input now accepts full email addresses too (e.g. hi@example.com); the domain is extracted automatically.
  • Added maxResults (default 1000) to bound large/empty runs and keep them fast and cheap.
  • Added sortBy dropdown (input order / highest score / worst offenders / best grade) to order the output.
  • Numeric fields (mxCount, spfLookupCount, dmarcPct, deliverabilityScore, passCount, totalChecks) are now real numbers, and hasMx/hasSpf/hasDmarc/hasDkim/hasBimi are real booleans (previously strings).
  • Added a per-record dataset fields schema (nullable-safe) with titles and descriptions.
  • Added a ~4-minute time budget: long runs stop gracefully and save everything collected.
  • Proxy defaults to Apify Proxy (AUTO) for the DNS-over-HTTPS requests; the dead DATACENTER-only group is never forced.

2026-07-06

  • ✨ README overhaul: added shields badges, ready-to-run example scenarios, a complete 29-field output reference, expanded high-intent FAQ, and a cross-linked email/DNS/website tool grid.

2026-07-01

  • Maintenance pass: re-verified end-to-end on live data and confirmed successful runs within the 5-minute quality window on the default input.
  • Sharpened Store metadata (SEO title & description) and expanded the FAQ with high-intent, long-tail questions for easier discovery in Google and Apify Store search.
  • Added ready-to-run example tasks that cover common real-world use cases.

2026-06-24

  • Initial release — 5-protocol email deliverability audit (MX, SPF, DKIM, DMARC, BIMI), weighted scoring, 31 DKIM selectors probed, no API key, CSV/JSON export.

*Maintained: last verified 2026-11-14 — checked end-to-end against live run history (reliability, output fields and types, and time/memory budgets).