IP-based estimate
Your public IP points to a likely city, region, network owner, and routing footprint. It may reflect your ISP, VPN, mobile gateway, or company edge.
IP location, live map context, and optional device compare
What's my location?
See the approximate place websites infer from your connection, then compare it with precise device coordinates only when you choose.
Finding your network location
Automatic result
Locating your connection…
IP-based location is approximate and may reflect your ISP, VPN, or network gateway.
Public IP
Checking…
- Country
- —
- Local time
- —
- Network
- —
- Privacy signal
- Checking
Live map context
World locator
Only in this tab
Device location
- Coordinates
—- Distance from IP estimate
- —
Browser privacy check
What this page can see from your browser.
These signals are read and compared in this tab. They are not added to the location API request or the local lookup history.
- Time zone alignment
- Waiting for the IP result
- Language and IP country
- Waiting for the IP result
- Browser and platform
- Checking locally
- Privacy preferences
- Checking locally
- Connection type
- Checking locally
Optional VPN path check
Does WebRTC expose a different public IP?
Nothing runs until you press the button. The check contacts a Google-operated STUN server, modern browsers may mask local addresses with mDNS, and Safari or Firefox may report less detail.
Not run. Your normal HTTP public IP is the only path shown so far.
JavaScript is off, so browser-only time zone, language, connection, and WebRTC checks are not running. The privacy and limitation text below remains available.
How close is this to your real location?
Compare the estimate with what your device can report.
IP location is an estimate. It can identify a city or region, but not your precise device position.
Device location
Browser geolocation asks for permission only after you click. When available, it can use GPS, Wi-Fi, and local signals to get much closer to the device itself.
Why they differ
Carrier-grade NAT, hosted infrastructure, stale geolocation data, and privacy tools can make an IP estimate land far from where the device is actually standing.
Location readout
Where the IP points
Network and privacy
How the connection looks
Routing and evidence
What the provider reported
Reported signals
Quick actions
Every check stays on one page, one tap away.
Page-native actions only: anchors, sample lookups, privacy terms, and the live health endpoint.
My IP result
Jump back to the live result card and copy the current public IP in one click.
Open result IP lookupGo straight to the input field and run another public IPv4 or IPv6 query.
Open input Precise compareAsk the browser for device location and compare it with the network estimate on the same map.
Use GPS DetailsRead the routed prefix, network role, timezone, confidence, and evidence grouped below.
Read evidence Service healthOpen the live health endpoint used to verify the application is responding.
Open endpoint Privacy termsRead how IP-based estimates work here, where GPS stays, and what the map provider can see.
Open termsLearn more
Three practical ways to interpret the result before you overtrust it.
Location accuracy
Wrong city does not always mean wrong data.
An IP address often maps to the network edge that served you, not the room your device is in. That is normal for many residential, mobile, and hosted routes.
Read the live location evidenceDevice comparison
GPS and browser geolocation answer a different question.
If you need the device position instead of the network footprint, compare the map after pressing the precise-location button and granting permission.
Run the compare nowNetwork role
Public resolvers, VPNs, and cloud edges leave different clues.
The network, privacy, and routing groups help explain whether the address looks residential, shared, hosted, or otherwise different from a normal home line.
FAQs
Frequently asked questions about this location result.
How accurate is IP geolocation?
IP geolocation is usually accurate to a city or region and can be less precise. It reflects network registration and routing, not the exact device position.
Why is my IP location wrong?
Your public IP may belong to an ISP gateway, mobile carrier, company network, VPN exit, or cloud edge located somewhere other than your device.
Why does my IP show the wrong city?
Providers may map an address to a nearby routing hub, registration office, or stale database record. A wrong city does not identify your home or device location.
Does a VPN change my IP location?
Usually. Websites normally see the VPN exit IP and its approximate location instead of the public IP assigned by your local network.
How precise is city-level IP location?
A city label is an estimate, not a measured radius or street address. The dashed map range on this page is a client-side heuristic, not provider-reported accuracy.
Can IPv4 and IPv6 show different locations?
Yes. The two addresses can use different provider records, gateways, or routing paths, so their estimated cities and network details may differ.
Why do IP location websites disagree?
Services use different data sources, refresh schedules, confidence rules, and fallback methods. None of them can turn an IP address into a verified physical address.
Do you send my device coordinates to the API?
No. Device latitude, longitude, and accuracy stay in the current tab. OpenStreetMap receives requests for the visible map tiles needed to render the comparison.
Can I share an IP lookup?
Yes. Shared links include only the public IP query in the ?ip= parameter. They never include optional device coordinates or local lookup history.
What kinds of addresses are accepted?
Enter one public IPv4 or IPv6 literal. Hostnames, URLs, private ranges, CIDR blocks, and port numbers are intentionally rejected.
What should I use for a real physical location?
Use the precise-location button and your browser's geolocation permission. IP geolocation is not a substitute for GPS or a verified street address.
Does this page track or sell my lookups?
No. There are no ads or cross-site analytics. Successful explicit lookups can appear in local device history, which stores only the IP and time and can be cleared in one click.