Enter a domain and get an A–F email-security grade, a check-by-check breakdown (DMARC, SPF, DKIM, MTA-STS, TLS-RPT, BIMI, DNSSEC, security.txt) and the exact issues to fix. Free, no sign-up.
The plain-English reasons the bulk Actor attaches to each domain for teams that prospect on email posture. If this is your own domain, read them as a to-do list.
This page runs the same code as our paid Email Security Signals Actor: the grading files are copied byte for byte, so a domain gets the same grade here as in a bulk run (two exceptions: security.txt is fetched from our server, and a site that blocks automated requests may answer it differently; and the MTA-STS policy file isn’t fetched here, so a published _mta-sts record earns its 5 points, while the Actor also fetches the policy and awards them only for a working enforce or testing policy that covers the domain’s MX hosts). Scores add up to 100:
| DMARC (40) | A valid record at p=reject earns 35, p=quarantine 30, p=none 15; plus 5 for a rua= reporting address. Enforcement in testing mode (t=y) or at pct below 100 costs 5. A subdomain without its own record is graded on its parent’s. |
|---|---|
| Duplicate DMARC (−10) | A subdomain that publishes several v=DMARC1 records of its own loses 10 when its parent’s record is valid: receivers discard all of them, so it is graded on its parent’s record, and receivers that still follow RFC 7489 apply no DMARC policy at all. |
| SPF (20) | Exactly one record, within the 10 DNS-lookup limit and with no permerror: 20. Ending in ?all costs 10, no all at all costs 5, and +all scores 0. A broken or duplicated record scores 5. |
| DKIM (15) | A key found at one of the common selectors we probe. |
| Parked domains | A domain that declares it sends no mail (no MX, SPF exactly v=spf1 -all, DMARC p=reject with sp and np also reject, no t=y, pct 100) isn’t expected to publish DKIM, MTA-STS, TLS-RPT or BIMI, so it gets those points unless one of them is misconfigured. |
| 5 points each | MTA-STS (here: a published v=STSv1 record; the policy file isn’t verified in the browser), TLS-RPT, BIMI, DNSSEC, and a /.well-known/security.txt with a Contact: field whose Expires: date hasn’t passed. |
| Letter | A from 85, B from 70, C from 55, D from 40, F below. Unless it has both a valid SPF record and a valid DMARC record, a domain is capped at D. |
A lookup that fails (resolver error or timeout) is reported as unknown and not penalised, so a flaky resolver never makes a domain look spoofable. DKIM keys can’t be listed, only probed by selector name, so “no DKIM key found” can mean the domain uses a selector we don’t try. “Bulk-sender compliant” means SPF passes, DMARC is published and DKIM was found, the authentication part of the Gmail, Yahoo and Microsoft bulk sender rules.
Privacy: DNS lookups go straight from your browser to Cloudflare’s public DNS resolver (cloudflare-dns.com), and a lookup that fails there is asked once more at Google’s (dns.google). Browsers can’t read another site’s security.txt, so that one check goes through our server, which answers only yes or no (and, for an expired file, its Expires: date). For the same reason the MTA-STS policy file isn’t fetched here: the page checks only that the _mta-sts record is published. We don’t store the domains you check.
The same engine runs in bulk on Apify: paste domains, URLs or email addresses and get one row per domain with every field above, ready to export as CSV. $0.02 per graded domain; invalid inputs, duplicates, domains that don’t exist (NXDOMAIN) and DNS lookup failures are free.
Grade a list on Apify →Or have us grade your list free: send up to 100 domains to hello@siftsmith.com, and we’ll run them through Email Security Signals and email you a CSV file with each domain’s grade, the issues found and whether it meets the bulk-sender rules, or the reason a domain couldn’t be graded.
More on what the Actor returns and how it’s priced, what Gmail, Yahoo and Microsoft require from bulk senders, fixing SPF “too many DNS lookups”, fixing Outlook’s 550 5.7.515 bounce, fixing the 550 5.7.509 DMARC reject bounce, fixing “DMARC alignment failed” when SPF or DKIM pass, moving DMARC from p=none to quarantine and reject, fixing “multiple DMARC records found”, fixing “multiple SPF records”, fixing Microsoft 365 DKIM “CnameMissing”, fixing DKIM “no key for signature”, splitting an SPF record over 255 characters, fixing SPF “too many void lookups”, fixing Gmail’s 550 5.7.25 missing-PTR bounce, checking that your DMARC report addresses are authorized, and fixing a BIMI logo that isn’t showing. All fixes are listed on the email authentication error fixes page.
How do well-known software companies compare? See DMARC adoption statistics for the Forbes Cloud 100: how many use p=reject, SPF -all, MTA-STS and BIMI.
Only need to know who hosts a company’s email? The free email provider checker shows Google Workspace, Microsoft 365 or a security gateway for up to 50 domains at once, and which email providers SaaS companies use benchmarks the 2025 Forbes Cloud 100.