An SPF, DKIM and DMARC checker looks up the DNS records that say which servers may send mail for your domain and what a receiver should do when a message fails. The tool is the easy part. The hard part is reading the result: an SPF softfail means the domain owner believes the sender is probably not authorised but has not published a hard fail, a permerror usually means the record has too many lookups, and a DMARC policy of none asks receivers to take no action. Below are four checkers and what each page says it covers, then each result in plain words.
The tools were read from their own pages on 2026-11-15, and the standards were read from the RFC Editor on the same day. If you are looking at one particular failure, the pages on SPF softfail, DMARC fail and DKIM fail in Gmail go further. The records themselves are walked through in SPF, DKIM and DMARC for cold email.
Four checkers and what their pages say
| Checker | Covers | How you use it | Limits and notes stated |
|---|---|---|---|
| MXToolbox SuperTool | SPF, DKIM and DMARC lookups, among many other DNS commands | Enter a domain and pick the command | None stated on the page |
| Google Admin Toolbox, Check MX | MX and SPF records; an optional DKIM selector field | Enter a domain, and a selector if you want DKIM checked | None stated; the page does not mention DMARC |
| dmarcian DMARC Inspector | The DMARC record only: whether one exists, syntax errors, a legend for each tag. SPF and DKIM are separate tools in its menu | Enter a domain | Says it does not store what you enter |
| Mail-Tester | Analyses a message, your mail server and your sending IP, and scores it out of 10 using SpamAssassin | Send an email to the address it shows you | Its FAQ limits use to 3 tests in 24 hours; more tests are sold in packs |
The first three look at DNS records for a domain. Mail-Tester works the other way: it looks at a real message you send it. That difference matters, because a record can be correct while the message you actually send is signed by a different domain. Use a record checker first, then a message test.
Reading SPF
SPF is a list in DNS of the servers allowed to send for your domain. The standard is RFC 7208. A checker returns one of these.
- Pass: the sending server is on the list.
- Softfail: RFC 7208 section 8.5 describes it as the domain owner believing the host is not authorised, without committing to a hard fail, and says receivers should not reject on that result alone. A record that ends in ~all produces it. If your own mail shows softfail, the record is missing a sender you use.
- Permerror: section 2.6.7 says the published records could not be correctly interpreted. One cause to check first is the limit in section 4.6.4: implementations must limit the terms that cause DNS lookups to 10, and going over the limit gives a permerror.
An example of how the limit is reached. Suppose your record has seven include terms for your mail host, a newsletter service, a CRM, a helpdesk, a billing tool, a scheduling tool and a survey tool. Suppose two of those includes contain three more includes each. Seven plus six is 13 lookups, which is over 10. Nothing looks wrong on the page, and the check fails. The fix is to remove senders you no longer use, not to add another record.
Reading DKIM
DKIM signs each message with a key whose public half sits in DNS under a name called a selector. A checker that asks for a selector, as Google's does, needs the right one, and the selector is in the DKIM-Signature header of a real message, in the s= tag. A not-found result may only mean you typed the wrong selector. Google's sender guidelines (read on 2026-11-15) say DKIM keys must be at least 1024 bits. The pass you want is a signature that verifies and whose domain matches the domain in your From address.
Reading DMARC
DMARC ties the From address to SPF and DKIM. Its current standard is RFC 9989, published in May 2026, which replaced RFC 7489. Section 5.3.5 says a message passes when one or more of its authenticated identifiers (the SPF or DKIM domain that passed) aligns with the From domain. The record's p tag (section 4.7) says what the domain owner wants done with failures: none means the owner offers no expression of preference, quarantine means it considers the mail suspicious (the spam folder, for example), and reject means it treats the failure as a clear sign the domain is being misused. Alignment can be relaxed, where the two share an organizational domain, or strict, where they must be identical (section 3.2.10).
A policy of none is a valid record and the usual starting point, because it lets you collect reports before you enforce anything; RFC 9989 calls p=none with reports coming in monitoring mode (section 3.2.12). A checker that flags p=none is telling you the domain is monitored and not protected.
Which results matter for sending
Google's sender guidelines (read on 2026-11-15) require all senders to set up SPF or DKIM, and require senders of more than 5,000 messages a day to personal Gmail accounts to set up SPF, DKIM and DMARC, with the DMARC policy allowed to be none and the From domain aligned. If you send through your own Gmail or Google Workspace address on your own domain, the setup is on your domain, and the checkers above will show whether Google's records are published. If a result is wrong, fix the DNS record and test again; DNS changes can take time to reach receivers.
A short routine
- Run the domain through a record checker for SPF and DMARC, and DKIM with the selector from a real message.
- Fix any permerror or missing sender first, because it is the one that breaks.
- Send a message to a test inbox and read its headers for spf, dkim and dmarc results.
- Move DMARC from none only after reports show your real mail passing.
- Check again after any change of mail host or any new tool that sends for you.
A passing record is not a promise of inbox placement. It removes one reason for a receiver to distrust you, and the rest is the list, the message and the volume. The plans for sending from your own Gmail are on the pricing page.
Rocketship finds buyers and emails them from your own Gmail, from $12 a month with a 7-day trial that requires a card.