| Guide | GDE-085 |
| Topic | IP address lookup |
| Domain | Digital infrastructure |
| Last tested | 22 November 2026 |
Short answer: To run an IP lookup, enter the address in the RDAP.org client for its registered holder, then in the Hurricane Electric BGP Toolkit for the network that routes it. Treat the result as a network and a location estimate, not a person.
What is an IP lookup?
An IP lookup is a query that shows which organisation an internet address is registered to, which network routes it and roughly where it is used. Investigators use it to tell a hosting server, VPN exit or mobile network apart from a home connection before they draw any conclusion.
IANA allocates address blocks to five regional internet registries (RIRs), such as RIPE NCC for Europe, the Middle East and Central Asia, and ARIN for North America, which assign them to networks. Each network has an autonomous system number (ASN), the identifier it uses to announce its addresses to the rest of the internet through BGP, the internet's routing protocol.
An IP lookup reads three layers: the registry record, the routing data and commercial geolocation estimates. Journalists, fraud researchers and security teams run it on addresses from email headers, server logs and DNS records. It identifies a network, and only rarely a person.
| • | Identifying the hosting company behind a website's server address |
| • | Checking whether an address in an email header belongs to a mail provider, VPN or home connection |
| • | Testing a claim that activity came from a particular country |
| • | Establishing which network controlled an address on a specific date |
| • | Finding the right abuse contact for a malicious server |
How do you run an IP lookup and trace who controls an address?
Seven free tools and seven steps take you from a single address to a documented record of its registered holder, routing network and likely location.
Six of the seven tools return results in the browser without an account: RDAP.org, Hurricane Electric, RIPEstat, AbuseIPDB, the MaxMind demo and the IPinfo web lookup. ExoneraTor also needs no account but returned an error for recent dates on the test day.
RDAP.org web client: Free, no login. Sends an IP or ASN lookup straight to the responsible registry's RDAP server, the successor to WHOIS, and returns the registered holder, range, dates and abuse contact.
Hurricane Electric BGP Toolkit: Free, no login. Shows the prefix an IP address sits in, the ASN that announces it and that network's other prefixes and peers.
RIPEstat: Free, no login. RIPE NCC's data service for IP addresses and ASNs, with a routing history drawn from its RIS route collectors.
ExoneraTor: Free, no login. The Tor Project's service that checks whether a Tor relay was running on an IP address on a given date. On 22 November 2026 it answered a 2010 date but returned a server error for 2026 dates, so confirm it answers your date before relying on it.
AbuseIPDB: Free to search, no login. Shows community abuse reports, an abuse confidence score and the top reporting countries and categories for any IP address. Charts and report search need an account.
MaxMind GeoIP demo: Free web demo of MaxMind's commercial geolocation data, returning location, ISP, connection type and an accuracy radius for up to 25 addresses. It ran without a login.
IPinfo: Free and paid tiers; the free Lite plan lists 50 web lookups. The web lookup shows location, ASN, company and hosting, VPN, proxy or Tor flags without an account; hosted-domain lists need a free account, and city-level and privacy data through the API is paid.
What we tested: On 29 October and 22 November 2026 we looked up 8.8.8.8, a Google public DNS server, and its prefix 8.8.8.0/24. Six of the seven tools returned results in a browser with no login. ExoneraTor failed: it returned a server error for every 2026 date we tried and answered only its own 2010 example.
Run in a browser on 22 November 2026: ARIN's record for 8.8.8.0 to 8.8.8.255, network name GOGL, registrant Google LLC, with the abuse contact. | ||
Re-run on 22 November 2026: 8.8.8.0/24 originated by AS15169 (Google LLC), with no login. | ||
AS15169 was the only origin for 8.8.8.0/24 from 1 to 22 November 2026. | ||
On 22 November 2026 lookups for 8.8.8.8 on 1 September, 29 October and 20 November 2026 returned "Server problem: the database appears to be empty". The tool's own example, 86.59.21.38 on 1 January 2010, returned a positive result for relay tor26. | ||
22 November 2026, no login: 8.8.8.8 showed a 0% abuse confidence score, 508 reports from 172 reporters and a whitelist note naming Google Public DNS. Charts and report search asked for an account. | ||
22 November 2026, no login: United States, network 8.8.8.0/24, Google, connection type Corporate, with an accuracy radius of 1000 km. | ||
Re-run on 22 November 2026: Mountain View, US, AS15169, a hosting flag, and VPN, proxy and Tor not detected, with no login. |
This is a snapshot of one address on two days. 8.8.8.8 is a well-documented anycast address on a large network, an easy case, and the RIPEstat history covered 1 to 22 November 2026 only.
The Three-Layer Rule: Report the registry holder, the routing network and the location estimate as three separate findings. Never let one layer stand in for another.

