Published MX host addresses lack completed PTR records
ShipReady found one or more published MX hosts with resolved addresses for which all completed reverse-DNS lookups returned no PTR records.
Why it matters
Reverse DNS is a property of the addresses serving a listed inbound MX host. This finding gives an owner a DNS signal to review; it does not establish how receivers score or deliver any real email.
How ShipReady detects it
What it inspects
ShipReady retrieves MX hosts, queries both A and AAAA records for each, then performs PTR lookups for every resolved address.
What triggers a finding
The rule triggers for a host only when it has at least one resolved address, no address has a PTR response, and no PTR lookup is unanswered. A PTR response for any address or any incomplete lookup suppresses the host finding.
What the evidence shows
All completed reverse-DNS lookups for the tested addresses of the listed MX host returned no PTR records.
Limits of this check
ShipReady does not test outbound sending IPs, SMTP connections, forward-confirmed reverse DNS, receiver reputation, spam filtering, or actual mail delivery. It does not infer a provider's behavior from this DNS observation.
How to fix it
Identify who operates the listed MX host
Determine whether the hostname and its address range are managed by your team or by a mail provider before attempting a reverse-DNS change.
Review PTR configuration with the responsible operator
If the host is intended to receive mail and you control its addresses, configure the intended PTR records through the IP-address provider or mail infrastructure owner.
How to verify the change
Verify reverse DNS
Query each active MX host's A and AAAA addresses, then query the corresponding PTR records after changes propagate.
Expected: The intended active addresses have the expected reverse-DNS records.