Internet Protocol addresses are numbered labels that allow devices to exchange traffic across networks. An internet protocol address location lookup by city and provider helps you confirm where a connection appears to originate and whether routing aligns with expectations. Results are presented in plain language so you can make quick decisions and share context.
You can enter a public address or a domain name and the tool finds the current address then reports the city, country, latitude and longitude, and the service provider. It also shows the local time based on the reported time zone so you can read timestamps in context.
A simple example is checking a sign in from an unfamiliar place and seeing it maps to the expected region and provider. Another is surveying a set of addresses to spot hosting ranges by the name that appears in reverse lookup.
Location data is approximate and can be influenced by relays or privacy tools, so treat the output as directional rather than precise.
Internet Protocol version 4 (IPv4) and version 6 (IPv6) addresses are the identifiers being inspected. A submitted value may be an address, a domain, or a full Uniform Resource Locator (URL). When a domain or URL is provided, the hostname is extracted and resolved to an address using Domain Name System over HTTPS (DoH).
The address is then sent to a geolocation service that returns descriptive fields such as country, region, city, postal code, latitude, longitude, time zone, and connection attributes including Internet Service Provider (ISP), Autonomous System Number (ASN), and Autonomous System Organization. The interface also computes a local time string from the returned time zone identifier to help interpret event timing.
Coordinates are displayed with fixed precision for readability. The string for copying uses six decimal places on latitude and longitude to balance brevity with map accuracy. The tool also performs a reverse Domain Name System (PTR) query to display a human‑readable name when one is published.
Comparisons across runs are valid for the same address at a given moment; results can change as routing or registry data is updated. Domain queries choose the first available IPv4 answer, falling back to IPv6 when needed.
| Symbol | Meaning | Unit/Datatype | Source |
|---|---|---|---|
| ip | Resolved Internet address | IPv4/IPv6 string | Derived |
| lat | Latitude | degree | API |
| lng | Longitude | degree | API |
| tz | Time zone identifier | IANA string | API |
| offsetmin | UTC offset | minute | API |
| type | Address family | “IPv4” or “IPv6” | API |
52.520008, 13.404954. The OpenStreetMap and Google Maps links open at those coordinates, and the local time is rendered using that time zone.
| Field | Type | Min | Max | Step/Pattern | Error Text / Placeholder |
|---|---|---|---|---|---|
| Address | string | — | — |
IPv4: ^(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)\.(25[0-5]|2[0-4]\d|1\d\d|[1-9]?\d)$IPv6: ^(([0-9A-Fa-f]{1,4}:){1,7}[0-9A-Fa-f]{1,4}|(([0-9A-Fa-f]{1,4}:){1,7}:)|(::([0-9A-Fa-f]{1,4}:){0,6}[0-9A-Fa-f]{1,4}))$ or any string containing ::
|
Placeholder: “8.8.8.8 or example.com” |
| Domain/URL | string | — | — | Hostname extraction supports http, https, and strips mailto: |
Errors: “Could not resolve domain to an IP.” |
| Public IP detect | network | — | — | Timeout ~6000 ms on the detection request | Errors: “Could not detect your IP.” |
| Input | Accepted Families | Output | Encoding/Precision | Rounding |
|---|---|---|---|---|
| Address or domain/URL | IPv4, IPv6, hostname | Info fields, map, JSON | JSON pretty print; CSV rows “Field,Value” | Lat/Lng to six decimals |
https://ipwho.is/{ip}.https://api.ipify.org?format=json.https://dns.google/resolve?name=...&type=... then https://cloudflare-dns.com/dns-query?name=...&type=... with accept: application/dns-json.https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png with attribution.Client logic is lightweight; latency is dominated by external requests. Map rendering and string formatting are constant‑time for single results.
Transient errors show inline messages. Identical inputs yield the same fields when upstream services return consistent data.
rel="noopener" to limit tab access.::.Behavior aligns with Internet Protocol addressing practice, reverse DNS conventions for pointer records, and the IANA time zone database for local time rendering.
Lookups are issued from the browser to public APIs; no results are stored server‑side by this page.
Internet Protocol address lookup, with optional domain resolution and reverse name:
Example. Input “example.com”. The tool resolves the hostname, fetches location fields, shows a local time, and offers map links and JSON.
You now have a concise view of where an address appears to be and who operates the network.
No. Lookups are requested from public endpoints and the page does not retain results beyond your session.
Downloads are created locally on demand.It reflects what the upstream service reports for the address. Proxies, mobile networks, and routing changes can shift results.
It indicates the address family returned by the service, either IPv4 or IPv6.
Yes. The hostname is extracted from http or https URLs. Addresses in mailto links are ignored.
No. Network access is required to resolve names, query geolocation, and load map tiles.
It is the PTR record found via reverse DNS. Not all addresses publish one and many use generic values.
You can copy or download a CSV of visible fields and a prettified JSON payload of the full response.
This page makes direct calls to third‑party services. Usage is subject to those providers’ terms.