Skip to content
AdminKit

How do you use reverse DNS to investigate an unfamiliar IP address in your logs?

AdminKit explains how reverse DNS helps investigate an unfamiliar IP in your logs: a PTR lookup turns the address into a hostname, often the fastest first clue to what it is — a cloud provider, a generic residential-ISP name, or nothing at all. A PTR record isn't verified against anything, so treat it as a lead to pair with WHOIS/RDAP.

By AdminKit team, Netbase JSC · Updated

Key takeaways

  • A reverse DNS (PTR) lookup turns an IP address into a hostname. That hostname is often the fastest clue to what kind of network the address sits on.
  • The PTR record is published by whoever controls the address block and is not checked against anything. Treat it as a lead, never as proof.
  • Forward-confirm any hostname that matters: look the name up and check that it resolves back to the same IP.
  • No PTR record is common and means little on its own. Move on to WHOIS/RDAP, which reports who the block is registered to.
  • Reverse DNS and RDAP answer different questions. Weigh both against what the traffic is actually doing before you block anything.

Why start with a hostname instead of the raw address?

Because a name usually tells you more at a glance than the numbers do. An IP address on its own tells a human reader almost nothing — it’s a string of numbers with no inherent meaning until you look something up about it. A reverse DNS (PTR) lookup, defined by RFC 1035 (also on the IETF Datatracker) for IPv4 (in-addr.arpa) and extended to IPv6 (ip6.arpa) by RFC 3596, converts that address back into a hostname, which is frequently the fastest first signal about what you’re actually looking at in a server log, firewall log, or access log: a hostname naming a known cloud platform, a monitoring or search-engine crawler, or a generic ISP-assigned name all point you in meaningfully different directions before you’ve done anything else. AdminKit’s reverse DNS tool performs this lookup directly against any IPv4 or IPv6 address, with no query logged. Treat the hostname as a lead rather than a verdict: it is one piece of evidence to weigh during the analysis phase of incident handling described in NIST SP 800-61 Rev. 2.

How does a reverse lookup find the name for an address?

It turns the address into a special domain name and asks DNS for that name’s PTR record. For IPv4, RFC 1035 §3.5 writes the four octets in reverse order under in-addr.arpa. For IPv6, RFC 3596 §2.5 writes every hexadecimal digit (nibble) of the full 128-bit address in reverse order, separated by dots, under ip6.arpa. Reversing puts the most specific part first, so each network can be delegated the part of the reverse tree that matches its address block.

AddressReverse lookup name
198.51.100.2525.100.51.198.in-addr.arpa
2001:db8::11.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa
4321:0:1:2:3:4:567:89ab (the example in RFC 3596)b.a.9.8.7.6.5.0.4.0.0.0.3.0.0.0.2.0.0.0.1.0.0.0.0.0.0.0.1.2.3.4.ip6.arpa

The IPv6 form is easy to get wrong by hand, because every zero that the short notation drops has to be written back in. AdminKit’s tool builds the name for you, and the PTR record generator shows it without doing a lookup. Python’s ipaddress module does the same through reverse_pointer:

>>> import ipaddress
>>> ipaddress.ip_address("2001:db8::1").reverse_pointer
'1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa'
>>> ipaddress.ip_address("198.51.100.25").reverse_pointer
'25.100.51.198.in-addr.arpa'

What does a hostname prove, and what doesn’t it?

It proves only that the operator of the reverse zone chose to publish that name. The single most important fact to carry into this kind of investigation is that a PTR record is set by whoever controls the IP address block, not verified against anything by DNS itself. That means a hostname that looks official — naming a well-known company, service, or product — is a claim the address’s operator chose to publish, not a certified fact.

This is precisely the gap forward-confirmed reverse DNS (FCrDNS) is designed to narrow: after the PTR lookup gives you a hostname, look that hostname up separately (AdminKit’s DNS lookup tool works for this) and check whether its own A or AAAA record resolves back to the same IP you started with. The reverse DNS tool does not run that second step for you. Agreement in both directions is a meaningfully stronger signal than the PTR record alone, though still not a cryptographic guarantee the way a TLS certificate or DNSSEC signature would be — it simply confirms the claimed hostname and the IP are, at minimum, mutually consistent with each other right now. RFC 1912 §2.1 has asked operators to “make sure your PTR and A records match” since 1996, so a well-run network usually passes.

Example output (illustrative, documentation addresses and example.net hostnames). The first address forward-confirms; the second does not:

$ dig -x 192.0.2.44 +short
web-01.example.net.
$ dig web-01.example.net A +short
192.0.2.44

$ dig -x 203.0.113.9 +short
mail.example.org.
$ dig mail.example.org A +short
198.51.100.80

In the second case the name mail.example.org points to a different address, so the PTR claim is not confirmed. That can be a stale record left after a move, or a name chosen to look like someone else’s server. Either way, give it no weight until RDAP and the traffic itself explain it.

What do common hostname patterns suggest?

Hostnames follow loose conventions, not rules, so read the patterns below as hints. The domain at the end of the name (who operates the reverse zone) matters more than the words in front of it.

Pattern in the PTR resultWhat it usually suggestsWhat to check next
The address written into the name, with labels such as dynamic, pool, dsl, cable or cust, under an ISP’s domainA home or small-office connection; the address may be reassigned to someone else laterRDAP for the ISP and its abuse contact; log timestamps, since the user behind it can change
The address written into the name under a cloud or hosting provider’s domain, sometimes with a region labelA rented server or VM; the provider’s customer, not the provider, is running itRDAP for the provider’s range; report abuse to the provider
A descriptive service name such as mail, mx, smtp or relay under an organisation’s domainA mail server or relayFCrDNS; the mail-server guide below
A crawler-style name under a search engine’s domainA search-engine crawler, if it forward-confirmsFCrDNS against the operator’s documented method
A name under a domain unrelated to the RDAP holderThe block holder may have handed reverse DNS to a customer, or the name is misleadingRDAP holder first; FCrDNS on the name
No PTR record at allNothing on its own; common on many rangesRDAP

What if there’s no PTR record at all?

Then move on to a different source; it is not a dead end. A missing reverse DNS record is extremely common and, by itself, a weak signal in either direction. Many cloud providers, hosting companies, and especially residential ISPs simply don’t configure PTR records for every address they operate, so an absent result shows up constantly in ordinary, entirely legitimate traffic. Don’t treat a missing PTR record as suspicious on its own — treat it as a reason to move to a different source of information about the same address rather than a dead end.

What does WHOIS/RDAP add to reverse DNS?

It tells you who holds the address block, from registry records rather than from DNS the operator writes. Reverse DNS and WHOIS/RDAP answer two different questions about the same IP address, and running both gives you more than either alone. The PTR record is a DNS entry the address’s operator chose to publish (or didn’t); a WHOIS/RDAP lookup instead returns the address block’s actual registration data — which organization a regional internet registry (ARIN, RIPE NCC, APNIC, LACNIC or AFRINIC) shows as holding that range, and which network it belongs to. AdminKit’s Whois / RDAP tool performs this lookup for an IP address directly, fetched from your browser via the rdap.org proxy, and shows the registered range, the network name or holder, and the country. An address with a vague or absent hostname but a clearly identified registration — a known cloud provider’s address space, for instance — still tells you something useful about what kind of infrastructure you’re dealing with, independent of whatever its reverse DNS does or doesn’t say.

RDAP is the structured, JSON-based successor to WHOIS. RFC 9082 defines the query: ip/<address> returns the most specific registered network that contains the address. RFC 9224 defines how a client finds the right registry’s server from IANA’s bootstrap registries; rdap.org is a public bootstrap service that redirects each query to the authoritative RDAP server. RFC 9083 §5.4 defines the “ip network” object that comes back. Example (illustrative; the field values are the documentation example from RFC 9083):

{
  "objectClassName": "ip network",
  "handle": "XXXX-RIR",
  "startAddress": "192.0.2.0",
  "endAddress": "192.0.2.255",
  "ipVersion": "v4",
  "name": "NET-RTR-1",
  "type": "DIRECT ALLOCATION",
  "country": "AU",
  "parentHandle": "YYYY-RIR",
  "entities": [ ... ]
}
FieldWhat it tells you during triage
startAddress / endAddressThe registered block the address belongs to; useful if you need to rate-limit a range rather than one address
name and handleThe network’s registry name and ID; compare with the domain in the PTR name
countryThe country on the registration, not necessarily where the traffic came from
parentHandleThe larger block this one was carved out of, often the provider that sub-allocated it
entities with role abuseThe contact the registry lists for network abuse issues (RFC 9083 registers abuse as an entity role)

The full JSON, including entities, is what the RDAP server returns; AdminKit’s tool summarises the range, name and country. For finding and using the abuse contact, see reading a WHOIS/RDAP result to find an abuse contact.

What’s a simple triage sequence?

  1. Run a reverse DNS lookup on the unfamiliar address with AdminKit’s reverse DNS tool to see if it resolves to a hostname at all, and if so, what it claims to be — see how to read a reverse DNS (PTR) lookup result for what the result does and doesn’t tell you, or the best free reverse DNS (PTR) lookup tools comparison if you’re weighing AdminKit’s tool against other free PTR lookups.
  2. If the hostname looks notable, confirm it with FCrDNS — look up that hostname’s own A/AAAA record with the DNS lookup tool and check it resolves back to the same address, rather than trusting the claimed name at face value.
  3. Run a WHOIS/RDAP lookup on the address itself to see which organization and network it’s actually registered to, independent of its reverse DNS.
  4. Weigh both results together with what the traffic is actually doing — a consistent, well-known hostname and registration lowers concern; an inconsistency between the two, or traffic behavior that doesn’t match what a legitimate service of that type would normally do, raises it.
  5. If you’re specifically chasing a mail-related problem rather than general log triage, see PTR records and reverse DNS for mail servers for the FCrDNS check as receiving mail servers apply it, and why is my IP address blacklisted? if reputation, not just identification, is the question you’re actually trying to answer.

Reading the two results side by side:

Reverse DNS resultRDAP resultReasonable reading
Name forward-confirms and its domain matches the RDAP holderHolder clearly identifiedConsistent; judge the traffic on its behaviour
Name forward-confirms, domain differs from the RDAP holderHolder is a providerOften a customer with delegated reverse DNS; the holder’s abuse contact is usually the one to use
Name does not forward-confirmAnyGive the name no weight; rely on RDAP and behaviour
No PTR recordHolder clearly identifiedNormal; rely on RDAP and behaviour
No PTR recordVague or sub-allocated blockFollow parentHandle up to the provider

What can’t these lookups tell you?

None of these lookups, alone or combined, constitute proof of malicious intent — they establish what an address claims to be and who it’s registered to, which is context for a decision, not a substitute for actually evaluating what the traffic from it is doing. They also describe the address now, not when the log line was written. On ranges where addresses are reassigned, the PTR record and even the registration can change between the request and your lookup, so note the time you checked.

See AdminKit’s page for security analysts & SOC teams for the fuller set of free lookups — including WHOIS/RDAP and User-Agent parsing — this kind of triage draws on. This triage walkthrough is part of AdminKit’s DNS cluster of DNS and reverse-DNS guides and tools.

This guide is general information, not a security audit of your specific network — see our disclaimer for what AdminKit's guidance does and does not commit to.

Frequently asked questions

I see an unfamiliar IP repeatedly hitting my server — what should I check first?

Start with a reverse DNS (PTR) lookup on the address: a hostname that clearly names a known cloud provider, search engine, or monitoring service (for example, a hostname ending in a major cloud provider's domain) narrows down what you're looking at immediately, while no PTR record at all, or a generic ISP-assigned hostname, tells you less on its own and is worth following with a WHOIS/RDAP lookup on the same address to see which organization and network it's actually allocated to.

Can I trust a hostname that claims to belong to a well-known company, like a search engine's crawler?

Not from the PTR record alone — anyone who controls an IP address block can set its PTR record to any hostname they choose, including one designed to look legitimate. The standard way to add confidence is forward-confirmed reverse DNS (FCrDNS): look up the hostname the PTR record returned and confirm its own A or AAAA record resolves back to the exact same IP address. If both directions agree, the claim is at least internally consistent; if the forward lookup returns a different address or nothing at all, treat the claimed hostname with real suspicion rather than taking it at face value.

Why does the IP show no PTR record at all?

A missing PTR record is common and, on its own, tells you very little — reverse DNS is set by whoever controls the address block (a cloud provider, hosting company, or ISP), and many operators simply don't bother configuring it for every address, particularly on residential and some lower-cost cloud ranges. It's a data point to combine with a WHOIS/RDAP lookup on the same address, not a signal of malicious intent by itself; plenty of entirely legitimate traffic originates from IPs with no reverse DNS configured.

What does a WHOIS/RDAP lookup add that reverse DNS doesn't tell me?

Reverse DNS gives you a hostname, which is set by the address's operator and not independently verified; WHOIS/RDAP instead gives you the address block's actual registration — which organization it's allocated to and which regional internet registry manages it — sourced from registry records rather than a DNS record the operator controls directly. Running both on the same IP gives you two independent angles on the same question, which is more useful than either one checked alone, especially when they disagree with each other.

Is a reverse DNS hostname enough evidence to block an IP address?

No — treat it as one input into a decision, not the decision itself. A hostname (or its absence) tells you something about how the address is configured, not whether the specific traffic you're seeing from it is malicious; plenty of legitimate scanners, monitoring services, and ordinary users share infrastructure with no distinctive reverse DNS at all. Combine it with what the traffic is actually doing, the address's WHOIS/RDAP registration, and, if relevant, whether the address appears on a reputation list before deciding to block anything based on it.

Want AdminKit to watch this for you?

Free checks tell you the state today. Protective DNS and monitoring tell you when it changes.

Huy Nguyen (David), Founder and CEO of Netbase JSC

Talk to an expert

Huy Nguyen (David), Founder & CEO, Netbase JSC

Ask whether this fix applies to your setup, or get a second pair of eyes on your DNS and mail records.