| Field | Value | Copy |
|---|---|---|
| {{ key }} | {{ val }} |
Internet Protocol addresses identify where a device can be reached on the wider network and they can hint at a coarse location that helps with everyday checks. Many people search for a public IP address lookup when testing a connection or confirming a service region.
The page reveals the current public address and a plain summary of version, provider, and time zone so you can confirm where traffic appears to come from. A simple map helps you visualize the approximate area and a compact readout lets you copy details for quick reference.
Use it when verifying a new router, testing a VPN exit, or helping someone confirm where a connection appears to originate. If something looks off, compare the stated time zone and provider with what you expect and repeat the check later to see if routing changed.
Results reflect network routing rather than your exact position, so the map points near an access location and might resolve to a gateway. Consistency over a few checks usually offers the clearest picture.
The tool observes your public Internet Protocol address and retrieves associated attributes, including an approximate geographic centroid, administrative areas, time zone, and network operator details. It reports the address family as IPv4 or IPv6 and displays a human readable local time derived from the time zone string.
A single transformation is applied for readability: the local clock display is computed from the returned time zone using the platform’s locale function for date and time formatting. Mapping centers on the provided latitude and longitude at a moderate zoom so the pin remains contextual rather than street precise.
Interpretation should focus on broad region and provider. Geographic resolution varies because allocations and gateways can represent cities or larger areas. When a VPN or corporate egress is in use, results describe that exit rather than an individual device.
| Input | Accepted Families | Output | Encoding/Precision | Rounding |
|---|---|---|---|---|
| IP address (query parameter) | IPv4, IPv6 | Attributes, map view, copyable tables | JSON values displayed verbatim | None applied |
| — | — | CSV and JSON downloads | UTF‑8 text; JSON pretty print | None applied |
| Field | Type | Min | Max | Step/Pattern | Error Text |
|---|---|---|---|---|---|
| ip (query) | string | — | — | Not enforced in UI | “Lookup failed.” |
| Request failure | — | — | — | 9 s abort | “Unable to retrieve IP information. Please refresh.” |
| Map coordinates | number | finite | finite | — | Map hidden if invalid |
Processing is browser‑based. The page issues requests to third‑party endpoints to obtain IP attributes and map tiles. No data is transmitted or stored by this page beyond those calls.
IP address inspection with an approximate location and provider check.
Example: Visit with ?ip=192.0.2.1 to check a specific address; the fields will populate accordingly.
It is approximate and often maps to a service gateway or city center. Treat it as a region cue rather than an exact position.
Precision varies by provider and allocation.The time zone reflects the network exit point. If a VPN or corporate egress is active, the zone may differ from your physical location.
Disable VPN to compare.Yes. Add ?ip=<address> to the page URL and reload. The lookup will run for that address.
No. Results are shown in the page and files you download are created in your browser.
External endpoints are contacted to obtain data.No. The lookup service and map tiles require network access.
Offline use is not supported.You can save a prettified JSON response or a compact CSV of the Info table for quick sharing.
Downloads rely on your browser’s file APIs.Provide the address in the ip query parameter. The service detects the family and returns matching details.
The point represents an estimated location for the network, not a device. Expect city‑level accuracy, sometimes broader.
Use it for orientation, not navigation.