So what does SPF actually do?
SPF is a TXT record on your domain that lists the servers allowed to send email for it. When your email arrives, the receiving server looks at the IP that connected, checks it against that list, and records a pass or a fail. On its own a fail rarely sinks a message, but together with DMARC it decides whether Gmail and Outlook believe the email is really from you.
What I check
- Exactly one record. Two v=spf1 records count as a permanent error under RFC 7208, and receivers then ignore SPF altogether. It usually happens when someone adds a new tool and publishes a second record instead of editing the first.
- The ten-lookup limit. Every include, a, mx, ptr and exists costs a DNS lookup, and includes inside includes count too. Past ten, SPF fails with a permanent error. I walk the whole tree and give you the real number.
- Void lookups. Terms that point at names that don't exist. More than two and some receivers stop trusting the record.
- The ending. A record that ends in +all lets anyone on the internet send as you. One that is only "v=spf1 ~all" lets no one send, which sounds safe but fails all your own mail.
- Your mailbox provider. If your MX points at Google Workspace or Microsoft 365 and SPF doesn't include them (directly or through a flattening service), mail from your own team fails SPF.
Fixing it
When something is wrong, the report ends with the corrected record. It keeps every include you already have, adds what's missing, and merges duplicates into one, so you can paste it into your DNS as it is.