Use an IP lookup for the right question
An IP lookup explains an address from a connection or log. Enter one IPv4 or IPv6 address to see its category, approximate location and registered network. Location and registration come from separately identified sources. A geographic estimate does not identify a subscriber, while a registry record describes an address allocation. For your own browser’s current source, start with the homepage; a lookup of a typed address does not observe traffic from that device.
Read more
This IP lookup accepts ordinary dotted-decimal IPv4 and standard IPv6 notation. It rejects full URLs, ports, subnet suffixes, abbreviated IPv4 values, and interface zone identifiers. Copy only the address from a log or support message. If your input contains a prefix such as /24, use the subnet calculator to inspect that network range. A domain name belongs in DNS lookup, which can return addresses published for the name.
For a public address, this page requests the responsible regional registry’s RDAP record and a separately attributed IPWhois location profile. Either source can succeed while the other fails. The summary reports complete, partial or missing usable information; an echoed address and timestamp alone are insufficient. Private and special-use ranges are classified locally instead of being sent to public subscriber services. Stop ends the browser’s wait, and Clear removes the displayed input and report.
Read an IP lookup without overclaiming
The normalized address and address family describe the input itself. The registered network name and handle identify the returned registry object. Start and end addresses describe that object's range, which can be larger than a particular customer's assignment. An IP lookup can show an allocation or reassignment record depending on the registry's data. Read the record type and source rather than assuming every returned organization is the individual using the connection.
Read more
Registration country is an administrative attribute, separate from the location provider’s country estimate. The location section may also show a region, city, timezone and network organization. A map appears only when the provider returned valid coordinates; it marks an approximate network location, not GPS or an exact home. A VPN exit, mobile gateway or provider hub can be far from the person using it. Missing fields remain unavailable rather than guessed.
Network ownership is not personal identity
An address can be used through an internet provider, mobile gateway, company, VPN exit, or hosting platform. The registered network holder can be several organizational layers away from the person who sent a request. An IP lookup cannot establish a person's name from an address alone. Avoid identifying or accusing someone solely because a public registry associates the range with an organization or region.
IP lookup limitations and troubleshooting
The location profile and registration record use different datasets and update schedules. Their organizations or countries can legitimately disagree because of leasing, wholesale services, mobile routing or VPN exits. The location service is cached briefly to reduce upstream traffic, and its source timestamp reflects retrieval. Today’s result does not establish which customer held an address months ago. Keep an event timestamp separately when investigating historical traffic and consult an appropriate historical source.
Read more
Why can an IP lookup fail?
A provider can time out, apply quotas, omit fields or return no matching record. This page preserves a successful source when its companion fails. A missing response does not prove that an address is unused or suspicious. Verify the input and retry after the stated delay; rapid repetition rarely adds evidence. Review the source sections before sharing a report, and keep addresses and approximate coordinates private when they reveal connection context.
Sources and next steps
Registry selection follows the IANA RDAP bootstrap registries and IANA's address allocation directory. ARIN's RDAP documentation explains structured registration records. Address handling also draws on RFC 1918, RFC 6598, and RFC 5952. An IP lookup should always identify which kind of evidence it is presenting.
For routing origins, continue with ASN lookup. For operator-published hostnames, use reverse DNS lookup. Choose the next check according to the question that remains unanswered, rather than treating every dataset as a single ownership or safety verdict.