SPF Dependency Visualizer
Explore the SPF dependency tree and see where third-party email services enter your policy.
Run a diagnostic
The analysis script has not loaded. If the button stays disabled, reload the page and check JavaScript or caching settings.
Email headers stay in your browser. Public DNS results may be cached for 5 minutes. Public DNS TXT checks may use Google Public DNS when the server resolver returns no TXT records. Email headers are not sent to that DNS service.
How to use and interpret this tool
Enter a sending domain to inspect its SPF TXT policy and the include or redirect mechanisms it references. The dependency tree explains which third-party policies may be evaluated when a message is sent.
How to read the findings
SPF permits at most ten DNS-querying mechanisms and modifiers during an individual evaluation, not simply ten visible include statements. The actual path depends on the sender's IP, record order and nested rules.
Limitations and next steps
This is a static configuration map, not a simulation of every possible sending IP. Avoid replacing includes or flattening records without checking address changes and the services that really send your mail.
Need continuous authentication protection?
Method and limitations
Map SPF include and redirect dependencies, locate missing records and assess potential DNS lookup-limit risks. Public DNS checks cannot prove inbox delivery or message-level authentication.
Frequently asked questions
Is the dependency count the official SPF lookup count?
Not exactly. SPF evaluates mechanisms per message and path; this visualization is a static approximation for remediation.
Does a large SPF tree always exceed ten lookups?
Not necessarily. The limit applies to the DNS-querying mechanisms reached along an actual evaluation path.
Educational diagnostics, not a guarantee of deliverability or provider approval.