A reverse IP lookup takes an IP address and returns information about who or what is behind it: a hostname, the network owner, or, in B2B marketing, the company a website visitor is likely browsing from. A normal DNS lookup goes from a name to an address; a reverse lookup goes from the address back to a name or organization.
The term covers two different things that are often confused: the technical DNS mechanism (reverse DNS) and commercial IP-to-company databases used for visitor identification.
How reverse IP lookup works
1. Reverse DNS (PTR records)
DNS has a built-in reverse mapping. For IPv4, the address is written backwards under the special domain in-addr.arpa, and the owner of the address block can publish a PTR record pointing to a hostname (RFC 1035, IETF). IPv6 uses the same idea under ip6.arpa, with each hexadecimal digit reversed (RFC 3596, IETF).
So a lookup of 203.0.113.25 queries 25.113.0.203.in-addr.arpa. If a PTR record exists, you might get mail.example.com. Mail servers use this to check senders, and admins use it to read logs. The limits: PTR records are optional, set by whoever controls the address block (often the ISP, not the company), and frequently generic, such as host-203-0-113-25.isp.net.
2. IP-to-company databases
B2B identification tools go further. They combine several sources into a database that maps IP ranges to organizations:
- Registry (WHOIS/RDAP) data: who an address block is allocated to. Large companies and universities often hold their own ranges.
- Reverse DNS: hostnames that reveal the organization.
- Observed traffic: IPs repeatedly seen with a company's email domain in form fills or logins.
- Cloud and hosting ranges: flagged so data-center traffic is not mistaken for a company.
The output is a probabilistic match ("this IP most likely belongs to Company X") plus firmographic data about that company.
Example
Example (illustrative): your site logs 1,000 sessions from 800 IP addresses in a week. The lookup pipeline might sort them like this:
- Corporate network ranges registered to a company: matched with high confidence.
- Shared offices, coworking spaces and corporate VPN exit nodes: matched, but sometimes to the wrong tenant or to a VPN provider.
- Residential broadband and mobile networks: usually only the ISP, so no company.
- Cloud and data-center IPs: bots, crawlers or consumer VPNs, filtered out.
The share that resolves to a company depends heavily on your audience. A site visited mainly by enterprise employees in offices resolves far more than one visited by small-business owners working from home. Ask any vendor to run a test on your own traffic rather than trusting a headline match rate.
Accuracy limits
| Factor | Effect |
|---|---|
| Remote and hybrid work | Home connections show the ISP, not the employer |
| VPNs and secure web gateways | Traffic may exit through a security vendor's or a distant office's IP |
| Mobile networks | Carrier-grade NAT puts many users behind one address |
| IPv6 | Huge address space and rotating privacy addresses make range mapping harder; adoption is growing (Google IPv6 statistics) |
| Stale data | Address blocks change hands; old mappings misattribute |
How B2B teams use reverse IP lookup
- Seeing which target accounts visit the website without filling a form.
- Alerting account owners when a known account views pricing or demo pages.
- Personalizing pages by industry or company size for identified visitors.
- Filtering bot and data-center traffic from analytics.
Frequently Asked Questions
Can a reverse IP lookup identify a person?
Not on its own. It identifies a network, and at best the organization that owns it. Tying an IP to a named person requires other data, such as a login, a form fill or a third-party identity graph, and at that point privacy law treats it as personal data processing. In the EU, IP addresses can themselves be personal data.
What is the difference between reverse IP lookup and reverse DNS?
Reverse DNS is the specific DNS query for a PTR record, returning a hostname if one was published. Reverse IP lookup is the broader term: it can mean reverse DNS, finding all domains hosted on one server IP, or matching an IP to a company using commercial databases.
Why does my reverse IP lookup return only an ISP?
Because the address belongs to the ISP's pool, typically a home, mobile or small-office connection. The ISP controls the PTR record and registry entry, so nothing points to the end user's organization. This is the main reason company-level match rates fall as remote work grows.
Related
See how the lookup fits into a full workflow in visitor identification and the visitor identification guide, compare tools in website visitor identification software, and read about signals in intent data.