Internet Protocol (IP) Geolocation Finder

{{ badge.label }}: {{ badge.value }}

IP address, domain, or URL:

Use one target such as 8.8.8.8, 2001:4860:4860::8888, or example.com.

This helper contacts a public IP-detection service only after you select it.

Address preference:

The other address family is used as a fallback when the preferred record is absent.

Reverse DNS evidence:

Off is neutral and avoids the additional DNS request. PTR names are supporting evidence, not identity proof.

Request timeout:

The neutral default is 9000 ms; accepted range is 2500–15000 ms.

Field	Value	Evidence	Copy
{{ row.label }}	{{ row.value }}	{{ row.source }}

{{ item.title }}{{ item.detail }}

Open OpenStreetMap Open Google Maps

IP geolocation is approximate provider evidence. It can reflect an ISP, VPN, proxy, privacy relay, or carrier gateway rather than a device's physical position.

A city attached to an Internet Protocol (IP) address is a database attribution, not a device measurement. IP geolocation providers combine routing, registry, network-owner, and observed location evidence to associate address ranges with places. The result usually describes where a network block is used or managed, which may be far broader than one person's position.

That distinction changes how a result should be used. A home connection may appear near an internet service provider hub. Mobile traffic can leave through a carrier gateway shared by many subscribers. A VPN, corporate proxy, privacy relay, cloud server, or public resolver can place the visible address in another city or country entirely.

IP address: The public routable address being attributed. A direct IPv4 or IPv6 input is looked up as entered.
ASN: The Autonomous System Number associated with the network announcing the address. It helps identify the network operator, not the individual user.
PTR record: An optional reverse Domain Name System (DNS) name published for an address. It can hint at network purpose but does not prove ownership or trust.
Coordinates: Approximate latitude and longitude supplied by the geolocation provider. A precise-looking map pin does not imply GPS accuracy.

A hostname or URL adds a DNS decision before geolocation. The host can have both IPv4 and IPv6 answers, several addresses in one family, or responses that change with time, resolver, and client location. The address selected for one lookup is a snapshot. It may not be the address used by another visitor or by the same service later.

Location becomes more useful when read beside network evidence and time. A country mismatch may justify another look at a login, but the ASN may reveal an expected VPN or cloud provider. A familiar city is weak evidence when the address was shared. Timestamped application, authentication, firewall, or provider logs are needed before associating an address with an event.

The safe conclusion is narrow: IP geolocation can supply approximate geographic and network context for one resolved public address. It cannot establish a street address, identify a person, prove who controlled the address at a past moment, or replace a provider record tied to the relevant timestamp.

How to Use This Tool:

Choose the exact public target whose network context you need, then preserve the resolved address with the result.

Enter one public IPv4 address, IPv6 address, hostname, or HTTP/HTTPS URL. Use Use my IP only when you intend to contact a public address-detection service.
For a hostname or URL, select IPv4 first, then IPv6 or IPv6 first, then IPv4. A direct IP is never changed by this setting.
Turn on Reverse DNS evidence only when a PTR name would help the investigation. Set the per-request timeout between 2500 and 15000 milliseconds; 9000 milliseconds is the neutral default.
Run the lookup and record the Resolved IP. Read the location, ASN, organization, and optional PTR together, then compare that address with logs from the same time window.

Interpreting Results:

The location summary is approximate provider context. Country, region, city, postal code, timezone, and coordinates may be missing or may describe a network facility rather than the user. Do not let the map's visual precision outweigh that limitation.

Use the resolved IP as the anchor for later checks. A hostname can resolve differently on another run.
Use ASN and organization to identify the announcing network, then confirm ownership through an ASN or WHOIS source when attribution matters.
Treat a PTR name as supporting evidence. No PTR is common, and a returned name does not prove current control, identity, or safety.
Read evidence coverage as field completeness, not confidence or accuracy. A category can be 100% complete while its location remains approximate.

Technical Details:

IP geolocation begins only after one valid public IPv4 or IPv6 address is available. Hostnames and URLs are reduced to a hostname, resolved through public DNS-over-HTTPS services, and then passed to IPinfo for location and network fields. Private, loopback, link-local, and multicast inputs are rejected because public geolocation has no meaningful answer for them.

Lookup Core:

IP geolocation lookup stages
Stage	Input	Decision and result
Classify target	IP address, hostname, or HTTP/HTTPS URL	Keep a direct address or extract and validate one public hostname.
Resolve hostname	Validated hostname and address preference	Try the preferred A or AAAA family first through public resolvers, then fall back to the other family when no usable public answer is returned.
Look up network context	One resolved public address	Request IPinfo fields for country, region, city, postal code, timezone, coordinates, ASN, and organization.
Request reverse DNS	Resolved address, when enabled	Construct the IPv4 `in-addr.arpa` or IPv6 `ip6.arpa` name and request a PTR answer.
Normalize evidence	Provider and resolver responses	Validate coordinates and address syntax, remove a trailing dot from PTR names, separate ASN from organization text, and label missing fields.

Evidence Coverage Formula Core:

Coverage measures how many declared fields were returned within each evidence category.

C = \frac{a}{t} \times 100 %

a is the number of nonblank fields returned and t is the declared field count for that category. Target resolution uses three fields; location context uses four; coordinates and network owner use two each; reverse DNS uses one.

The percentage is stored without rounding and rendered for comparison. It says nothing about geographic precision, database age, resolver representativeness, or whether the address belonged to the same customer at another time.

Limitations, Privacy, and Accuracy Notes:

A lookup sends network identifiers to outside services. The exact requests depend on the input and optional checks.

A direct IP address is sent to IPinfo. A hostname or URL host is first sent to public DNS-over-HTTPS resolvers, and the selected address is then sent to IPinfo.
Reverse DNS sends the address-derived reverse name to a public resolver. Use my IP separately contacts a public IP-detection service.
If a direct provider response cannot be read, a server-assisted fallback may relay the resolved IP for the same lookup. No retention promise is shown by the tool, so do not submit a target that your policy forbids sharing with these services.

Provider data can be stale or coarse and does not include an accuracy radius or observation timestamp in this result. VPNs, proxies, relays, carrier gateways, anycast services, and cloud networks can shift the apparent place. Use timestamped logs and authoritative provider records for consequential attribution.

References:

IP Geolocation API Data, IPinfo.
JSON API for DNS over HTTPS, Google Public DNS.
How to get an IP address from a hostname in Python, Simplified Guide.
How to check PTR records with dig, Simplified Guide.