How to Check Reverse DNS for Mail (Step-by-Step Guide)
A practical guide to checking reverse DNS for mail servers, including PTR records, forward confirmation (FCrDNS), and what good mail-related reverse DNS looks like.
Why reverse DNS matters for mail
Reverse DNS (rDNS) is an important trust signal for outbound mail servers. Many receiving systems check PTR records as part of spam filtering and reputation assessment.
A missing, incorrect, or low-quality PTR setup can reduce trust and contribute to spam classification or rejection.
While reverse DNS alone does not guarantee deliverability, it is a baseline requirement for most modern mail systems.
Start with the sending IP address
Reverse DNS checks always begin with the sending IP address, not the domain name.
That IP should have a PTR record that maps to a meaningful hostname.
You can check PTR records by querying the IP directly.
If no PTR record exists, this is a primary issue that should be resolved before investigating further.
Understand forward-confirmed reverse DNS (FCrDNS)
A strong reverse DNS setup includes forward-confirmed reverse DNS (FCrDNS).
This means the PTR hostname resolves back to the original IP address via a forward lookup.
For example, an IP resolves to a hostname via PTR, and that hostname resolves back to the same IP via an A record.
This bidirectional relationship increases trust and is commonly checked by receiving mail systems.
Confirm the PTR target resolves forward
After identifying the PTR record, perform a forward DNS lookup on the returned hostname.
The hostname should resolve successfully and ideally include the original IP address.
If the forward lookup fails or points elsewhere, the reverse DNS configuration is weak or inconsistent.
What good reverse DNS usually looks like
- PTR record exists for the sending IP
- PTR hostname is clearly associated with the domain or mail service
- PTR hostname resolves via A or AAAA record
- Forward lookup includes the original IP (FCrDNS)
- Hostname reflects a mail role such as mail.example.com
What weak reverse DNS often looks like
- No PTR record configured
- PTR hostname does not resolve
- PTR hostname resolves to a different IP
- Generic or provider-default naming such as ip-1-2-3-4.provider.net
- Hostname unrelated to the sending domain
Who controls reverse DNS
PTR records are not managed in your normal DNS zone.
They are controlled by the organisation that owns the IP address range, such as your ISP, cloud provider, or hosting provider.
This means reverse DNS changes often require updates through your infrastructure provider rather than your DNS hosting platform.
How reverse DNS affects deliverability
Many mail systems treat missing or invalid reverse DNS as a negative signal.
While it may not always cause outright rejection, it can contribute to spam scoring and reduced inbox placement.
Reverse DNS is typically evaluated alongside SPF, DKIM, and DMARC. A complete and consistent setup across all of these areas provides the strongest foundation for reliable email delivery.
A practical reverse DNS troubleshooting workflow
- Identify the sending IP address from mail headers or logs
- Query the PTR record for that IP
- Confirm the PTR hostname exists and is meaningful
- Perform a forward lookup on the PTR hostname
- Verify the forward result includes the original IP (FCrDNS)
- Update PTR via your provider if missing or incorrect
- Re-test mail delivery after changes
Related checks
Reverse DNS is only one part of diagnosing mail delivery issues.
If behaviour appears inconsistent, consider whether DNS caching or propagation may also be affecting results.