Selected SPF text has more than ten direct lookup-counting terms
ShipReady counted more than ten direct include, a, mx, ptr, exists, or redirect terms in the selected SPF text.
Why it matters
An SPF record with many DNS-dependent terms deserves a review of its provider dependencies and deployment design before it is changed.
How ShipReady detects it
What it inspects
ShipReady performs bounded DNS TXT inspection, selects one SPF-formatted record, splits its text on whitespace, and classifies supported mechanism and modifier tokens.
What triggers a finding
The rule triggers when the scanner counts more than ten direct include, a, mx, ptr, exists, or redirect terms. Exactly ten does not trigger. The scanner does not expand include terms or follow redirects.
What the evidence shows
The selected SPF text has more than ten direct lookup-counting terms under ShipReady's bounded token parser.
Limits of this check
ShipReady does not evaluate the SPF record's dependency graph, expand includes, resolve redirects, process macros, simulate a receiving server, send email, or determine actual SPF outcomes, delivery, or inbox placement.
How to fix it
Map actual SPF dependencies
Inventory the services that send mail for the domain and trace the current SPF include and redirect relationships with the responsible providers.
Simplify only after validating senders
Reduce or consolidate direct DNS-dependent terms where the provider configuration permits it, while preserving every intended sending path.
How to verify the change
Verify the deployed SPF dependency graph separately
Query the published record and use provider-aware SPF analysis or controlled mail tests to evaluate the actual dependency graph after a change.
Expected: The published SPF record supports the intended senders and its actual evaluation has been reviewed separately.