Free tool
Scan a domain's email security in one pass. The scanner looks up seven DNS records, SPF, DKIM, DMARC, BIMI, MTA-STS, TLS-RPT and MX, scores the setup out of 10 and lists what to add.
Checking whether a domain is ready to send cold email? Use the deliverability score instead. It validates SPF, DKIM, DMARC and MX in more depth and adds a blacklist check.
Walkthrough
A 39-second walkthrough. Most of the score comes from SPF, DKIM, MX and DMARC, and 8 or above is in good shape. MTA-STS shows up in the results too, but it protects mail coming in to you, not the cold email you send. In the demo a domain scores 6 with no DMARC, then 8 after adding a basic record.
Step 1
Type the bare domain, such as yourdomain.com. A leading https:// and a trailing slash are removed. Enter a subdomain to scan that name on its own.
Step 2
The scanner runs the seven DNS lookups and returns a security score out of 10.
Step 3
SPF, DKIM, DMARC, BIMI and MTA-STS each have a card. Click one to see the record found, SPF warnings, DKIM selectors or the DMARC policy.
Step 4
Work through the Recommendations list, publish the missing records at your DNS host, then click New Scan.
Each record below is a live DNS lookup. SPF, DKIM and DMARC are the core of email authentication, so they carry most of the points. A record that exists adds points to the score. The points add up to 11, and the score is capped at 10, so a domain can reach the top score without every optional record.
| Record | Where the scanner looks | Points |
|---|---|---|
| SPF | TXT at yourdomain.com starting v=spf1 | 2, plus 0.5 with no warnings (over 10 lookups, +all) |
| DKIM | TXT at <selector>._domainkey.yourdomain.com for 6 common selectors | 2.5 when a key is found |
| DMARC | TXT at _dmarc.yourdomain.com starting v=DMARC1 | 2, plus 0.5 for p=quarantine or 1 for p=reject |
| MTA-STS | TXT at _mta-sts.yourdomain.com containing v=STSv1 | 1 |
| MX | MX records at yourdomain.com | 1 |
| BIMI | TXT at default._bimi.yourdomain.com containing v=BIMI1 | 0.5 |
| TLS-RPT | TXT at _smtp._tls.yourdomain.com containing v=TLSRPTv1 | 0.5 |
DKIM selectors. The scanner tries google, default, selector1, selector2, dkim, mail. If your provider signs with another selector, the scan reports DKIM as not found. Look up the s= value in a sent email's DKIM-Signature header and test it in the DKIM checker.
MX and TLS-RPT. Both are looked up and scored, but the results show cards for the other five records only. A missing MX record appears in the Recommendations list instead.
The bands match the label shown under your score. The setups described are the usual way a domain lands in each band.
8 to 10
SPF, DKIM, DMARC and MX are all in place. Scores above 8 add a stricter DMARC policy or MTA-STS.
6 to 7.9
One core piece is missing, most often the DMARC record.
4 to 5.9
SPF or DKIM is missing, so receivers can only partly verify mail from the domain.
0 to 3.9
Only one of SPF, DKIM and DMARC is in place, or none of them.
Worked example: a domain with a clean SPF record, a DKIM key, MX records and DMARC at p=none scores 8. The same domain with no DMARC record scores 6. Moving DMARC to p=reject raises it to 9, and adding MTA-STS takes it to 10.
Every record here is a TXT record except MX. Add it at your DNS host with the host name shown, replace yourdomain.com with your domain, and scan again once it has propagated.
| Record | Host | Example value |
|---|---|---|
| SPF | @ | v=spf1 include:_spf.google.com ~all |
| DMARC | _dmarc | v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com |
| MTA-STS | _mta-sts | v=STSv1; id=20261027 |
| TLS-RPT | _smtp._tls | v=TLSRPTv1; rua=mailto:tls-reports@yourdomain.com |
| BIMI | default._bimi | v=BIMI1; l=https://yourdomain.com/logo.svg |
The SPF example is for Google Workspace; use the include your mail provider gives you. DKIM keys are generated by your provider, so copy the selector and key from its admin panel. MTA-STS also needs a policy file at https://mta-sts.yourdomain.com/.well-known/mta-sts.txt. This scan only reads the TXT record, so confirm the policy file with the MTA-STS checker. BIMI shows your logo only once DMARC is at quarantine or reject; the DMARC generator builds that record for you.
A 0 to 10 sending-readiness score with a blacklist check.
Validate your SPF records and ensure proper email authentication.
Verify DKIM signatures and public key configuration.
Analyze email headers for authentication and routing information.
Test your emails against spam filters and improve deliverability.
Calculate optimal mailbox counts for your email infrastructure.
FAQ
It looks up seven DNS records on the domain you enter: SPF, DKIM, DMARC, BIMI, MTA-STS, TLS-RPT and MX. For each one it reports whether the record exists, shows the record it found, and adds points to a domain security score out of 10. Missing SPF, DKIM, DMARC, MX or MTA-STS records also appear as recommendations.
SPF is worth 2 points plus 0.5 when it has no warnings. A DKIM key at any of the six selectors checked is worth 2.5. DMARC is worth 2, plus 0.5 for p=quarantine or 1 for p=reject. MTA-STS and MX are worth 1 each, and BIMI and TLS-RPT are worth 0.5 each. The total is capped at 10.
8 or higher. A domain with SPF, DKIM, MX and a DMARC record at p=none scores 8. Moving DMARC to p=reject takes it to 9. Reaching 10 also needs MTA-STS, or BIMI and TLS-RPT together. Below 6 usually means one of SPF, DKIM or DMARC is missing.
The scanner tries six common selectors: google, default, selector1, selector2, dkim and mail. If your provider uses a different selector, such as a dated Google selector or k1 for Mailchimp, the scan will not find it. Open a sent email, find the s= value in the DKIM-Signature header, and check that selector by name with the DKIM checker.
No. It only reads DNS records on your domain. To see whether a domain or IP is listed on spam blocklists, use the Inboxkit deliverability score, which checks 10 blocklists, or the blacklist checker.
The domain scanner is a broad email security scan: seven records, including BIMI, MTA-STS and TLS-RPT, with extra weight for a strict DMARC policy. The deliverability score answers a narrower question, whether a domain is ready to send: it validates SPF, DKIM, DMARC and MX in more depth, checks 35 DKIM selectors and adds a blacklist check. Use the scanner to audit a domain, and the deliverability score before you send cold email from it.
Not directly. MTA-STS tells other servers to use encrypted TLS when they deliver mail to your domain, and TLS-RPT asks them to report when that fails. Both protect the mail you receive. Inbox providers judge the mail you send on SPF, DKIM, DMARC, reputation and content, so these two records raise your security score without changing inbox placement.
Yes. The scanner looks up records at the exact name you enter, so entering mail.yourdomain.com checks SPF at mail.yourdomain.com and DMARC at _dmarc.mail.yourdomain.com. A subdomain with no DMARC record of its own is still covered by the parent domain's policy at receiving servers, but the scan will report DMARC as missing.
Scan after every DNS change, after adding a new sending tool that needs its own SPF include or DKIM key, and before launching a campaign from a new domain. DNS changes can take from a few minutes to a few hours to show up, so rescan if a record you just added is not found yet.
Inboxkit sets up the mailboxes and DNS records your cold email domains need.