SPF report
nos.nl
1 / 10 DNS lookups
Free for one domain. No credit card.
SPF Health
1 / 10 DNS lookups
- 95–100 Healthy
- 80–94 Good
- 60–79 Needs attention
- 40–59 High risk
- 0–39 Critical
Include depth: 1
Estimated with SPF Manager
100 / 100 · 1 / 10 lookups
This record uses
1
of 10
DNS lookups
SPF Lookup Limit: The 10 DNS Lookup Rule
RFC 7208 limits SPF evaluation to ten DNS lookups, and exceeding that limit causes a PermError that breaks authentication.
Read article
SPF Lookup Limit: The 10 DNS Lookup Rule
RFC 7208 limits SPF evaluation to ten DNS lookups, and exceeding that limit causes a PermError that breaks authentication.
Read article%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email contributes 1 lookup. Total: 1 / 10 lookups.
Detected sources
What we found
2 things worth knowing about this record, most serious first.
-
High
Record too long for DNS
A single DNS TXT string may not exceed 255 characters, and oversized responses can be truncated in transit. The TXT records on this domain total 729 bytes, which risks truncation.
Read more about this → -
Note
Macro in use
The mechanism include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email uses an SPF macro. Macros are evaluated per message and cannot be flattened, so this lookup stays even after flattening.
Read more about this →
How the 1 lookups are counted
RFC 7208 counts one DNS lookup for each include, redirect, a, mx, ptr, and exists mechanism evaluated — including nested chains.
1 / 10 used
-
1
include
%{i}._ip.%{h}._ehlo.%{d}._spf.vali.emailCounted toward %{i}._ip.%{h}._ehlo.%{d}._spf.vali.email
Each row is one DNS lookup consumed while evaluating your SPF record. The segments above sum to 1.
What if you changed something
Turn a sender off to see what removing it would free up, or add one to see how close it takes you to the limit. Nothing here changes your DNS — it is arithmetic on the numbers above.
Lookups in that scenario
/
With SPF Manager
/
Unchanged, whatever you add.
Starting point: 1 of 10 lookups as published today.
How your SPF chain becomes one include
See what changes when nos.nl moves to one managed include.
Current situation
- Health score
- 100 / 100
- Lookup count
- 1 / 10
- Detected providers
- %{i}._ip.%{h}._ehlo.%{d}._spf.vali.email
- Risk
- LOW
After SPF Manager
- Health score
- 100 / 100
- Lookup count
- 1 / 10
- Room to grow
- 9 lookups spare
- Providers
- Automatically managed
- Risk
- NONE
Watch the chain collapse
Watch nested provider includes collapse into a single managed include.
Your DNS today
TXT @ nos.nl
v=spf1 include:… +1 includes
1 / 10 lookups
%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email
Unidentifiedinclude:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email
With SPF Manager
TXT @ nos.nl
v=spf1 include:nos.nl.flat-spf.com -all
1 / 10 lookups
Managed include
nos.nl.flat-spf.com
Resolves 1 providers automatically
What changes if you let us manage it
One include, whatever you add
Your record becomes a single include that we host. Adding another provider later changes what resolves behind it, not what you publish, so your own record stops growing toward the 10-lookup limit.
Provider changes are our problem
When a provider quietly starts sending from new addresses — or starts costing more lookups than it used to — we see it and republish. You never find out from a bounce.
Always current, never touched
You publish one TXT record once. From then on the addresses behind it stay correct without you editing DNS again.
Free for one domain. No credit card.
Specific actions for this domain
-
Monitor provider changes
Your SPF is healthy today. Track lookup usage when new email tools are added.
All SPF includes
Expand each source to see include records, lookup contribution, nesting depth, and guidance.
-
include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.emaildepth 1 1 lookup
Recommendation: keep authorized, but monitor for nested include changes.
Managed automatically with SPF Manager
Share this report
Send it to whoever manages your DNS before anything changes.
Analyzed 0 seconds ago.