spins.guru · location check

What your location looks like online

Any website you visit can estimate where you are. This page shows your state and country resolved three independent ways, side by side: from your device (GPS / WiFi / cell, if you allow it), from your IP address, and from the network edge via /cdn-cgi/trace. The verdict panel below flags when they disagree — a VPN, a country mismatch, or a state that doesn’t line up.

Nothing here is sent to us or logged. This page is static — there is no spins.guru server behind it. Everything runs in your browser, and we never receive or store any of it. How each lookup works ↓

iCloud Private Relay detected

Your traffic is routed through a relay (Apple Private Relay or a VPN), so the IP and edge cards may show a broader area, or a different city or region, than where you actually are — they often still land in the right region, but don’t treat them as exact. Your device card (if you allow it) is unaffected. How to turn it off ↓

Device

GPS / WiFi · state & country, most precise

Idle

IP address

Cloudflare edge · city, state, country

Querying IP geolocation…

Network edge

Cloudflare · country only, no city

Reading edge trace…

Awaiting signals

Run the device request and the IP/edge lookups to compute a consistency verdict.

Country

—

IP vs edge vs device

State / region

—

IP vs device

Connection

—

relay / VPN status

Device ↔ IP distance

—

needs your device location

If a result looks wrong

Each method estimates your location a different way, so each one is “wrong” for a different reason. Here’s what to check.

Device GPS / WiFi / cell

Most precise when it works — but only as good as the radios your device can see.

Says the wrong city/state: on a desktop with no GPS chip, the fix comes from WiFi positioning — your router’s location in the provider’s database. A recently-moved or brand-new router can place you at its previous address until the database catches up.
Very low accuracy (large ± metres): the OS fell back to cell towers or IP. Move near a window, enable WiFi (even without connecting), and retry.
Permission denied / blank: allow Location for this site in the browser, and in System Settings → Privacy & Security → Location Services (the browser must be enabled there too).
“State” is blank but coordinates show: the point fell outside the bundled US-state boundaries (e.g. you’re outside the US, or right on a coastline at low map resolution).

IP address network lookup

Coarse by nature — it locates your internet provider’s routing, not you.

Wrong city, right region: normal. IP databases resolve to your ISP’s nearest hub, which can be tens of miles away. The coordinates are a city centroid, not your address.
Completely wrong region/country: usually a VPN, proxy, or mobile carrier-grade NAT routing you through another city. Turn off the VPN and hit Refresh.
“Connection” says direct but you’re on a VPN: not every IP database carries a proxy flag, so a quiet VPN can read as direct. The distance check in the verdict catches most of those anyway.
Two providers disagree: expected — different IP databases are updated on different schedules. Neither is authoritative.

Network edge Cloudflare

What the server actually receives — country-accurate, no street detail.

Shows “Not on edge”: the page isn’t being served through Cloudflare. This column only works on a Cloudflare-fronted host (like geo.spins.guru); from file:// or a non-Cloudflare host it can’t resolve.
Country looks off: the edge sees your connection’s exit point. With a VPN it reflects the VPN’s country, not yours.
Different PoP than expected: the three-letter code (e.g. HNL, LAX) is the nearest Cloudflare data centre, not a precise location — it can be a neighbouring metro.
No state shown: by design — the edge trace only exposes country, never subdivision.

How websites estimate your location. There are only a few methods, and this page shows all of them. IP geolocation (used by nearly every site) maps your public network address to a city — coarse, but requires no permission. Browser geolocation (navigator.geolocation) asks your permission, then the operating system fuses GPS, nearby WiFi access points, and cell towers into a precise fix — a website receives only the resulting coordinates, never the raw WiFi list (browsers block that). Edge / server-side geolocation reads the country from the connection itself. A site can’t see more than these without software installed outside the browser. This page is a read-only view of what each method says about you, right now.