SPF record lacks the recognised all-or-redirect form for this check
ShipReady found no recognised all mechanism or redirect modifier required by this check, or found a recognised ?all mechanism.
Why it matters
An SPF record should make its intended treatment of senders outside its listed mechanisms clear. This scanner signal helps an owner review whether the record's terms match the organisation's intended policy.
How ShipReady detects it
What it inspects
ShipReady tokenizes the selected SPF record with its bounded parser and checks for recognised all mechanisms and a recognised redirect= modifier.
What triggers a finding
The rule triggers when no recognised all mechanism and no recognised redirect= modifier are present, or when a recognised ?all is present. The implementation checks term presence; it does not verify literal final-token position or validate a redirect value or target.
What the evidence shows
The selected SPF record did not contain the recognised all or redirect form required by this check, or contained ?all.
Limits of this check
ShipReady performs bounded DNS and text parsing. It does not evaluate SPF, determine a particular SPF or DMARC result, validate redirect targets, test recipient behavior, send email, or test delivery, inbox placement, or spam placement.
How to fix it
Review the intended SPF policy
Inventory legitimate senders and determine how the organisation intends to handle senders outside that set before changing the record.
Choose the appropriate SPF terms
Update the one SPF record using terms that match the intended policy and provider documentation. If using redirect=, verify its value and target separately because this check does not do so.
Test sending behavior separately
Send controlled messages through each intended sender and inspect the authentication results after DNS propagation.
How to verify the change
Requery the SPF TXT record
Inspect the published SPF text and verify its recognised all or redirect terms match the policy chosen for the domain.
Expected: The SPF record contains the intended policy terms, and controlled mail tests show the expected authentication behavior.