SPF Record Checker
Look up and validate a domain's SPF record. The checker finds the v=spf1 TXT record, checks the syntax and the all mechanism, detects duplicate records, recursively resolves every include and redirect, and counts DNS lookups against SPF's hard limit of 10.
Enter a domain and we query its TXT records over DNS-over-HTTPS, parse the SPF record, and walk each include: and redirect= to count the DNS-querying mechanisms. Exceeding 10 lookups, having two SPF records, or ending with +all or ?all are flagged as failures, with the exact fix.
Instant Results
Live checks in seconds
Nothing Stored
No logs of what you check
No Sign-Up
Free, no credits or email
What Does SPF Record Checker Do & How Does It Work?
Enter a domain and we query its TXT records over DNS-over-HTTPS, parse the SPF record, and walk each include: and redirect= to count the DNS-querying mechanisms. Exceeding 10 lookups, having two SPF records, or ending with +all or ?all are flagged as failures, with the exact fix.
How to Use SPF Record Checker (Step-by-Step)
- 1Enter your domain.
- 2Check the record and the findings.
- 3Look at the include tree and lookup count.
- 4Fix errors in your DNS, then re-check.
The SPF rules that break most often
Only one SPF record is allowed — a second one makes SPF fail with a PermError. Evaluation may use at most 10 DNS lookups (include, a, mx, ptr, exists, redirect); adding several email providers often exceeds it. The record should end with ~all or -all; +all authorises the whole internet.
SPF checks the envelope sender, not the From address people see — so it only stops spoofing when combined with DMARC.
Fixing too many lookups
Frequently Asked Questions
Should I use ~all or -all?
Both are fine with DMARC enforcing the policy. ~all (soft fail) is the common, safe default; -all is stricter.
Where do I add or edit the SPF record?
In your DNS provider (registrar, Cloudflare, Route 53…) as a TXT record on the root of your domain.
What do you do with the domains and URLs I check?
Our server performs the lookup once and returns the result to your browser. We don't store the addresses you check or build a history. Private and internal addresses are blocked.
Guides & Tutorials
Explore More Free Browser Tools
View All 290+ Tools Directory →All tools run client-side in your browser with zero data uploads, no sign-up, and zero tracking. Discover other popular converters and calculators:
Cryptographic Standards & Zero-Knowledge Privacy Architecture
SPF Record Checker is engineered to strict security and cryptographic specifications — guaranteeing zero data leakage, zero backend telemetry, and audited implementation:
- 1. 100% Zero-Knowledge Client Execution: Passwords, private keys, hashes, and API tokens are computed strictly in your browser's local memory via Web Crypto API (SubtleCrypto) and audited @noble/hashes. Nothing is ever sent to or stored on our servers.
- 2. Official RFC & NIST Compliance: Adheres to established security specifications including RFC 2104 (HMAC), RFC 6238 (TOTP), RFC 9106 (Argon2id), RFC 4122 (UUID v4), and FIPS 180-4 (SHA family).
- 3. Memory-Hard & Brute-Force Resilient: Incorporates robust hashing algorithms (Argon2id, bcrypt, PBKDF2) with configurable memory and iteration costs to defend against GPU-accelerated cracking.
- 4. Transparent & Inspectable: Every cryptographic calculation occurs visibly in client-side JavaScript. You can verify through your browser's Network tab that zero outbound requests are made with your sensitive inputs.
- 5. SSRF-Safe Diagnostic Probing: For internet-facing checks (SSL certificates, DNS records, HTTP security headers), handshakes run through isolated proxies that never log or store queried domains.
Suggest a Feature or Improvement for SPF Record Checker
Need custom options, higher limits, or extra format support? Let our engineering team know!