Domain Email Security Audit - SPF, DMARC, DKIM, MTA-STS, DNSSEC
Pricing
from $3.00 / 1,000 domain auditeds
Domain Email Security Audit - SPF, DMARC, DKIM, MTA-STS, DNSSEC
Bulk-check domains for SPF lookup limit, DMARC, DKIM key size, MTA-STS, TLS-RPT, BIMI, CAA, DNSSEC and HTTPS certificate expiry. Score, grade and fix list.
Pricing
from $3.00 / 1,000 domain auditeds
Rating
0.0
(0)
Developer
Stephen
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
18 days ago
Last modified
Categories
Features
Share
Domain Email Security Audit — SPF, DMARC, DKIM, MTA-STS, DNSSEC
Paste a list of domains, get one row per domain with a 0–100 score, an A–F grade and a prioritised fix list, plus the raw findings:
| Check | What you get |
|---|---|
| SPF | Record, all qualifier, includes, recursive DNS-lookup count vs the RFC 7208 limit of 10, ptr use, duplicate records |
| DMARC | Policy, subdomain policy, pct, alignment; falls back to the organisational domain and tells you when the policy is inherited. Report addresses are shown as mailto:***@domain (mailbox removed) |
| DKIM | Keys found at ~36 common selectors + your own, key type and RSA key size (flags < 2048-bit), revoked keys |
| MX | MX hosts, null MX (RFC 7505) detection |
| MTA-STS | _mta-sts TXT, policy file from https://mta-sts.<domain>/.well-known/mta-sts.txt (RFC 8461), mode, and whether every MX is covered |
| TLS-RPT, BIMI | Presence and settings |
| CAA | Allowed certificate authorities (inherited from parent zones per RFC 8659) |
| DNSSEC | Signed (DS at parent) and validated (AD flag from a validating resolver) |
| HTTPS | Certificate issuer, TLS version and days until expiry |
Domains without MX are treated as non-mail domains: they're scored on the "don't let anyone spoof me" basics (SPF -all, DMARC reject) instead of being penalised for missing DKIM/MTA-STS.
Quick start
- Paste domains (URLs and email addresses are accepted and reduced to the domain).
- Optional: add your mail provider's DKIM selector (e.g.
google,selector1) so DKIM can be found. - Click Start. The prefilled example audits
example.comandcloudflare.comin a few seconds.
Who it's for
- Agencies, MSPs and IT consultants auditing client portfolios before Google/Yahoo/Microsoft bulk-sender rules bite.
- Cold-email / deliverability teams checking sending domains every week (schedule it and diff the results with any dataset-diff Actor).
- Security teams monitoring brand domains for weak DKIM keys, missing DMARC or expiring certificates.
Pricing (pay per event)
| Event | Price |
|---|---|
| Domain audited | $0.003 per domain |
| Actor start (Apify standard, once per run) | $0.0003 |
Invalid domains and domains that don't exist (NXDOMAIN) are free. 1,000 domains = $3. Set "Maximum cost per run" and the Actor stops cleanly when it's reached.
Input example
{ "domains": ["example.com", "https://www.cloudflare.com/", "postmaster@yourcompany.co.jp"], "dkimSelectors": ["s2048"] }
Output example
Real output for example.com: listing/output-example.json. Each row has domain, status, score, grade, issues[] (severity, code, message, points) and one object per check (spf, dmarc, dkim, mx, mtaSts, tlsRpt, bimi, caa, dnssec, https).
How it works / responsible use
- All data comes from public DNS, by default through Cloudflare's public resolver 1.1.1.1 over DNS-over-HTTPS (no API key; Cloudflare's resolver privacy commitments apply). About 40–60 small DNS queries per domain.
- The only HTTP request is the MTA-STS policy file at the fixed well-known URL defined by RFC 8461 (published precisely so that senders fetch it automatically), sent without following redirects as the RFC requires. The HTTPS check opens one TLS handshake to port 443 and reads the certificate; no pages are crawled.
- No personal data is collected or stored: no WHOIS, no SOA contact mailbox, and email addresses in DMARC/TLS-RPT/CAA records are reduced to their domain.
- Connections to private/internal IP addresses are refused.
- DKIM selectors can't be enumerated, so "DKIM not found" means "not at the selectors tried" — add your provider's selector.
Limits
- The score is our own weighting, not an industry standard. It is a checklist, not a deliverability guarantee.
- DNS answers come from one resolver at one moment; changes still propagating may not show yet.
- Default memory 256 MB; our test run (1 domain) peaked at 55 MB.
Use it from the API
Run it and get the results in one call (send your Apify token in the header, not in the URL):
curl -X POST "https://api.apify.com/v2/acts/noisy_jubilee~domain-email-security-audit/run-sync-get-dataset-items" \-H "Authorization: Bearer $APIFY_TOKEN" -H 'Content-Type: application/json' \-d '{"domains":["example.com"]}'
You can also schedule it in Apify Console, call it from the Apify Python/JavaScript clients, or connect the dataset to Make, Zapier, Slack, email or a webhook.
FAQ
Why does it say DKIM not found when we sign mail? DKIM selectors cannot be listed from DNS. Add your provider's selector in DKIM selectors.
Does it send email or log in anywhere? No. It only reads public DNS, one well-known MTA-STS policy file and one HTTPS certificate per domain.
Is the score an industry standard? No, it is our own weighting. Use the issues[] list as the to-do list.
Are invalid or non-existent domains charged? No.
Not affiliated with Google, Microsoft, Yahoo, Cloudflare or any mailbox provider.
No warranty
Provided as is, without warranty of any kind. Results are automated and can be incomplete or wrong; check anything important against the original source before relying on it.