Build the reverse name
IPv4 octets are reversed under in-addr.arpa; IPv6 nibbles are reversed under ip6.arpa.
Direct answer: A reverse DNS lookup asks the address's reverse zone for a PTR record and returns the hostname or aliases that the address-space operator chose to publish.
The server sends the public IP address through the DNS reverse-lookup path for its in-addr.arpa or ip6.arpa name. Result responses are private, uncached and excluded from search indexing. Do not enter passwords or secrets. Read the lookup privacy policy.
What this reverse dns lookup tells you
Reverse DNS asks for PTR records beneath the special address-mapping zones. It shows which hostname the address holder chose to publish; it does not reverse every domain that happens to use the address.
- Which PTR hostname or hostnames are currently returned
- Whether the reverse name has no data or cannot be resolved
- What to check for forward-confirmed reverse DNS
A PTR hostname identifies published reverse DNS, while the IP WHOIS lookup describes the registered number-resource range containing the address.
How the evidence is collected
Query PTR
The authoritative reverse-zone operator controls the result, often an ISP or hosting provider.
Confirm forward if relevant
Resolve the returned hostname and compare its A or AAAA addresses when an application expects forward-confirmed reverse DNS.
Read the fields without overclaiming
| Signal | What it can establish | What it does not prove |
|---|---|---|
| PTR | A hostname published for an address in reverse DNS. | Every virtual host served by that address. |
| Forward match | The PTR hostname resolves back to the queried address. | Verified organizational identity. |
| NoData | The reverse name exists without a PTR answer. | That the address is unused. |
| Generic hostname | Provider naming for infrastructure or an address pool. | A customer name or physical location. |
A mail server has a PTR but it does not resolve forward
Some receivers treat this as a poor operational signal. Confirm the intended mail hostname, publish matching forward address data, and have the address provider set the PTR. This improves consistency but does not replace SPF, DKIM, DMARC or reputation controls.
Common mistakes
- Expecting a list of all hosted domains
- Assuming the PTR holder owns every service on the address
- Using a generic PTR as geolocation
- Treating forward confirmation as authentication
Reverse DNS Lookup FAQ
Who can change a PTR record?
Usually the organization controlling the address allocation or its delegated reverse zone, not the domain registrar.
Can one IP have multiple PTR records?
DNS permits it, but many applications expect one stable canonical hostname and multiple answers can reduce interoperability.
Why does email care about reverse DNS?
Receivers commonly use consistent hostname and address configuration as one operational reputation signal among many.
Explore more reverse dns lookup and domain research questions