Skip to content

SPF include has no SPF record

An include in your SPF record points at a name with no SPF record, which gives permerror until you fix the typo or drop the retired service.

Last updated:

What the checker reports

Critical spf.include_no_record

An included domain has no SPF record

The record includes a domain that publishes no v=spf1 record. Receivers return permerror when they reach that include, so SPF fails for every server not matched before it.

How to fix: Check the include against the setup guide of the service it belongs to. Correct the name if it has a typo, or remove the include if you no longer use the service.

What this error means #

An include tells a receiving mail server to check another domain’s SPF record and use its answer. If that domain publishes no SPF record, the receiver has nothing to evaluate. It looks up the TXT records at the name and finds none that begin with v=spf1, or the name doesn’t exist at all, and the check of that domain ends with the result none. RFC 7208 §5.2 turns that result into permerror for your record, so SPF fails.

Processing stops there. Terms on the left of the broken include still decide for the servers they match, because evaluation goes from left to right and a match ends it (RFC 7208 §4.6.2). Mail from a server matched earlier passes. Mail from servers that only match after the broken include, and everything written after it, gets a permerror instead.

Two results are different, and it helps to know which one you have:

  • A DNS timeout or a server failure while looking up the included name gives temperror, a temporary error, and the include passes that on (RFC 7208 §4.4, §5.2). It can clear by itself, so it isn’t this finding.
  • A target that does have a record, but whose evaluation ends in fail, softfail or neutral, just doesn’t match. The include is skipped and the receiver moves to the next term.

Only a missing record, or a record that itself ends in permerror, produces a permerror at the include. Two causes are common for a missing record.

A retired service. You stopped using a mailing tool or a shop platform and kept its include. If its domain no longer publishes SPF, the include now points at nothing.

A typo in the name. One wrong letter in spf.mailr.example points the include at a name nobody publishes. Receivers check SPF when a message arrives (RFC 7208 §2.2), so nothing flags the mistake when you publish it.

How receivers treat it #

Standard: RFC 7208 §5.2

Only the evaluated result of the referenced SPF record is used, rather than literally including the mechanisms of the referenced record in the first.

The table in that section lists what each result of the included check does to the include term. A pass is a match, fail, softfail and neutral don’t match, temperror stays temperror, and both permerror and none return permerror.

A permerror means the domain’s published records couldn’t be correctly interpreted, and RFC 7208 §2.6.7 says it definitely requires DNS operator intervention. What a receiver does next is its own local policy (§4.2). If it rejects the message during the SMTP conversation, §8.7 says it should use reply code 550 with, if supported, the enhanced status code 5.5.2.

DMARC treats it as no SPF pass. RFC 9989, which replaced RFC 7489 in May 2026, only treats a domain as an SPF-authenticated identifier when SPF passes (§4.10.2), so a permerror gives DMARC nothing to align. Mail can still pass DMARC through an aligned DKIM signature (§5.3.5).

Broken and fixed record #

dead-include.zone
example.com.  TXT  "v=spf1 ip4:192.0.2.10 include:spf.mailr.example include:spf.oldshop.example include:spf.helpdesk.example ~all"

Two of the three includes in this record are broken. spf.mailr.example is a typo for spf.mailer.example. spf.oldshop.example belonged to a shop platform that was cancelled, and its domain no longer publishes an SPF record. Mail from 192.0.2.10 still passes, because the ip4 term on the left matches first. Mail through the mailing tool and the help desk fails.

live-include.zone
example.com.  TXT  "v=spf1 ip4:192.0.2.10 include:spf.mailer.example include:spf.helpdesk.example ~all"

The typo is corrected, the cancelled service’s include is gone, and the working one is unchanged.

How to fix it #

  1. List every include: in your record, then look up the TXT records at each included name with any DNS lookup tool. A working include returns a record that starts with v=spf1, because that’s the only kind a receiver keeps (RFC 7208 §4.5).
  2. The one that returns no v=spf1 record, or an NXDOMAIN error, is the broken include.
  3. Compare its spelling with the service’s own setup guide. If the guide gives a different name, use the guide’s.
  4. If you no longer use the service, delete the include. Make sure none of your own mail still goes out through it first.
  5. Publish the corrected record, then run the SPF Record Checker and confirm the include now resolves.

Check your domain

Records look right? Check the list next.

Kavik.email checks every address on your list, so what you send reaches real inboxes.