Part of this record is behind a macro
NOTEWhat it means
The term the offending value expands to a different name for every sending server, so the rest of the chain cannot be read from DNS alone. The lookup count shown is what we could reach, not the total, and the real cost depends on who is sending.
How to fix it
Nothing to change if this is your provider’s design, which it usually is. To see what the record really costs, check a specific sending address against it: the evaluation follows the macro the way a receiver does.
Check your own domain
This page describes the condition. To find out whether your domain has it, run the SPF test or the full checkup, which examines every record at once.
Understand it properly
This page covers one condition. For the whole picture, What is SPF, and the ten-lookup limit, or start at the Health Library.
Where this comes from
We judge this against RFC 7208 section 7. Every finding on this site cites the specification behind it so you can check the work rather than take our word for it.
Other SPF conditions
SPF_MACRO_CHAIN_HIDDEN
Every fix on this site is yours to implement. If you would rather someone did it, I take this work directly.