IP lookup

Find approximate location, network and registration evidence for a public address. Private addresses are classified locally.

Public registry and approximate location data.

One public IP is sent to its RDAP registry and IPWhois for separate registration and approximate-location records. Private and reserved inputs are classified locally.

Example report

Illustrative data. Run a lookup for live results.

IP information found

Example report

Available network records are shown below. Registration and approximate location are separate observations; neither identifies a person or device.

Next step: Check the source and time beside each record. Use ASN lookup for routing or reverse DNS for a hostname; rerun missing sources later.

1.1.1.1IPv4

Approximate IP location

IPWhois · 2026-01-15T14:23:00.000Z

Estimated country
Not provided
Estimated city
Not provided
Estimated region
Not provided
Latitude / longitude
Not provided
Time zone
Not provided
Location unavailable

No coordinates were returned for this address.

Internet registration (RDAP)

APNIC (RDAP) · 2026-01-15T14:23:00.000Z

Registered network
Example netblock
Address range
1.1.1.0 – 1.1.1.255
Registration country (not location)
AU
Registration date
2024-08-15T00:00:00Z
Last changed
2026-01-10T00:00:00Z
Location unavailable

No coordinates were returned for this address.

This is a database estimate, not GPS or a street address. A map appears only when valid coordinates are supplied. Registration country below can legitimately differ.

Registration events

Registration events

  1. registration
  2. last changed

Location and registration are independent

  1. One address

    Normalize and classify the submitted IPv4 or IPv6 address.

  2. Location provider

    Retrieve an approximate geographic and network profile.

  3. Regional registry

    Retrieve the allocated network record through RDAP.

  4. Read both sources

    Keep estimate, administrative data and source times separate.

Both sources describe the submitted address; neither identifies an individual. Missing information remains missing.
On this page

Learn more about IP lookup

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.

IP lookup questions

Can an IP lookup find an exact home address?

No ordinary public lookup reliably identifies an exact home. Even commercial geolocation estimates can point to a network exit or a broad area. Registration information is more limited still. An IP lookup should help you understand a network, not encourage false precision. A street-level marker without supporting evidence can be misleading even when the underlying country estimate happens to be correct.

Why does my IP lookup show a company I do not recognize?

Your retail provider may use infrastructure registered to a parent company, wholesale carrier, acquired business, or partner. A VPN or relay can show its exit network instead of your home provider. Compare the address with a fresh browser observation and check your network settings. The IP lookup identifies the returned registered network; the commercial relationship between that network and your service may require additional confirmation.

Is IP lookup the same as reverse DNS?

Reverse DNS requests operator-published PTR records for an address. This page instead separates regional-registry registration from a location provider’s geographic estimate. These datasets can disagree without proving an error or malicious traffic. A returned hostname is not proof of legal ownership, and a missing PTR record does not mean an address is unused.

Reverse DNS lookup

Can I look up an IPv6 address?

Yes. This IP lookup supports IPv6 and normalizes compressed notation. IPv4-mapped IPv6 inputs are treated as their equivalent IPv4 address so a mapped socket representation is not mistaken for evidence of native IPv6 connectivity. To test whether your browser can reach an IPv6-only destination, use the IPv6 test. Classifying a written address and measuring a live route are separate operations.

IPv6 test

What should I include in a report?

Record the exact address, event time, lookup time, registry source, and relevant network fields. State whether you need registration, location, reputation, or routing information. A focused IP lookup report makes its evidence clear and its limits visible. Review copied results before posting them publicly, and avoid attaching credentials or unrelated personal information from the original log.

What happens when I enter a private address?

The tool classifies special-use input locally instead of assigning an invented public city or provider. A private address can be reused on many unrelated networks. It cannot identify a particular household or company without additional local context.

Does typing an address prove that it belongs to my device?

No. A lookup analyzes the supplied value. It does not observe a connection from that device. Use a fresh browser observation for your current public address, and keep the distinction when sharing information copied from logs.

Why can registration load while location fails?

These sections use separately identified sources and can return independently. A failed geolocation request does not erase available registration evidence. Read each source state rather than interpreting partial completion as either total success or no information.