SPF record monitoring
DoubleCheck reads the SPF record of your domain every day and alerts you when it disappears, becomes invalid or no longer rejects unauthorised senders.
The problem
An SPF record lists the servers that may send mail for your domain. It is edited by hand in DNS, and it changes every time you add or drop a mail service: a newsletter tool, a helpdesk, a new mail provider.
Each of those changes can break it without an error message. A second record, a typo, or one include too many makes receivers ignore the whole record, and your mail starts to land in spam.
Why it matters
Without a working SPF record, anyone can send mail that looks like it comes from your domain, and receivers have little reason to trust the mail you send yourself.
SPF is limited to 10 DNS lookups. Every include, a, mx and redirect counts, and the lookups of the services you include count as well. Going over the limit is a permanent error for the receiver.
Large mail receivers expect sender authentication from bulk senders. SPF is one of the three records they look at, together with DKIM and DMARC.
How to check it manually
Look up the SPF record of a domain with dig or nslookup:
dig +short TXT example.com
nslookup -type=TXT example.com
Look for the one record that starts with v=spf1. Then count the include, a, mx, ptr, exists and redirect terms, and those of every included record. That is slow to do by hand, and it is out of date the day someone changes the record.
How DoubleCheck checks it
DoubleCheck reads the record once a day, follows the includes and redirects and counts the DNS lookups. It reports the result in plain words, such as "SPF ends in ~all (softfail); use -all to reject unauthorised senders".
A missing record, a second record, more than 10 lookups and +all are errors. ~all, ?all and a record without an all term are warnings. If you consciously keep ~all, choose to accept soft fail and ~all is OK. When DNS does not answer, the result is unknown and you get no alert: a resolver problem is not a problem with your domain.
- Measures
- A DNS TXT lookup of your domain. DoubleCheck reads the SPF record, follows its include and redirect terms and counts the DNS lookups the way a receiving mail server does.
- Runs
- Once a day. The interval is the same for every domain check: what it reads rarely changes.
- Status
-
- OK when the record ends in -all, or in ~all when you accepted soft fail.
- Warning when it ends in ~all (unless accepted) or ?all, or has no all term, so unlisted senders are not rejected.
- Error when there is no SPF record, more than one, or the record is invalid (for example more than 10 DNS lookups).
- Error when the record ends in +all, which lets every server send for your domain.
- Unknown, and no alert, when DNS itself does not answer.
- Options
-
- Required SPF policy: -all (hard fail) by default. Choose "-all or ~all" to accept soft fail.
All of it in one report
Want to see this next to the rest of the mail setup of a domain? The e-mail health report reads MX, SPF, DKIM, DMARC, blacklists, name servers and the domain registration at once and gives you a PDF with findings and advice, for €0.20.
Frequently asked questions
Is ~all not good enough?
~all (softfail) tells receivers that other senders are suspicious, but does not tell them to reject the mail. It is the usual starting point while you are still collecting your senders. The warning reminds you to move to -all once the list is complete. If you keep ~all on purpose, accept soft fail in the options of the check.
Which domain do I enter?
The domain you send mail from, for example example.com. A web address is accepted too, and DoubleCheck uses the domain from it. An IP address is not.
Does the domain need a website or an A record?
No. The check only looks up a TXT record, so a domain that only sends mail works fine.
Why is this check only daily?
SPF changes when someone edits DNS, which is rare. Once a day finds a broken record in time, and it keeps the cost of the check low.
Start monitoring with DoubleCheck
Start with €5 of free credit, no credit card required. Alerts by email, SMS, Slack, Microsoft Teams or Discord.