Fail

An include in your SPF record is broken

The short version

Fix or remove the include; the detail names it.

What it means

One of the includes (or the redirect) in your SPF record points at a name that doesn't work: the name doesn't exist, it has no SPF record, it has two, its record has a syntax error, or it loops back to a record already being checked. The finding's detail names the include and what is wrong with it.

Why it matters

A receiver that follows a broken include stops and returns a permanent error, so SPF fails for every message from your domain, not just mail from that service. It often happens after a provider renames its include or after a typo in a setup guide is copied as is.

How to fix it

  1. Find the include named in the detail and check it against the provider's current setup guide. Providers sometimes move to a new include name, such as a new _spf subdomain.
  2. If you no longer use the service, remove the include.
  3. If the include points at another domain of yours, fix that domain's SPF record first.
  4. Check the result in the SPF builder, then update your TXT record.

Cloudflare

Open the domain, go to DNS then Records, and edit the TXT record whose content starts with v=spf1. Save, and keep the proxy setting off; TXT records are never proxied.

Other DNS hosts

Open the DNS settings for the domain, find the TXT record for the root of the domain (shown as @ or left blank), and edit its value. Don't add a second TXT record that starts with v=spf1.

Check it worked

Run the SPF checker or the full email check on your domain. Changes show up once the old record's TTL has passed, usually within an hour. The finding should be gone and the SPF section should show your new record with its lookup count. Every include in the tree should be shown without a broken status.