No MX record observed for a domain with selected SPF text
ShipReady found selected SPF text for the organisational domain but no MX records in a completed DNS lookup.
Why it matters
A domain that has an SPF record may have an email-related configuration worth reviewing when it has no MX records. This is a DNS observation only; it does not establish actual sending, receiving, replies, bounces, or mail-delivery outcomes.
How ShipReady detects it
What it inspects
ShipReady runs this check only when it has selected SPF text for the organisational domain, then performs a DNS MX lookup for that domain.
What triggers a finding
The rule triggers when the MX lookup completes with NXDOMAIN or no MX answer. An absent selected SPF record or any DNS lookup failure suppresses the finding.
What the evidence shows
The completed MX lookup for the organisational domain returned no MX records while selected SPF text was present.
Limits of this check
ShipReady does not prove that the domain sends mail, cannot receive mail through every permitted delivery path, has a broken fallback path, loses replies or bounces, or experiences deliverability problems. It does not send SMTP or email.
How to fix it
Confirm whether the domain is meant to receive mail
Review the domain's mail-provider and product requirements before adding records; some domains intentionally do not receive email.
Configure the intended receiving service
If the domain should receive email, publish the MX records supplied by the receiving mail provider and retain any related provider requirements.
How to verify the change
Verify MX DNS after propagation
Query the organisational domain's MX records from an independent resolver and confirm they match the intended mail provider.
Expected: The expected MX records are present for a domain intended to receive email.