More than one SPF TXT record was observed
ShipReady found more than one TXT value beginning with v=spf1 at the organisational domain.
Why it matters
An SPF configuration should be maintained as one intended record. Multiple SPF-formatted TXT values can make it difficult to understand which sending-authorisation configuration is meant to apply.
How ShipReady detects it
What it inspects
ShipReady queries TXT records for the derived organisational domain and selects values whose trimmed text begins with v=spf1.
What triggers a finding
The rule triggers when more than one SPF-formatted TXT value is returned by that completed DNS lookup.
What the evidence shows
More than one SPF-formatted TXT record was observed at the organisational domain.
Limits of this check
ShipReady performs bounded DNS and text inspection. It does not send email, evaluate how a recipient processes the records, prove SPF failed for real mail, or test delivery, inbox placement, or spam placement.
How to fix it
Inventory intended sending services
List the services that legitimately send mail using the domain and collect the SPF mechanisms each requires.
Publish one deliberate SPF record
Combine the intended mechanisms into one SPF record at the organisational domain and remove superseded SPF-formatted TXT values.
Validate real sending paths separately
Use controlled messages from each intended provider to verify authentication behavior after DNS propagation.
How to verify the change
Query the deployed TXT answers
After DNS propagation, query TXT records for the organisational domain and inspect the returned SPF-formatted values.
Expected: Exactly one intended SPF-formatted TXT record is returned for the organisational domain.