You need to confirm the reverse DNS hostname for a public IP address.
PTR / Reverse DNS Lookup
Check reverse DNS hostnames for a public IPv4 or IPv6 address.
Use this PTR lookup tool to inspect the reverse DNS hostname returned for a public IP address, confirm whether a PTR record exists, and decide what to check next for service identity, mail reputation, or forward/reverse DNS validation.
Check PTR records before troubleshooting mail reputation or reverse-DNS identity issues.
Lookup result
8.8.8.8
NOERROR
Type Value TTL
No PTR records were returned for this IP address by the resolver.
What this tool does
PTR / Reverse DNS Lookup converts a public IPv4 or IPv6 address into its reverse DNS name and queries the live PTR records currently visible from the resolver used by this page.
Use it to confirm whether a reverse hostname exists, inspect what name is published for the IP, and compare that result with the service identity or mail setup you expect.
It does not prove the service is reachable or healthy. It only checks the reverse-DNS layer.
When to use this tool
A mail or reputation issue requires checking whether an IP has a valid PTR record.
A public service address should map back to a hostname and you want to verify the live reverse result.
You are checking whether forward and reverse DNS line up for a server IP.
A provider is expected to control reverse DNS and you need a simple PTR validation step.
You want a focused reverse-DNS lookup before moving to mail, blacklist, or service-level checks.
How to use PTR / Reverse DNS Lookup
- Enter a single public IPv4 or IPv6 address.
- Run the lookup to query the reverse DNS zone for that IP.
- Review the returned PTR hostname or note whether no PTR record exists.
- Compare the reverse hostname with the service identity you expected.
- If needed, continue to forward DNS, IP ownership, blacklist, or mail-related checks.
How to interpret PTR results
PTR record found
Likely meaning: The reverse DNS zone returned one or more PTR hostnames for the IP address.
Common causes: This usually means reverse DNS is configured and publicly visible for the address.
Next action: Compare the returned hostname with the service identity you expected, then verify whether forward DNS points back to the same IP if needed.
No PTR record found
Likely meaning: The IP did not return a PTR record.
Common causes: Reverse DNS may not be configured, the provider may control the reverse zone, or the IP may not be intended for public name identity.
Next action: If the IP is used for mail or public-facing service identity, check who manages reverse DNS and whether a PTR should exist.
Unexpected reverse hostname
Likely meaning: A PTR record exists, but it does not match the hostname you expected.
Common causes: The IP may belong to a provider default hostname, an old server role, a relay, or a different service than you expected.
Next action: Compare the PTR hostname with the owner/provider and verify whether forward DNS and service identity need to be updated.
Multiple PTR records returned
Likely meaning: More than one reverse hostname was returned for the same IP.
Common causes: This can happen in unusual reverse-DNS configurations or during transitions, but it is often worth validating carefully.
Next action: Confirm whether multiple PTRs are intentional. If not, clean up the reverse zone configuration.
Invalid input
Likely meaning: The page could not normalize the value into a valid IPv4 or IPv6 address.
Common causes: The input may contain a hostname, URL, or malformed IP instead of a single address.
Next action: Enter one public IPv4 or IPv6 address only.
Lookup failed
Likely meaning: The browser could not complete the reverse-DNS request cleanly.
Common causes: Invalid input, DNS issues, or upstream resolver/network problems can block the request.
Next action: Retry with a valid IP address, then compare with IP Lookup or DNS Lookup if needed.
Common DNS issues this tool helps uncover
A public IP has no PTR record even though mail or public service identity requires one
PTR exists but points to an old or provider-default hostname
Forward and reverse DNS do not align for the same service
The wrong IP was checked from logs, DNS, or CDN output
The provider controls reverse DNS and the expected hostname was never published
Mail or blacklist troubleshooting is blocked by missing or mismatched reverse DNS
Next steps after PTR Lookup
Run IP Lookup
Check IP ownership, ASN, and broader reverse-DNS context for the same address.
Check forward DNS
If you need to compare the reverse hostname with its forward records, move to DNS Lookup next.
Check blacklist status
If the IP is used for mail, continue to Blacklist Check after confirming PTR.
Run MX Lookup
If the issue is mail delivery, compare PTR findings with MX and mail-routing records.
Related tools
IP Lookup
Inspect basic ownership, reverse DNS, and network details for an IP.
DNS Lookup
Query A, AAAA, CNAME, TXT, and other DNS records for a domain.
Blacklist Check
Check whether an IP or domain appears on common reputation blocklists.
MX Lookup
Inspect mail exchange records and delivery destinations for a domain.
Ping
Check whether a host responds and measure round-trip latency.
PTR / Reverse DNS Lookup FAQ
What does PTR / Reverse DNS Lookup do?
It checks the PTR records for a public IPv4 or IPv6 address and returns the reverse DNS hostname or hostnames currently visible from the resolver used by the page.
What input should I enter?
Enter a single IPv4 or IPv6 address such as 8.8.8.8 or 2606:4700:4700::1111. Do not enter a hostname or full URL.
Why is reverse DNS important?
Reverse DNS is commonly used for service identity, logging, and mail reputation checks. Missing or mismatched PTR data can matter especially for outbound mail.
Why is there no PTR result?
The IP may not have reverse DNS configured, or the provider controlling the reverse zone may not have published a PTR record for it.
What should I check after PTR Lookup?
Usually IP Lookup, forward DNS for the returned hostname, blacklist status, and MX or mail-auth checks if the address is mail-related.