What is reverse IP lookup?

At the networking layer, a reverse IP lookup queries the DNS for a PTR (pointer) record. For IPv4, the octets of the address are reversed and appended with the `.in-addr.arpa` domain — so a lookup for `8.8.4.4` queries `4.4.8.8.in-addr.arpa` and retrieves a hostname like `dns.google`. The reversal exists because DNS reads names from most-specific to least-specific, while IP addresses are written the other way. PTR records are controlled by whoever owns the IP block — usually an ISP or a large enterprise that purchased its own block from a regional registry (ARIN for North America, RIPE NCC for Europe, APNIC for Asia-Pacific) — not by whoever runs the website, which is why coverage is uneven.

In the B2B visitor-identification context, the mechanism goes further than standard PTR records. A JavaScript tag or server-side log captures the visitor's public IP; a commercial IP-to-company database — built from Regional Internet Registry records, ISP data partnerships, and machine-learning models — maps the IP to a company name plus firmographic attributes (industry, employee count, estimated revenue, headquarters). The result is typically delivered in milliseconds, before the page finishes loading.

The data return typically includes 10–20 fields per lookup: company name, domain, industry classification (NAICS/SIC), headcount, estimated revenue, and geography. Premium platforms also append behavioral context — which pages were visited, for how long, and whether the account appears on a configured target-account list.

6sense Research found that only approximately 3% of B2B website visitors submit a form. Without reverse IP lookup, that traffic is invisible — analytics tools record page views but cannot tell you that a procurement team spent 12 minutes on your pricing page and three minutes on your case studies. When an IP match succeeds, that anonymous session becomes an account-level intent signal: a named company showing active purchase research.

Account-based marketing teams use this signal to prioritize accounts, trigger sales alerts, or serve personalized content and targeted ads. The category has grown substantially: independent market research from 2025 projects the visitor identification software market will expand at a compound annual growth rate above 15% through 2035, reflecting how central IP-to-company matching has become to revenue operations stacks.

The lift is real when the data is accurate, but the signal needs context. A single visit from a target account is noise; repeated sessions on high-intent pages — pricing, competitor comparisons, case studies — from the same company over a short window is a strong buying signal worth acting on immediately.

Accuracy varies sharply by traffic source. Corporate office traffic — employees working from a company-owned network with a dedicated IP block registered in the company's name — resolves at 85–95% accuracy for most commercial providers. The problem is that corporate office traffic has become a minority of B2B web visits.

Remote work is the biggest structural headwind. Employees on residential ISP connections appear under their ISP (Comcast, AT&T, BT), not their employer. Industry estimates in 2025–2026 suggest that a large share of B2B knowledge-worker traffic now originates from residential IPs, which are largely opaque to IP-to-company matching. VPN use, Carrier-Grade NAT (CGNAT), and coworking spaces compound the problem. Independent testing by Warmly and others in 2025–2026 puts realistic company-level match rates at 30–65% of US B2B traffic — well below vendor-marketing claims, and a significant decline from the 80%+ rates achievable when most employees worked from offices a decade ago.

Leading platforms compensate by layering in cookie graphs, device fingerprinting, and deterministic identity data on top of IP matching. Demandbase, for example, holds a US patent on methods for identifying companies visiting websites that go beyond standard PTR records — using machine learning to map IP ranges leased from ISPs back to the actual corporate tenant. Even so, no single data layer closes the gap entirely; the most accurate stacks combine multiple signals.

A forward DNS lookup resolves a human-readable domain name (like `komo.ai`) to an IP address, using an A or AAAA record. Reverse IP lookup goes in the opposite direction — it resolves an IP address back to a domain name or organization, using a PTR record stored under the `.in-addr.arpa` zone.

Ownership asymmetry matters here. You control your forward DNS records directly through your domain registrar. You do not control reverse DNS — PTR records are managed by whoever owns the IP block, which is usually an ISP or a large enterprise that purchased its block from a regional registry. A company can have a perfectly configured forward DNS setup and still have no usable PTR record because their ISP never configured one on their behalf.

In the B2B identification context, commercial providers go further than standard PTR records. They build proprietary databases that map IP ranges to companies by combining RIR data with ISP partnerships, machine learning, and behavioral correlation — because PTR alone would leave too many corporate IP ranges unmapped, particularly those leased rather than owned outright.

Every major mail server performs a reverse DNS lookup on the IP address that sent an incoming email. The server checks whether a PTR record exists for that IP, then does a forward lookup on the returned hostname to verify it points back to the same IP — a process called Forward-Confirmed Reverse DNS (FCrDNS). If either check fails, the message is likely to be flagged or rejected.

This became a hard requirement in 2024–2025. Google and Yahoo mandated valid reverse DNS for bulk senders in February 2024. Microsoft followed with a permanent 550 5.7.515 rejection for non-compliant bulk mail to Outlook, Hotmail, and Live addresses from May 2025. For cold outreach, sending from a server or cloud IP without a matching PTR record — a common scenario with shared hosting or newly provisioned cloud servers — is one of the fastest ways to destroy deliverability.

Setting up a PTR record for your sending IP (and ensuring the returned hostname matches your `From` domain) is considered a baseline requirement for any outbound email program, alongside SPF, DKIM, and DMARC. Many ESPs handle PTR configuration automatically for their shared IP pools; teams running on raw cloud infrastructure must configure it explicitly with their IP provider — typically via a support ticket to the hosting or ISP vendor that owns the block.

Performing a reverse IP lookup on publicly registered IP data is legal. The underlying information is derived from public registries such as ARIN, RIPE NCC, and APNIC, which publish allocation data openly. The legal question under GDPR turns on whether IP addresses constitute personal data — and GDPR does classify IP addresses as personal data by default, because they can potentially be linked to an individual.

However, company-level identification — matching an IP to an organization without resolving to a named individual — is considered low privacy risk and is generally defensible under GDPR's legitimate interests basis, because the output is organizational, not personal. CCPA applies a similar logic: the California Attorney General has indicated that if a business collects IP addresses but does not link them to any particular consumer or household and could not reasonably do so, the IP address would not qualify as 'personal information' under CCPA.

Practically, vendors operating in the EU recommend disclosing IP-based company identification in your privacy policy and presenting a cookie/tracking notice to visitors. Person-level identification of EU or UK residents — where the lookup result is linked to a specific named individual — requires a lawful basis, typically explicit consent. Using reverse IP lookup results for unauthorized system access or exploitation crosses both legal and ethical limits regardless of jurisdiction.

Reverse IP lookup is a first-party intent signal: it tells you which accounts are researching you right now, in real time, without waiting for them to raise a hand. That is exactly the kind of signal Komo is built to act on. When a target account shows up on your pricing or case-study pages — even anonymously — that visit is evidence of active evaluation, not passive curiosity.

Komo monitors these signals alongside others (job changes, funding, hiring activity) and, when one fires, researches the account and drafts the outreach: the right contact at the right company with a message grounded in what they were looking at and what has changed in their world. The reverse IP match provides the timing; Komo supplies the context and the draft.

The human-in-the-loop model matters here because IP-matched visitors are probabilistic, not certain — a match rate of 30–65% means a meaningful share of signals need a second look before you act on them. Komo keeps you on every send that matters, so the speed advantage of real-time visitor intelligence does not come at the cost of wasted outreach to the wrong company or contact.