SPF checker report
SPF report for laravel.com
We explain exactly why your SPF uses 3 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.
Executive summary
The full story for laravel.com in one glance.
Current situation
- Risk Low
- Lookup count 3 / 10
- Providers detected Google Workspace, Mailchimp
- Maintenance Manual updates expected
After SPF Manager
- Risk None
- Lookup count 1 / 10
- Providers Synchronized automatically
- DNS change One TXT record to publish
SPF Health 90 → 100 · Lookups 3 → 1
Monitor laravel.comCurrent vs future
See what changes when laravel.com moves to one managed include.
Current situation
- Health score
- 90 / 100
- Lookup count
- 3 / 10
- Detected providers
- Google Workspace Other Mailchimp
- Risk
- LOW
After SPF Manager
- Health score
- 100 / 100
- Lookup count
- 1 / 10
- Providers
- Automatically managed
- Risk
- NONE
Estimated operational impact
Indicative savings based on provider complexity and your current SPF structure.
These estimates are based on provider complexity and detected SPF structure. They are indicative, not guaranteed.
Estimated provider changes
~6 / year
Estimated manual DNS edits
~9 / year
Estimated time saved
~12h / year
Estimated risk reduction
~10%
SPF Health
3 / 10 DNS lookups
Estimated with SPF Manager
100 / 100
- 95–100 Healthy
- 80–94 Good
- 60–79 Needs attention
- 40–59 High risk
- 0–39 Critical
Include depth: 3
Why this matters
Google Workspace contributes 1 lookup. Other contributes 1 lookup. Mailchimp contributes 1 lookup. Total: 3 / 10 lookups.
Detected sources
Why fix this today
- Your SPF record uses 3 of 10 DNS lookups — complexity adds maintenance risk.
- Provider SPF records change without notice — your DNS may fall behind.
- Manual updates become risky when several providers depend on the same record.
Simulate next provider change
SPF risk is not static. The next provider update can push you over the limit — unless changes are synchronized automatically.
Current chain
3 / 10
After simulated change
4 / 10 lookups
One step closer to the lookup limit.
With SPF Manager
1 / 10
Provider changes are detected, validated, and folded into your managed include — your public DNS stays one record.
Specific actions for this domain
-
Replace nested includes
Include depth is 3. Nested provider chains increase permerror risk and make troubleshooting harder.
-
Switch to a managed include
Publish one managed include in DNS and let SPF Manager resolve provider includes behind it.
LARAVEL.COM looks healthy today. Monitor lookup usage and provider changes so new tools do not silently push you toward the limit.
Monitor laravel.comSafe, validated SPF changes
Replacing a DNS record feels risky. SPF Manager is designed to keep you in control.
- RFC-aware validation
- One DNS record under your control
- No direct DNS write access required
- Original SPF remains visible in history
- Reversible migration path
- Provider changes synchronized automatically
How the 3 lookups are counted
RFC 7208 counts one DNS lookup for each include, redirect, a, mx, ptr, and exists mechanism evaluated — including nested chains.
3 / 10 used
-
1
include
_spf.google.comCounted toward Google Workspace
-
2
include
helpscoutemail.comCounted toward Other
-
3
include
servers.mcsv.netCounted toward Mailchimp
Each row is one DNS lookup consumed while evaluating your SPF record. The segments above sum to 3.
All SPF includes
Expand each source to see include records, lookup contribution, nesting depth, and guidance.
-
include:_spf.google.comdepth 1 1 lookup
Recommendation: keep authorized, but monitor for nested include changes.
Managed automatically with SPF Manager
-
include:helpscoutemail.comdepth 1 1 lookup
Recommendation: keep authorized, but monitor for nested include changes.
Managed automatically with SPF Manager
-
include:servers.mcsv.netdepth 1 1 lookup
Recommendation: keep authorized, but monitor for nested include changes.
Managed automatically with SPF Manager
Could this have been prevented?
Manual SPF maintenance repeats the same risky work. SPF Manager synchronizes provider changes automatically.
Manual SPF today
- Microsoft changes SPF → manual DNS update !
- Google changes SPF → manual DNS update !
- Mailchimp changes SPF → manual DNS update !
- Salesforce changes SPF → manual DNS update !
With SPF Manager
- Provider change detected
- SPF output validated
- Managed include synchronized
- Your DNS stays unchanged
How your SPF chain becomes one include
Watch nested provider includes collapse into a single managed include.
Your DNS today
TXT @ laravel.com
v=spf1 include:… +3 includes
3 / 10 lookups
Google Workspace
include:_spf.google.com
Other
Otherinclude:helpscoutemail.com
Mailchimp
include:servers.mcsv.net
With SPF Manager
TXT @ laravel.com
v=spf1 include:laravel.com.flat-spf.com -all
1 / 10 lookups
Managed include
laravel.com.flat-spf.com
Resolves 3 providers automatically
Generate managed SPF for laravel.com
One managed include resolves your provider chain and keeps changes synchronized automatically.
Generate managed SPF for laravel.comFix laravel.com in minutes
Generate a managed SPF include for laravel.com and keep provider changes synchronized automatically — setup takes just a few minutes.
SPF Health 90 → 100 · Lookups 3 → 1
Fix laravel.com in minutesNo credit card required. You stay in control of your DNS records.
Share this report
Share this report with a client, colleague, or DNS administrator before making changes.
Email authentication platform
SPF is live today. Additional modules will plug into the same report experience.
Included in this report
Expands your deliverability coverage
Expands your deliverability coverage
Expands your deliverability coverage
Expands your deliverability coverage
Analyzed 1 hour ago.