Skip to content
AdminKit
Free tool Updated

Reverse DNS (PTR) lookup: what hostname does an IP resolve to?

How does this check work, and what does the result tell you?

AdminKit looks up the PTR record for an IPv4 or IPv6 address, live, to show the hostname it reverse-resolves to, if any, since many receiving mail servers check for a matching, sensible PTR record as a basic anti-spam signal before accepting mail.

Part of the DNS cluster — more tools, guides and terms on dns.

AI explanation Run a check below, then sign in to ask AI to explain the result in plain language.

What the result means

A missing PTR record is normal, especially on residential or dynamic IP ranges — it is set by whoever owns the IP block, not by the person using the address day to day.

Next step

Confirm the forward record matches with a DNS lookup, or check your own IP's details.

Keep this result

Copy a link to this check so you can share it or run it again later. Want a heads-up when this result changes? Talk to our team and we'll set it up for you.

Set up alerts with our team

How it works and limits

This tool converts the IP address you enter into its reverse-lookup name — in-addr.arpa for IPv4 (RFC 1035) or ip6.arpa for IPv6 (RFC 3596) — and queries that name’s PTR record through the same DNS-over-HTTPS proxy as the general DNS lookup tool.

Reading the result

A PTR record maps an IP back to a hostname, the reverse of a normal A/AAAA lookup. It is set by whoever controls the IP block — usually an ISP or hosting provider — not by the person using the address day to day. See how to read a reverse DNS (PTR) lookup result for what a hostname, or its absence, actually means.

What a result can look like

  • A sensible, matching hostname (e.g. mail.example.com) — the strongest positive signal for a mail-sending IP.
  • A generic ISP-assigned name (e.g. 123-45-67-89.dynamic.example-isp.net) — normal for a residential or dynamic address, but weak for an IP sending mail.
  • No PTR record at all — common and harmless for non-mail-sending IPs; a likely deliverability problem for ones that do send mail.

Limits

  • This tool looks up a PTR record that already exists. To build the exact reverse-DNS name/record for an IP that doesn’t have one yet — or to decode an existing in-addr.arpa/ip6.arpa name back to its IP — use AdminKit’s PTR record generator, which computes the name without doing any lookup.
  • Not every IP has a PTR record; a missing result is normal for most residential connections.
  • A PTR record is not verified against the forward A/AAAA record unless you also look that name up (use the DNS lookup tool) — a mismatch is a known spoofing/misconfiguration signal, not checked automatically here.
  • No query is logged; see /legal/privacy/.

A missing or wrong PTR record is one of several signals receiving mail servers weigh together with blocklist status — see why is my IP address blacklisted for the fuller picture of how mail reputation gets damaged and how to get delisted. For a mail-server-specific walkthrough of this exact check, see PTR records and reverse DNS for mail servers. See how this tool compares to ViewDNS.info’s Reverse DNS Lookup if you’re deciding between the two, or the best free reverse DNS (PTR) lookup tools comparison for the wider field of free reverse DNS tools beyond ViewDNS.info.

Reference: PTR record.

Frequently asked questions

Why do mail servers care about reverse DNS?

Many receiving mail servers check that a sending IP has a matching, sensible PTR record as a basic anti-spam signal.

Why does my IP have no PTR record?

Reverse DNS is controlled by whoever owns the IP block (often your ISP or hosting provider), not by you — residential IPs frequently have generic or no PTR records.

Does every IP need a PTR record?

No — it matters most for IPs that send mail, since many receivers use a missing or mismatched PTR record as an anti-spam signal. A residential or non-mail-sending IP with no PTR record is normal and not a problem on its own.

Can I set or change the PTR record for my own IP?

Not directly — only whoever controls the IP block (your ISP or hosting provider) can publish a PTR record for it. On most hosting providers you can request a specific PTR value through their control panel or support; on residential ISPs this is usually not offered.