Fail

Your SPF record needs more than 10 DNS lookups

The short version

Remove includes you don't use, or replace some with ip4 and ip6 ranges.

What it means

Checking your SPF record takes more than 10 DNS lookups. Every include, a, mx, ptr, exists and redirect costs one lookup, and so do the includes inside the records you include. A typical Google Workspace include alone uses four. The SPF standard sets 10 as the hard limit.

Why it matters

When a receiver reaches the eleventh lookup it stops and returns a permanent error. Your SPF record then fails for every message, even mail from servers you listed, and DMARC treats SPF as failed. The record looks fine to the eye, which is why this problem often goes unnoticed for months.

How to fix it

  1. Open the include tree in the result to see which includes cost the most.
  2. Remove includes for services you no longer use. Old newsletter tools and trial accounts are the usual culprits.
  3. For a service that sends from a few fixed addresses you control, replace its include with ip4: or ip6: entries.
  4. Move bulk mail (newsletters, marketing) to a subdomain such as news.example.com with its own SPF record.
  5. Rebuild and recount in the SPF builder before you publish.

We don't generate flattened records that copy every provider's addresses into yours: providers change their addresses without notice and a flattened copy then breaks silently.

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. The lookup count should read 10 or fewer.