Email configuration is incomplete
Two or more of SPF, DKIM, DMARC, and MX were absent for the scanned domain, so ShipReady combined the absence findings into one ordered task.
Why it matters
Email authentication helps recipients distinguish legitimate mail from forgery. Mail delivery and authentication depend on the services and records that your domain actually uses.
How ShipReady detects it
What it inspects
ShipReady performs DNS checks for SPF, DKIM, DMARC, and MX records, then considers only absence findings from those checks.
What triggers a finding
The merged rule triggers when two or more of those four records are absent. A single absent record remains a separate specific finding; malformed or otherwise defective records are not merged into this rule.
What the evidence shows
The listed record types were absent in the scanner's DNS checks for the domain.
Limits of this check
This finding does not prove that every mail stream is unauthenticated, that a domain sends or receives mail, or that all providers and selectors have been discovered. DKIM selector discovery is bounded, and MX matters only when the domain should receive mail.
How to fix it
Inventory every legitimate sender
List transactional, mailbox, marketing, and support providers that send as the domain before changing DNS.
Add records in a safe order
Configure SPF and DKIM for legitimate senders first. Add or confirm MX only if the domain receives mail. Start DMARC with monitoring, review aligned mail, then increase enforcement deliberately.
How to verify the change
Verify DNS and real mail flows
Query each published record and send test mail through every legitimate provider.
Expected: Required records resolve, legitimate mail aligns as intended, and DMARC reporting shows no unexpected sender before enforcement is raised.