What this tool shows
Enter a domain name and see its SPF (Sender Policy Framework) record, broken down into its individual mechanisms — which servers and services are authorized to send mail on the domain's behalf — along with warnings about common configuration problems.
A real, verified example
Looking up a domain with a real SPF record returns its mechanisms parsed individually (for example, an include: mechanism naming another domain's own SPF record, and the final all mechanism) and a DNS-lookup count toward SPF's own limit — confirmed by running this exact tool's own parsing logic against a real, representative DNS response.
SPF alone does not guarantee deliverability
A valid, well-formed SPF record is one input among several a receiving mail server considers (alongside DKIM, DMARC, sender reputation, and its own spam filtering) — it does not by itself guarantee that mail from this domain will be delivered, or that mail failing an SPF check will necessarily be rejected. Treat this tool as a diagnostic for your domain's own SPF configuration, not a deliverability guarantee.
The 10-DNS-lookup count is an approximation
SPF evaluation fails outright ("permerror") if checking a record requires more than 10 DNS lookups in total, per the SPF standard. This tool counts the lookup-consuming mechanisms (a, mx, include:, exists:, redirect) in your domain's own top-level record, but does not recursively follow each include: into its own target's SPF record to count lookups nested further down. This means the real total for a domain with deep include chains can be higher than the number shown here — the count is always presented as an approximation, not an exact RFC 7208 evaluation.
Multiple SPF records are flagged as a real problem
A domain should publish at most one SPF record. If more than one is found, that's flagged explicitly: multiple SPF records cause unpredictable evaluation by receiving mail servers, and is a genuine misconfiguration worth fixing, not a tool error.
No SPF record is a real, meaningful result
A domain can be valid and simply not publish an SPF record at all — shown plainly as "no SPF record found," not an error.
Privacy
The domain you enter is sent to our server, which queries DNS on your behalf. Nothing you look up is stored or logged beyond the immediate request.