DIAGNOSTIC PLAYBOOK
Split SPF TXT strings: one record or two records?
DNS can store multiple character strings inside one TXT record. SPF concatenates those strings, which is different from publishing multiple separate SPF records at the same name.
HealthCheck Email editorial team · · Examples are illustrative
How to investigate
- Inspect the DNS answer as individual records, not just the editor's visual line wrapping.
- Confirm that concatenated strings preserve needed spaces between mechanisms.
- Query through a public resolver after saving and compare the resulting policy with the intended complete text.
What this looks like
ILLUSTRATIVE EXAMPLE
Two chunks end and begin with include terms but neither contains a separating space. Concatenation joins the tokens into invalid syntax.
A mistake to avoid
Multiple quoted chunks can be valid. Do not merge every TXT record in the zone; ownership verification and other policies are separate data.
Keep the result in context
SPF evaluates the SMTP client against the envelope sender domain, or the HELO identity in the applicable case. A record lookup can identify publication problems; a message result also needs the actual sending IP and identity. Keep those inputs with your investigation.
Take the next step
Use the related check to gather evidence, then compare it with the affected message or service. Keep the result and time with your notes so a later change can be distinguished from the original problem.
Sources and further reading
The protocol references below explain the underlying behavior. Your sending or DNS provider supplies the account-specific settings for its service.