Fill the Server: 80% off your first 4 monthly invoices, monthly billing. Ends Nov 30, 2026. 25 spots in this batch.FILL25
Fill the Server, annual: about 29.63% off your first annual invoice. Ends Nov 30, 2026.FILL25Y
Fill the Server, 2 year term: about 15.69% off your first biennial invoice. Ends Nov 30, 2026.FILL25B
Fill the Server, 3 year term: about 11.11% off your first triennial invoice. Ends Nov 30, 2026.FILL25T
80% off your first 3 months, monthly billing. Ends Dec 25, 2027.3MONTHS80
50% off your first annual Shared term. Ends Dec 31, 2027.50SHARED
Shared Starter, 3 year term: C$105.84 total.MOOSE294
20% off your first 3 monthly VPS invoices. Ends Dec 31, 2027.20VPS3
25% off your first annual base VPS term.25VPS

← All guides

Email & DNS

SPF lookup limits: avoid permerror from too many DNS-dependent mechanisms

Published August 2026 · 2 min read · Updated 2026-09-05

SPF evaluation has a limit on DNS-querying mechanisms so one sender policy cannot trigger unbounded recursive work. A record can look syntactically valid yet produce PermError when include, a, mx, ptr, exists, or redirect processing exceeds the lookup budget.

Count mechanisms that cause DNS lookups

Inspect the published SPF record and recursively expand includes/redirects from every legitimate sending provider. ip4 and ip6 mechanisms do not consume DNS lookups in the same way, while include and nested provider records often do.

Provider records can change later, so a policy near the limit has little safety margin.

Do not publish multiple SPF records

A domain should have one SPF TXT policy at a given name. Adding a second record for a new service is not additive; receivers can treat multiple policies as an error.

Combine legitimate senders into one policy while staying within syntax and lookup limits.

Remove senders you no longer use

Old newsletter, CRM, support, invoice, website, and marketing services are common sources of unnecessary includes. Confirm ownership before removal so legitimate mail is not broken.

Flattening provider IPs manually can reduce lookup count but creates maintenance risk when providers change infrastructure; use it only with a reliable update process.

Validate with representative mail

Run an SPF parser/validator, then send through every legitimate source and inspect Authentication-Results. DMARC alignment still depends on the visible From domain and is not guaranteed by SPF pass alone.

  • Recursively count DNS mechanisms.
  • Maintain one SPF record.
  • Remove obsolete senders.
  • Test every real sending source.

Next step

Count SPF DNS lookups across includes, redirects and other mechanisms, then simplify the policy without authorizing senders the domain does not use.

Explore DotMoose domains and DNS

Keep reading

Related guides.

CAA record planning: control which certificate authorities may issue for a domain

Plan CAA records around the certificate providers you use, subdomains and incident contacts, then verify issuance will still work before enforcing restrictions.

Read the guide

CNAME chain problems: why extra DNS aliases can break or slow resolution

Trace CNAME chains, loops, missing terminal records and provider restrictions, then shorten unnecessary aliases without changing the intended hostname.

Read the guide

DKIM selector rotation: change signing keys without breaking verification

Rotate DKIM selectors by publishing the new key first, switching signers, monitoring authentication and retaining the old selector long enough for queued mail.

Read the guide

More domains & dns guides

We will handle the move. You check it first.

Your current site stays online until your new one is ready. You approve the copy first, and if anything is not right we switch you back right away. The price you pick is the price you renew at.

Start my free moveSee plans and prices
See pricesFree move