Gmail requires every sending server to have reverse DNS: a PTR record for its IP address, naming a host whose own A (or AAAA) record points back to that same address. The server that sent this message fails one of those two checks.
550 5.7.25 This message was blocked because the sending IP address doesn't have a PTR record, or the forwarding DNS entry doesn't reference the sending IP address. Gmail requires that sending IP addresses have a PTR record. Learn more about requirements for sending IP addresses. To learn more about Gmail requirements for bulk email senders, visit Email sender guidelines. - gsmtp
2 other wordings of the same rejection
Temporary:
451 4.7.23 203.0.113.5 The sending IP address for this message doesn't have a PTR record, or the PTR record's forward DNS entry doesn't match the sending IP address. To protect users from spam, your email has been temporarily rate limited. To learn more about IP address requirements for sending to Gmail, visit the IP addresses section of our sender guidelines. To learn more about Gmail requirements for bulk email senders, visit Email sender guidelines. - gsmtp
Temporary, older wording:
421 4.7.0 The IP address sending this message does not have a PTR record, or the corresponding forward DNS entry does not point to the sending IP. To protect our users from spam, email sent from your IP address has been temporarily rate limited. For more information, go to Email sender guidelines. - gsmtp
Your bounce names your own domain and sending address where this one says example.com and 203.0.113.5.
| Code | 550 5.7.25 |
| Sent by | Gmail |
| Type | Permanent — not retried |
| Cause | Reverse DNS |
See what receivers see
Send one email to our test address and get back the sending server’s reverse DNS, TLS, authentication and blocklist results — the things this bounce is about.
What it means
Reverse DNS is set by whoever owns the IP address — your hosting company, cloud provider or ISP — not in your domain’s DNS. That is why it is so often missed: everything in your own zone can be perfect and this still fails.
The 4.7.23 and 421 4.7.0 versions are temporary: Gmail slows the server down and it retries.
Why it happens
- A new VPS or cloud server whose reverse DNS was never set.
- A PTR record naming a host that does not resolve back to the same address (forward-confirmed reverse DNS fails).
- Mail sent over IPv6 from an address with no IPv6 PTR record, while the server’s IPv4 one is fine.
How to fix it
- Find the sending address in the bounce, and set its reverse DNS in your hosting or cloud control panel (or ask the provider) to a name such as mail.yourdomain.com.
- Make sure that name has an A record (AAAA for IPv6) pointing to the same address.
- If the server sends over IPv6 without IPv6 reverse DNS, set one — or make it send over IPv4.
- Send a test email to see the reverse DNS receivers see.
Questions
Can I fix reverse DNS in my domain’s DNS?
No. The PTR record lives in the reverse zone of the IP address, which belongs to whoever owns the address. You set it in your server provider’s panel, or ask them to.
Sources
Message text and meaning checked on 25 September 2026 against these official sources:
- Gmail SMTP errors and codes — knowledge.workspace.google.com
- Email sender guidelines — support.google.com