TROUBLESHOOTING NOTE
Multiple SPF records: how to diagnose and fix the configuration
Updated
A multiple-SPF warning usually means the checked hostname publishes more than one TXT record beginning with v=spf1. It does not mean all TXT records must be removed: verification records and other TXT data can coexist with SPF.
Confirm what is actually published
Run the SPF checker on the hostname used by your sending service. Save the Markdown report and compare it with the DNS provider's record editor. Multiple quoted strings inside a single TXT record are not the same as multiple SPF records.
If the editor and lookup disagree, check which nameservers are authoritative and whether the edited zone is the one in use. Cached answers may temporarily differ.
Plan one policy without losing legitimate senders
Inventory every service sending on behalf of this hostname, including business email, marketing platforms and transactional mail. Follow each provider's current SPF instructions. Have the domain administrator review a single combined policy before replacing competing policies.
Do not simply concatenate two complete v=spf1 records or delete a provider's authorization at random. Preserve unrelated TXT records. Nested includes and redirects need separate evaluation of SPF lookup limits; this tool does not perform that evaluation.
Verify the change with real mail
After the authorized change, rerun the lookup and test messages from every legitimate sending service. Inspect receiver authentication results. A readable static SPF record does not guarantee that a sending IP passes SPF or that mail reaches the inbox.
Reference and scope
IETF RFC 7208: SPF records, selection and lookup limits
This guide explains a diagnostic workflow. Provider-specific configuration and actual messages or browser behavior require separate verification. The linked tools report bounded observations, not a complete audit.