Free tool
A free email deliverability test for your sending domain. It runs live SPF, DKIM, DMARC, MX and blacklist checks and rolls them into one score from 0 to 10 that tells you whether the domain is ready to send.
Auditing a domain's wider email security, including BIMI, MTA-STS and TLS-RPT? Use the domain scanner instead.
Automate everything
Inboxkit automatically monitors and optimizes your email deliverability across all domains.
Walkthrough
A 43-second walkthrough of the four settings it checks: SPF, DKIM, DMARC and MX. In the demo a domain scores 7 out of 10 because DKIM is missing and DMARC only watches. After adding DKIM and moving DMARC to quarantine, the same domain scores 10.
Step 1
Use the domain in your From address, such as yourdomain.com. A leading https:// or www. is removed.
Step 2
You get a score out of 10, a risk level, a pass or fail for SPF, DKIM, DMARC and MX, the records found and the blacklist result.
Step 3
Publish the suggested records from the Recommendations list at your DNS host, wait for them to propagate, then click New Check.
Five checks, worth 10 points between them. These are the settings inbox providers look at before they read a single word of your email.
| Check | Points | What earns them |
|---|---|---|
| SPF | 3 | 1.5 for a v=spf1 record, 1.5 more when it is valid: only one SPF record, ending in ~all, -all or ?all, and no more than 10 lookup mechanisms. |
| DKIM | 2 | A DKIM key at any of 35 common selectors, covering Google Workspace, Microsoft 365, SendGrid, Mailgun, Mailchimp, Amazon SES, Zoho and generic names such as default and mail. |
| DMARC | 3 | 1.5 for a v=DMARC1 record, 1 more for p=quarantine or p=reject, and 0.5 more when the policy is enforced and a rua= report address is set. |
| MX | 1 | At least one MX record, so replies and bounces have somewhere to go. The mail provider is detected from it. |
| Blacklists | 1 | The IP your domain resolves to is checked against 10 DNS blocklists, including Spamhaus ZEN, SpamCop, Barracuda and SORBS. A listing earns no point and takes half a point off. A domain with no A record skips this check and the point. |
The blacklist check uses the IP your domain's A record points to, which is usually your website host, not the server your mail leaves from. To test a sending IP or a domain against more lists, use the blacklist checker.
8 to 10
Most checks pass and the domain is not listed. Below 10, the recommendations show which points you lost.
4 to 7
A core record is missing or weak, such as no SPF, or no DKIM with DMARC left at p=none. Fix it before a cold campaign.
0 to 3
Several core records are missing, so receivers cannot verify mail from this domain.
Worked example: a domain with a valid SPF record, MX records, a clean blacklist result, no DKIM and DMARC at p=none scores 7. Publishing a DKIM key and moving DMARC to p=quarantine with a rua address brings the same domain to 10.
The SPF and DMARC values match the suggestions the checker gives. Add them as TXT records at your DNS host and replace yourdomain.com with your domain. DKIM records come from your mail provider: Google Workspace gives you one TXT record, Microsoft 365 gives you two CNAME records.
| Gap | Host | Value |
|---|---|---|
| SPF missing (Google Workspace) | @ | v=spf1 include:_spf.google.com ~all |
| SPF missing (Microsoft 365) | @ | v=spf1 include:spf.protection.outlook.com -all |
| DKIM missing (Google Workspace) | google._domainkey | The key from Google Admin, Apps, Gmail, Authenticate email |
| DKIM missing (Microsoft 365) | selector1._domainkey | CNAME target shown in the Microsoft 365 DKIM settings. Add selector2 the same way |
| DMARC missing | _dmarc | v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com |
| DMARC at p=none | _dmarc | v=DMARC1; p=quarantine; rua=mailto:dmarc@yourdomain.com |
Keep one SPF record per domain. A second v=spf1 record makes both invalid, so add new senders as extra include: entries in the record you already have. Start DMARC at p=none while you read the reports, then move to p=quarantine once every sender passes. The DMARC generator builds the record for you.
A perfect score means receivers can verify your domain. It does not mean every email reaches the inbox. Placement also depends on sending reputation, built by warming up new mailboxes and keeping bounce and complaint rates low, and on the content of each email. An inbox placement test measures where a real send lands. Run drafts through the spam checker and follow the domain warmup guide before you scale volume.
Related
Validate your SPF records and ensure proper email authentication.
Verify DKIM signatures and public key configuration.
Analyze DMARC policies and email authentication alignment.
Complete DNS record validation for email authentication.
Seven-record email security scan, including BIMI, MTA-STS and TLS-RPT.
Check your domain and IP reputation across major providers.
FAQ
It is a rating of how ready a domain is to send email. This checker rates your domain from 0 to 10 using five things inbox providers look at before they read a message: SPF, DKIM, DMARC, MX records and whether the domain's IP is on a blocklist. A higher score means fewer setup reasons for mail to be filtered.
SPF is worth 3 points, DKIM 2, DMARC 3, MX 1 and a clean blacklist result 1, for 10 in total. SPF and DMARC earn part of their points for existing and the rest for being set up correctly: one valid SPF record, and a DMARC policy of quarantine or reject with a report address. The total is rounded to a whole number.
8 to 10 is low risk, 4 to 7 is medium risk and 0 to 3 is high risk. For cold email, aim for 10 before you send: that needs a valid SPF record, a DKIM key, DMARC at quarantine or reject with a rua address, MX records and no blacklist listings.
It is a domain-level deliverability test. It checks the DNS setup and blacklist status that decide whether receivers trust your domain, without sending an email. It does not measure inbox placement for a specific message or score your content. Use a spam checker on the email itself and an inbox placement test with seed mailboxes for those.
It checks 10 DNS blocklists, including Spamhaus ZEN, SpamCop, Barracuda and three SORBS lists, against the IP address your domain's A record points to. That is usually your website host. If your mail goes out through Google Workspace, Microsoft 365 or a sending platform, check those sending IPs separately with a blacklist checker.
It looks for a DKIM key at 35 common selectors. If your provider uses a custom selector, it will not be found. Open a sent email, find the s= value in the DKIM-Signature header, and check that selector with the DKIM checker. If the key exists there, your DKIM is working even though this score counts it as missing.
A p=none policy only monitors. Receivers still deliver mail that fails authentication, so it gives no protection against spoofing. The checker gives 1.5 of the 3 DMARC points for any DMARC record, 1 more when the policy is quarantine or reject, and the last 0.5 when that policy also has a rua report address.
The deliverability score answers one question: is this domain ready to send? It validates SPF, DKIM, DMARC and MX in depth and adds a blacklist check. The domain scanner is a broader email security scan of seven records, including BIMI, MTA-STS and TLS-RPT, with no blacklist check. Run the deliverability score before a campaign and the domain scanner for a full security audit.
Work through the recommendations under your score. Each one explains what is missing, and missing SPF and DMARC records come with a suggested record to publish. Keep a single SPF record, publish the DKIM key your provider gives you, and move DMARC from p=none to p=quarantine once your reports look clean. Run the check again after the DNS changes propagate.
Get started
Inboxkit sets up the mailboxes and DNS records your cold email domains need.