New: SalesBlink is now in ChatGPTHow the SPF raw check works
Paste the record text
Copy the SPF value from your DNS provider or a lookup tool and paste it in. Surrounding quotes are stripped automatically; everything else is checked exactly as written.
Review every term
Each mechanism and modifier is explained in evaluation order, with its qualifier, whether it costs a DNS lookup, and any syntax error at that exact position.
Fix and re-check
Findings are listed by severity with concrete fixes. Edit the text and run the check again until the record parses cleanly, then publish a single TXT record.
What this check does and does not tell you
- This tool performs no DNS queries. Include and redirect targets are listed and counted but never contacted, so nested records and live lookup totals are not verified here.
- A syntactically valid record can still fail in production — for example when an included domain is missing or the combined lookup count exceeds the RFC 7208 limit of 10.
- SPF evaluation depends on the sender IP and the envelope MAIL FROM / HELO identity of each message. Static analysis of a record cannot predict a per-message pass or fail.
- A passing SPF setup does not guarantee inbox placement; mailbox providers also weigh engagement, complaint rates, and content.
Related free tools
SPF Record Checker
Check the live SPF record of any domain, including nested includes, lookup counts, and void lookups over real DNS.
Open toolSPF Record Generator
Build a correct SPF record from your sending services with guided inputs, then publish it as a single TXT record.
Open toolDMARC Record Checker
Validate your DMARC policy, alignment modes, and reporting addresses against the current RFC 9989 specification.
Open toolFrequently Asked Questions
What is the difference between the SPF Raw Checker and the SPF Checker?
The SPF Checker looks up a domain’s live DNS records and follows include chains. This raw checker validates text you paste yourself, so it is ideal for reviewing a record before you publish it — but it never expands include or redirect targets because it performs no DNS queries.
Does this tool send my SPF record anywhere?
No. The record is parsed entirely in your browser with the same SPF parser our server-side checker uses. Nothing is uploaded, logged, or stored.
What is the 10 DNS lookup limit?
RFC 7208 limits SPF evaluation to 10 DNS-querying mechanisms and modifiers (include, a, mx, ptr, exists, and redirect). This tool counts the terms in the pasted record only; includes can hide additional lookups, so verify the total with the SPF Checker after publishing.
Should I use -all, ~all, or ?all at the end?
-all (fail) rejects unauthorized senders outright, ~all (softfail) marks them as suspicious, and ?all (neutral) offers no spoofing protection. Most senders start with ~all while they confirm every legitimate source is listed, then move to -all. Never use +all — it authorizes the entire internet to send as your domain.
Why does my record work in the checker but fail in production?
Syntax validity is only one part of SPF. A record can parse perfectly and still fail evaluation because an include target is missing, the 10-lookup limit is exceeded once nested includes are counted, or the sending service uses a different envelope domain. Always validate the published record with a live DNS check too.
Let your AI agent book your next meeting
14-day free trial. No credit card required.