Skip to content

Reverse DNS Lookup - Check the PTR Record for an IP

What this tool does

Enter an IPv4 or IPv6 address and the tool builds the reverse lookup name, asks Google Public DNS for its PTR record, and lists every hostname it returns. The lookup runs through a small proxy on this site. Each hostname has a Forward lookup link that opens the DNS lookup so you can check it points back to the same address.

Example

Looking up 8.8.8.8 queries 8.8.8.8.in-addr.arpa and returns dns.google. An A lookup for dns.google includes 8.8.8.8, so forward and reverse DNS agree. A mail server at 203.0.113.25 with a PTR of mail.example.com passes the same test only if mail.example.com has an A record of 203.0.113.25.

When there is no PTR record

Many addresses have none, especially home connections and cloud instances that nobody configured. That is normal for a web server. For a server that sends email, ask the IP owner to set one up, using a hostname under your own domain, then add the matching A record. Generic provider names such as ec2-203-0-113-25.compute.amazonaws.com can pass the forward check, but some spam filters score generic hostnames like that lower than a named mail host.

Once reverse DNS is in place, confirm the domain's SPF and DMARC records authorise the server. To see who registered the domain behind a hostname, use the WHOIS lookup.

Related Tools

Frequently Asked Questions

What is a reverse DNS lookup?
It asks DNS which hostname belongs to an IP address, the opposite of a normal lookup. The answer comes from a PTR record. 8.8.8.8, for example, has a PTR record of dns.google.
Where are PTR records stored?
Under a special name built from the address. For IPv4 the octets are reversed under in-addr.arpa, so 192.0.2.10 becomes 10.2.0.192.in-addr.arpa. For IPv6 every hex digit of the full address is reversed under ip6.arpa. The tool builds the name for you and shows it above the result.
Who sets up reverse DNS?
Whoever controls the IP address, usually the hosting provider, cloud platform or ISP, not your domain's DNS host. On AWS, Azure, Google Cloud and most VPS hosts there is a setting for it in the control panel or a support request. You can't add a PTR record in your domain's DNS zone.
Why does a mail server need reverse DNS?
Many receiving servers look up the PTR record of the connecting IP and reject or penalise mail when there isn't one. Gmail requires sending IPs to have a PTR record whose hostname resolves back to the same IP. That two-way match is called forward-confirmed reverse DNS.
How do I do this from a terminal?
dig -x 8.8.8.8 on macOS or Linux, or nslookup 8.8.8.8 on Windows. Both query the PTR record the same way this tool does.