No SPF TXT record was found
ShipReady found no TXT record beginning with v=spf1 for the organisational domain.
Why it matters
SPF lets a domain publish sending-authorisation information that other email authentication systems may use.
How ShipReady detects it
What it inspects
ShipReady queries TXT records for the organisational domain and selects records beginning with v=spf1.
What triggers a finding
The rule triggers when the completed TXT lookup contains no SPF record.
What the evidence shows
No SPF-formatted TXT record was observed in the completed lookup.
Limits of this check
ShipReady does not send email, test a sender, inspect DKIM or receiving-provider policy, or prove that messages can be spoofed or delivered to spam. DNS changes may also occur after the scan.
How to fix it
Publish an SPF record for intended senders
Inventory services that send using the domain and publish one SPF record that represents the intended sending sources.
How to verify the change
Query the deployed TXT record
Verify the domain returns exactly one intended SPF record and test legitimate sending paths separately.
Expected: A valid SPF record represents the intended senders.