PTR Record Lookup
A PTR record maps an IP address back to a hostname. This is reverse DNS. Enter an IP address to run a reverse lookup across 21 global servers and see the name it resolves to.
PTR takes an IP address, not a domain. Enter an IPv4 address such as 8.8.8.8.
Global DNS Propagation
 New York, USA Google | --- |
| Chicago, USA Gcore | --- |
| Los Angeles, USA Cloudflare | --- |
 Toronto, Canada CIRA | --- |
 Mexico City, MX OpenDNS | --- |
 London, UK Quad9 | --- |
 Frankfurt, Germany DNS.Watch | --- |
 Paris, France FDN | --- |
 Amsterdam, NL OpenNIC | --- |
 Moscow, Russia Yandex | --- |
 Singapore Singtel | --- |
 Tokyo, Japan IIJ | --- |
 Mumbai, India Google India | --- |
 Seoul, Korea KT | --- |
 Dubai, UAE Etisalat | --- |
 Sydney, Australia Telstra | --- |
 Auckland, NZ Cloudflare | --- |
 São Paulo, Brazil NIC.br | --- |
 Buenos Aires, AR Telecom Arg | --- |
 Johannesburg, ZA ISPA | --- |
 Cairo, Egypt Telecom Egypt | --- |
DNS Map
About PTR records
A PTR (Pointer) record does the opposite of an A record. Instead of turning a name into an IP, it turns an IP back into a name. This is called reverse DNS, and it lives in a special zone under in-addr.arpa for IPv4. Unlike forward records, a PTR is controlled by whoever owns the IP block, usually your hosting provider or ISP, not by the domain owner.
Each row shows one of the 21 global servers and the hostname the IP maps to, for example dns.google for 8.8.8.8. A row with no value means the IP has no PTR record set. Many residential and cloud IPs either have none or return a generic provider hostname.
Reverse DNS matters most for mail servers. Receiving servers often reject or flag mail from an IP whose PTR does not match the sending hostname. If you run your own mail server and messages are landing in spam, confirm the sending IP has a PTR record that resolves back to the name your server announces.