What happens if PTR and HELO don’t match?
Still have a question, spotted an error, or have a better explanation or a source we should cite?
Your mail server introduces itself the moment it connects to another server. That introduction is the HELO (or EHLO) command, and it carries a hostname. If the receiving server looks that IP up in reverse DNS and gets a different name back, something feels off. And receiving servers notice.
Here's what a clean, aligned configuration looks like for a hypothetical server at IP 192.0.2.1:
- HELO/EHLO hostname: mail.tidalmail.com
- PTR record (rDNS lookup of 192.0.2.1): mail.tidalmail.com
- A record (forward DNS for mail.tidalmail.com): 192.0.2.1
All three point to the same identity. That's what receivers want to see. This is called forward-confirmed reverse DNS (FCrDNS), and it's a basic trust signal.
When they don't match, a few things can go wrong. Some strict receivers will outright reject the connection at the SMTP level before your message even gets a chance. Others will pass the message through but apply heavier spam filtering. Reputation systems quietly log the inconsistency and it chips away at your sender score over time. None of these are instant death sentences on their own, but a mismatch is the kind of thing that stacks with other signals and eventually tips you into the junk folder.
The most common reasons this happens in practice:
- Your server's IP changed (cloud migration, new hosting) but the PTR wasn't updated to match
- You're on shared hosting and the HELO is set to the provider's generic hostname, not yours
- The PTR was never configured at all (your ISP or hosting provider usually controls PTR records, not you)
- A new sending IP was added but only SPF and DKIM were set up, with rDNS overlooked
The fix is straightforward in theory. Your HELO hostname, your PTR record, and your A record all need to agree. In practice, the tricky part is that PTR records are controlled by whoever owns the IP block, which is often your hosting provider or ISP, not you. You'll usually need to request the PTR update through them, not through your own DNS registrar.
If you're not sure whether your current setup is aligned, you can check your PTR alignment with a quick lookup or ask us if you're stuck. Getting this right is one of those foundational details that's easy to overlook and surprisingly impactful.
Contributors
Who worked on this answer
Every name links to their profile. Every company links to their site. Real people, real accountability.