Where am I? Two ways your location gets figured out
Ask a website "where am I right now?" and there are really only two honest answers it can give. One is a rough guess based on your IP address — usually good enough to name your city and internet provider. The other is a precise fix from your browser's Geolocation API, which can pin you to within a few metres, but only after you say yes. This tool shows both side by side so you can see how far apart they land.
The two methods don't compete. They answer slightly different questions, they fail for different reasons, and knowing which is which saves a lot of confusion when a map drops a pin in the wrong town.
IP-based location: the network's best guess
Every device on the internet has an IP address, and every IP address belongs to a block that some organisation registered with a regional registry like RIPE or ARIN. Geolocation databases start from those registration records, then layer on routing data, ISP corrections, and crowd-sourced sightings to estimate where each address is actually used. When you load this page, the server looks your IP up in one of those databases and reads back a country, a region, a city, and the name of your ISP.
It's quick and it needs zero permission — the IP travels with every request you make. The trade-off is precision. Country-level results are nearly always right, north of 99% in practice. City-level is where it gets shaky: depending on the country and the network, the right city comes back somewhere between a fifth and three-quarters of the time. The location you see is often your provider's registered address, not your living room.
Why IP location is sometimes plain wrong
A few things throw it off, and none of them mean anything is broken:
- Mobile carriers. Phone traffic usually funnels through a handful of central gateways. Your IP might resolve to a city hundreds of kilometres from where you're standing because that's where the carrier's gateway lives.
- VPNs and proxies. These replace your IP with the server's. If your VPN exits in Amsterdam, the database says Amsterdam — which is exactly what you're paying it to do. Our IP address checker shows the address sites currently see for you, VPN included.
- Corporate and campus networks. Big organisations often route everyone through one location. A remote worker can appear to sit at company headquarters.
- Stale databases. IPv4 addresses get sold and reassigned, and the various databases update on their own schedules. A freshly reallocated block can show its old country for weeks.
Browser geolocation: precise, but opt-in
The browser's Geolocation API is a different beast. On a phone it leans on actual GPS, accurate to roughly ten metres in the open. On a laptop without GPS it triangulates from nearby Wi-Fi networks and cell towers, which typically gets within twenty to a hundred metres. That's the difference between "your neighbourhood" and "your building."
Because that's genuinely sensitive, it's locked behind a permission prompt. The first time a page asks, your browser pops up a request — Allow or Block — and nothing happens until you choose. Decline, and the API simply returns an error; the page can't sneak around it. Allow, and the position is read once and handed to the page in your browser. This tool doesn't store it or send it anywhere; the readout you see is computed locally and gone when you close the tab.
That opt-in design is the whole point. IP location is passive and always available; precise location is something you grant deliberately, per site, and can revoke any time in your browser settings.
What location is actually used for
Most of the time location is doing quiet, useful work. Weather apps need to know your city to show the right forecast. Maps use the precise fix to centre on you and route you home. "Restaurants near me" and store locators rely on whichever signal they can get. Streaming and shopping sites apply regional pricing or licensing from your IP. Banks and payment processors check whether your IP country matches your account as a basic fraud signal — which is one reason a VPN occasionally trips a verification step.
None of that requires your street address. A coarse IP estimate covers weather and content regions; the browser fix only comes into play when an app genuinely needs precision, like turn-by-turn navigation.
A note on privacy
It's worth being clear about what each method exposes. Your IP is visible to every server you connect to — that's how the internet works — so IP-level location isn't really a secret, just imprecise. Precise location is the part worth guarding, and the permission prompt is your control point. Grant it only where you need it, and check your browser's site permissions now and then to clear out grants you've forgotten. If you also want to see which servers your traffic talks to, the DNS lookup tool is a good next stop.
Frequently asked questions
Why does my IP location show the wrong city?
Usually because the location belongs to your internet provider, not you. Mobile carriers route traffic through central gateways, corporate networks funnel everyone through one site, and geolocation databases can lag behind when addresses get reassigned. A VPN will also show its server's city instead of yours.
How accurate is IP geolocation?
Country level is almost always right, around 99% or better. City level is far less certain, landing correct roughly 20% to 75% of the time depending on the country and network. Think of it as an approximate region, not a precise spot.
How precise is browser GPS location?
On a phone with GPS, often within about ten metres in open conditions. On a laptop it falls back to Wi-Fi and cell-tower triangulation, which typically gets you within twenty to a hundred metres — still far tighter than an IP estimate.
Does this tool track or store my location?
No. The IP estimate is read from your connection, and the precise location, if you grant it, is computed in your browser and shown to you only. Nothing is logged or sent on, and it's gone when you close the tab.
Can a website see my exact location without asking?
Not the precise one. The Geolocation API always requires permission, and if you decline it just returns an error. A site can still estimate your rough area from your IP, since that's part of every connection, but it can't reach GPS-level precision without your explicit consent.
How do I stop a site from seeing my location?
Block the permission prompt, or revoke an existing grant in your browser's site settings under privacy or permissions. To change the IP-based estimate as well, a VPN or proxy will make sites see a different address and region.