What the bounce says
Exact wording as it appears in the rejection or NDR. Placeholders such as x.x.x.x and example.com stand for your own address and domain.
550-5.7.25 [x.x.x.x] The IP address sending this message does not have a PTR record setup, or the corresponding forward DNS entry does not point to the sending IP. As a policy, Gmail does not accept messages from IPs with missing PTR records.
Gmail refuses mail from IP addresses without valid reverse DNS. 5.7.25 states it plainly: there is no PTR for the sending IP, or the PTR name does not resolve back to that IP. The fix is on the infrastructure, through whoever controls the address block.
Most common causes
- No PTR record is published for the sending IP
- The PTR hostname does not resolve back to the IP
- A new server or IPv6 address was put into service without reverse DNS
- A generic provider PTR was removed or changed
What to verify next
- Confirm the IP from the rejection
- Run the reverse DNS auditor to verify PTR and forward confirmation
- Have the address-block operator publish a PTR under your domain
- Publish a matching A/AAAA record so forward-confirmed reverse DNS closes
Forward-confirmed reverse DNS
Gmail checks two things: that the IP has a PTR, and that the hostname in the PTR resolves forward to the same IP. A PTR alone is not enough; a PTR pointing at a name whose A record is a different address fails.
New servers, cloud instances and IPv6 addresses are the usual sources, because PTR publication is a separate step that is easy to skip.
- PTR must exist and resolve forward to the same IP.
- IPv6 is checked exactly as IPv4.
- Generic provider PTRs pass the check but signal unconfigured infrastructure.
Who publishes the PTR
The operator of the address block — hosting provider, cloud provider, ISP — publishes reverse DNS. Most offer a control-panel setting or a support request. Ask for a hostname under your own domain, then publish the matching A or AAAA record in your zone.
Verify before resending
Run the reverse DNS and HELO auditor on the IP. When PTR and forward resolution agree, send a test to a Gmail address. Allow the TTL to elapse if the PTR was just published.
Best diagnostic path
Mail Failure Doctor
Classify the complete rejection and preserve provider-specific diagnostic context.
Open analysis → Live analysisReverse DNS & HELO Auditor
Check reverse identity, forward confirmation and SMTP greeting consistency.
Open analysis → Live analysisEmail Infrastructure Digital Twin
Map the domain’s public mail infrastructure and provider relationships before remediation.
Open analysis →Known limits
- PTR publication depends on the provider’s process and timing.
- Some providers do not offer custom PTRs on shared plans.
Common questions
Can I set the PTR in my own DNS?
No. Reverse zones belong to the address-block operator. Request it from your provider.
My server prefers IPv6. Why now?
The IPv6 address needs its own PTR. Publish one or configure the server to prefer IPv4 for outbound mail.
Does the PTR need to match HELO?
Not strictly for this check, but consistency between PTR, HELO and forward DNS improves acceptance everywhere.
Why the exact message matters
The same status family can be triggered by different conditions, and providers frequently add diagnostic text that narrows the issue. Use the complete rejection text rather than treating the numeric code as a complete diagnosis.
Provider reference
For the provider-defined meaning and current requirements, review Gmail email sender guidelines.