SPF SPF Manager
Check your SPF

SPF checker report

SPF report for bloomstudio.nl

We explain exactly why your SPF uses 13 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
— and how to fix it in minutes.

Your SPF record exceeds the lookup limit

13 lookups were detected. RFC 7208 allows a maximum of 10. Your SPF exceeds the RFC lookup limit of 10. Email delivery may fail without warning when receivers treat the record as permerror.

Protect bloomstudio.nl Why this matters ↓

No credit card required. Generate one managed include for bloomstudio.nl.

Executive summary

The full story for bloomstudio.nl in one glance.

Current situation

  • Risk Medium
  • Lookup count 13 / 10
  • Providers detected None recognized
  • 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 60 → 100 · Lookups 13 → 1

Protect bloomstudio.nl

Current vs future

See what changes when bloomstudio.nl moves to one managed include.

Current situation

Health score
60 / 100
Lookup count
13 / 10
Detected providers
Other
Risk
MEDIUM

After SPF Manager

Health score
100 / 100
Lookup count
1 / 10
Providers
Automatically managed
Risk
NONE
Score potential 60 → 100

Estimated operational impact

Indicative savings based on provider complexity and your current SPF structure.

Estimated

These estimates are based on provider complexity and detected SPF structure. They are indicative, not guaranteed.

Estimated provider changes

~4 / year

Estimated manual DNS edits

~6 / year

Estimated time saved

~8h / year

Estimated risk reduction

~40%

SPF Health

60 / 100
Risk Medium

13 / 10 DNS lookups Over limit

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

Other contributes 7 lookups. Direct mechanisms contributes 6 lookups. Total: 13 / 10 lookups.

Detected sources

Other · 7 lookups Direct mechanisms · 6 lookups

Why fix this today

  • Your SPF record exceeds the lookup limit (13 / 10).
  • Some receivers may already treat SPF as invalid.
  • Removing a provider manually can break legitimate mail flows.

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

13 / 10

Microsoft 365 adds another nested include

After simulated change

11 / 10 lookups

Already exceeded — receivers may treat SPF as invalid.

With SPF Manager

1 / 10

Automatically synchronized

Provider changes are detected, validated, and folded into your managed include — your public DNS stays one record.

Specific actions for this domain

  • Reduce lookup count immediately

    Your record currently uses 13 DNS lookups. RFC 7208 allows a maximum of 10, so receivers may reject the record as invalid.

  • 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.

Reduce lookup sprawl for bloomstudio.nl with a managed SPF include that resolves provider includes automatically and keeps your published record predictable.

Protect bloomstudio.nl

Safe, 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 13 lookups are counted

RFC 7208 counts one DNS lookup for each include, redirect, a, mx, ptr, and exists mechanism evaluated — including nested chains.

13 / 10 used

Other · 7 Direct mechanisms · 6
  1. 1
    a bloomstudio.nl

    Counted toward Direct mechanisms

  2. 2
    mx bloomstudio.nl

    Counted toward Direct mechanisms

  3. 3
    mx bloomstudio.nl

    Counted toward Direct mechanisms

  4. 4
    mx bloomstudio.nl

    Counted toward Direct mechanisms

  5. 5
    mx bloomstudio.nl

    Counted toward Direct mechanisms

  6. 6
    mx bloomstudio.nl

    Counted toward Direct mechanisms

  7. 7
    include spf.web-hosting.com

    Counted toward Other

  8. 8
    include spf1.web-hosting.com Nested

    Counted toward Other · depth 2

  9. 9
    include spf2.web-hosting.com Nested

    Counted toward Other · depth 2

  10. 10
    include spf3.web-hosting.com Nested

    Counted toward Other · depth 2

  11. 11
    include spf4.web-hosting.com Nested

    Counted toward Other · depth 2

  12. 12
    include spf5.web-hosting.com Nested

    Counted toward Other · depth 2

  13. 13
    include spf-shared.jellyfish.systems Nested

    Counted toward Other · depth 2

Each row is one DNS lookup consumed while evaluating your SPF record. The segments above sum to 13.

All SPF includes

Expand each source to see include records, lookup contribution, nesting depth, and guidance.

  • include:spf.web-hosting.com
    depth 1 1 lookup
  • include:spf-shared.jellyfish.systems
    Nested depth 2 1 lookup
  • include:spf1.web-hosting.com
    Nested depth 2 1 lookup
  • include:spf2.web-hosting.com
    Nested depth 2 1 lookup
  • include:spf3.web-hosting.com
    Nested depth 2 1 lookup
  • include:spf4.web-hosting.com
    Nested depth 2 1 lookup
  • include:spf5.web-hosting.com
    Nested depth 2 1 lookup

Recommendation: fold this provider behind one managed include to reduce lookup sprawl.

Managed automatically with SPF Manager

  • a:bloomstudio.nl
    depth 1 6 lookups

Recommendation: fold this provider behind one managed include to reduce lookup sprawl.

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

  1. Microsoft changes SPF → manual DNS update !
  2. Google changes SPF → manual DNS update !
  3. Mailchimp changes SPF → manual DNS update !
  4. Salesforce changes SPF → manual DNS update !

With SPF Manager

  1. Provider change detected
  2. SPF output validated
  3. Managed include synchronized
  4. Your DNS stays unchanged

How your SPF chain becomes one include

Watch nested provider includes collapse into a single managed include.

Before → After

Your DNS today

TXT @ bloomstudio.nl

v=spf1 include:… +8 includes

13 / 10 lookups

Other

Other

include:spf.web-hosting.com

1 lookup

Other

Nested Other

include:spf-shared.jellyfish.systems

1 lookup

Other

Nested Other

include:spf1.web-hosting.com

1 lookup

Other

Nested Other

include:spf2.web-hosting.com

1 lookup

Other

Nested Other

include:spf3.web-hosting.com

1 lookup

Other

Nested Other

include:spf4.web-hosting.com

1 lookup

Other

Nested Other

include:spf5.web-hosting.com

1 lookup

Direct mechanisms

include:bloomstudio.nl

6 lookups

With SPF Manager

TXT @ bloomstudio.nl

v=spf1 include:bloomstudio.nl.flat-spf.com -all

1 / 10 lookups

SPF

Managed include

bloomstudio.nl.flat-spf.com

Resolves 8 providers automatically

Validated · 1 / 10 lookups
Paused — compare your current SPF chain with one managed include side by side. Each provider include consumes DNS lookups toward the 10-lookup limit. Flattening provider includes into one managed record… Your public SPF stays simple — SPF Manager maintains the rest.

Generate managed SPF for bloomstudio.nl

One managed include resolves your provider chain and keeps changes synchronized automatically.

Generate managed SPF for bloomstudio.nl

Fix bloomstudio.nl in minutes

Generate a managed SPF include for bloomstudio.nl and keep provider changes synchronized automatically — setup takes just a few minutes.

SPF Health 60 → 100 · Lookups 13 → 1

Fix bloomstudio.nl in minutes

No 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.

SPF

Included in this report

Analyzed
DKIM

Expands your deliverability coverage

Coming soon
DMARC

Expands your deliverability coverage

Coming soon
MX

Expands your deliverability coverage

Coming soon
DNSSEC

Expands your deliverability coverage

Coming soon

Analyzed 4 hours ago.