Skip to content
HEED Data Supply
Domain protection • HEED INSIGHTS

SPF Has a Lookup Budget: Audit the Evaluated Path

Adding a sending tool can spend a DNS budget you did not know you were sharing.

01 / Domain protection

What is the SPF lookup limit actually counting?

SPF limits the DNS-lookup terms evaluated during an authentication check. Nested includes matter, and the path taken by a particular sending address matters. Counting vendor names or visible TXT-record words is insufficient. Audit the evaluated path before adding a sender, and distinguish authentication failure from message content or recipient quality.

RFC 7208 limits evaluated lookup-causing terms to ten; exceeding that limit produces permerror. The relevant terms include include, a, mx, ptr, exists and redirect. Literal ip4, ip6 and all mechanisms do not consume that particular term budget. Other DNS and protocol limits still exist.

A short top-level record can hide a long chain of nested includes. Conversely, a mechanism that matches early may stop evaluation before later branches are reached. Inspect the actual sender path with an administrator and retain the result, rather than estimating from the number of tools on the invoice.

Sources: RFC 7208: SPF evaluation limits

02 / Domain protection

How can a new include break an otherwise working path?

Model the terms evaluated for a specific sending IP, including nested lookups, then compare the total with the protocol limit. Test all authorized sender classes because one path may pass while another fails. Treat a hypothetical count as a planning example until it is confirmed against the actual DNS configuration.

Assume a particular nonmatching prefix evaluates eight lookup-causing terms before reaching a new tool’s include. Evaluating that include adds one term and its nested path requires two more. The total is eleven. Under the RFC limit, this evaluated path exceeds the budget; the fact that the visible record contains only a few includes does not rescue it.

This is a constructed path, not a diagnosis of HEED or any vendor. A different sender might match earlier and evaluate fewer terms. Keep a per-sender worksheet so a passing test from one application does not conceal failure for another application using the same domain.

Hypothetical evaluated path for one sender
ComponentLookup-causing termsRunning total
Existing evaluated prefix88
New include itself19
Nested evaluated terms211
Protocol comparisonMaximum 10Over limit

Sources: RFC 7208: SPF evaluation limits

03 / Domain protection

What should the change review include?

Inventory authorized senders, identify obsolete entries, and have the domain administrator validate each evaluated path before changing SPF. Preserve a rollback record and inspect authentication on actual test messages. Passing SPF is one configuration result; it does not guarantee inbox placement, repair a poor audience, or authorize an outreach campaign.

Record the current DNS value, sender purpose, owner and observed authentication results. Remove an entry only after its owner confirms it is no longer required. Do not flatten provider-managed includes into copied IP lists without an ongoing maintenance plan; addresses can change and stale authorization can create a different failure.

After the approved change, verify representative messages from every authorized sending class. Compare the expected envelope identity with observed results and record the time. Keep contact quality work separate: a correctly authenticated message can still reach an irrelevant recipient, and an excellent audience cannot fix broken authentication.

  • Count the evaluated path, including nested terms.
  • Validate all required sender classes, not one convenient message.
  • Keep DNS ownership and rollback information with the change ticket.

Sources: RFC 7208: SPF evaluation limits · HEED B2B research scope

Define a B2B research briefSpecify the audience, required fields and exclusions before choosing a batch.

QUESTIONS

Common questions

Does one include equal one total DNS lookup?

The include itself consumes a lookup-causing term, and evaluating its referenced policy can consume more. Inspect the actual nested evaluation rather than counting top-level includes alone.

Will fixing SPF guarantee delivery?

No. Authentication is only one part of message handling. Receiver policy, reputation, content, recipient expectations and other factors still matter.

Sources

  1. RFC 7208: SPF evaluation limits
  2. HEED B2B research scope
KEEP READING