Reverse DNS Lookup

About this tool

Find the hostname registered for an IP address. Reverse DNS answers come from PTR records that the owner of the address block publishes, and mail servers rely on them to decide whether to accept a connection. The lookup queries Cloudflare and Google resolvers independently and then checks whether the hostname resolves back to the same address.

How to use it

  1. Enter an IPv4 or IPv6 address, for example 8.8.8.8 or 2001:4860:4860::8888.
  2. Leave geolocation enabled to see the country, city and ISP alongside the hostname, or turn it off for a faster, DNS-only answer.
  3. Run the lookup. The result shows the PTR hostname from each resolver, whether they agree, and the forward-confirmation status.
  4. For a mail server, confirm that forward confirmation passes: the PTR hostname must have an A or AAAA record pointing back at the same address.

What a PTR record is

Forward DNS maps names to addresses with A and AAAA records. Reverse DNS maps addresses to names with PTR records, stored in special zones: in-addr.arpa for IPv4, where 203.0.113.42 becomes 42.113.0.203.in-addr.arpa, and ip6.arpa for IPv6, where each hex digit of the address is reversed and dotted. These zones are delegated along with the address space, so the organisation that holds the block, usually an ISP, hosting provider or large enterprise, controls the PTR records. A domain owner cannot set reverse DNS from their domain's zone; they must ask whoever provides the server's address.

Forward-confirmed reverse DNS

Anyone who controls a reverse zone can publish any hostname in it, including a hostname they do not own. Forward-confirmed reverse DNS, or FCrDNS, closes that gap: after finding the PTR hostname, resolve it forward and check that one of its addresses matches the original. When both directions agree, the hostname is trustworthy. Mail receivers, SSH servers and some APIs apply this check before accepting a connection, and this tool reports it as a separate pass or fail so you can see exactly which side is misconfigured.

Why mail servers care

Spam is overwhelmingly sent from addresses with no PTR record or with a generic one such as 203-0-113-42.dynamic.example-isp.net. Receiving servers therefore treat missing or generic reverse DNS as a strong negative signal, and the largest providers reject such connections outright. A sending server should have a PTR record naming its own hostname, that hostname should resolve back to the same address, and the HELO name it announces should match. All three are visible or checkable from this page and the DNS lookup.

Other uses

Reverse DNS makes logs readable: a firewall or web server log full of bare addresses becomes a list of crawler hostnames, customer ISPs and cloud regions once each address is resolved. It also helps identify infrastructure, since many providers encode the data centre or role in the hostname. For a whole list of addresses, the bulk reverse DNS tab resolves them in one run and exports the result.

Frequently asked questions

What is a PTR record?

A PTR record maps an IP address back to a hostname, the opposite of an A or AAAA record. It lives in the in-addr.arpa zone for IPv4 or ip6.arpa for IPv6 and is managed by whoever controls the address block, usually the ISP or hosting provider.

Why does my IP have no reverse DNS?

The owner of the address block has not published a PTR record for it. Home connections often have a generic one or none at all. For a server, ask your hosting provider to set it, or set it yourself if they delegate reverse zones to you.

Why does reverse DNS matter for email?

Most receiving mail servers check that the sending address has a PTR record and that the hostname resolves back to the same address. Mail from an address without matching forward and reverse DNS is frequently rejected or marked as spam.

Can one IP address have several hostnames?

Many hostnames can point to one address with A records, but an address normally has exactly one PTR record. The PTR should name the host's primary hostname, which should resolve back to the same address.

Why do the two resolvers disagree?

One of them is serving a cached answer from before the record changed. Reverse zones often carry long TTLs, so a change can take a day to appear everywhere. The authoritative value is the one the newer-looking answer shows; re-run the lookup later to confirm.