Help & Troubleshooting
PTR Record (Reverse DNS)
What this is
A PTR record maps an IP address back to a hostname — the reverse of an A record. Mail servers check it constantly: sending mail from an IP with missing or mismatched reverse DNS is a strong spam signal.
How to read your result
For a mail server IP, the PTR should exist and should match the name the server uses in its SMTP greeting (and that name's A record should point back at the same IP — "forward-confirmed reverse DNS").
Common problems and how to fix them
No PTR record on a sending mail server IP
How it shows up: Outgoing mail is rejected or lands in spam at major providers; bounce messages mention reverse DNS or rDNS.
How to fix it: PTR records are controlled by whoever owns the IP block — your hosting/cloud provider — not by your domain's DNS. Set it in the provider's console (most clouds have an rDNS field) or open a ticket, pointing it at your mail server's hostname.
PTR exists but does not match the mail server's HELO name
How it shows up: Stricter receivers defer or reject mail; spam scores are elevated despite SPF/DKIM passing.
How to fix it: Align all three: the PTR name, the hostname the mail server announces (HELO/EHLO), and that hostname's A record. All should agree on one name and one IP.
Generic provider PTR (e.g. 203-0-113-7.provider.example)
How it shows up: Some receivers treat mail from generic-looking rDNS as consumer-grade and score it as likely spam.
How to fix it: Replace the default PTR with a hostname under your own domain (e.g. mail.yourdomain.com) via your provider's rDNS settings.