See the public IP address the internet sees for your connection, its approximate location and ISP — plus the browser, screen and local-network details this device reports. Free, no sign-up — the browser and device details are read locally on this device; your public IP is looked up over the network, as explained on this page.
What is “my IP address”, exactly?
Every device on a network needs an address so replies can find their
way back, and you have two that matter. Inside your home or office
network your router hands out private addresses —
the familiar 192.168.x.x and 10.x.x.x
ranges — which are only meaningful behind that router. On the
internet itself your whole network appears as one
public address, assigned by your ISP to the router,
and shared by every phone, laptop and TV behind it. The big number
at the top of this page is that public address: it is what every
website, mail server and game lobby you connect to sees, logs and
bases its location guesses on. The local-network section shows the
other side of the story — the private addresses of this device,
which no website can see (ours included) unless the browser itself
reveals them.
How this page works
Every other tool on this site is 100% local, and most of this page
is too — but a public IP address is the exception that proves the
rule, so the mechanics deserve stating plainly. The public
block sends one ordinary HTTPS request from your browser to
a lookup service, ipwho.is (falling back to
ipapi.co). The service simply reports the address the
request arrived from, plus the location and network its database
associates with that address. It necessarily learns the address it
reports, your browser's user-agent string and standard connection
metadata; its privacy policy governs that request. This site runs
no server in between: we do not receive, store or log your address.
The browser and device block is filled entirely
from APIs your browser exposes to any page — user-agent, screen
geometry, language and time-zone settings, hardware hints — read on
your device and sent nowhere. The local-network
block uses WebRTC with an empty server list, which makes
the browser enumerate its own network interfaces without contacting
anyone; the addresses it yields never leave the machine.
How to use this page
- Read the public address first, then its location and ISP: that trio is your identity as far as the open internet is concerned.
- Toggle your VPN (if you use one) and press Re-check public IP. The before/after difference shows exactly what the VPN changes — and the local blocks, which do not change, show what it doesn't.
- Compare the public address with the local-network addresses below it. If a guide or support forum asks for “your IP”, they almost always mean the public one; the 192.168-style one only helps someone already inside your network.
- Use the browser block when a bug report asks for your setup: the user-agent string at the bottom is the exact text support teams want, copy-paste ready.
Why the location is approximate — three typical results
Home broadband, no VPN: country and region are
usually right; the city is often the ISP's regional hub rather than
your suburb, and the ISP name is the fastest confirmation that the
result is really your connection. VPN switched on:
address, city and ISP all describe the VPN provider's exit server —
the correct answer to “what does the internet see?”, and the wrong
answer to “where am I?”. Office or mobile network:
large organisations and carriers route many users through a few
gateways, sometimes in another state (and the address may be a
CGNAT shared address — the page labels the range type so you can
tell). In all three cases the address itself is exact; only the
database's idea of where that address lives is fuzzy.
Frequently asked questions
Why does this page make a network request when every other tool here is local-only?
Because a public IP address cannot be read locally — it is assigned by your network and only exists as seen from the outside. No browser API exposes it, so the page asks a public lookup service (ipwho.is, with ipapi.co as fallback) "what address are you seeing?" and shows the answer. That service receives your public IP (it has to — that is the question), your browser's user-agent string and standard HTTPS connection data, and its own privacy policy governs that request. This site has no server in the loop: nothing is sent to us, stored, or logged by us. Every other block on this page — browser, screen, time zone, local addresses — is read locally and never leaves your device.
Why is the location wrong, or in a different city?
The location is not measured; it is looked up. IP geolocation databases map address ranges to the city where the ISP registered or typically routes them, and their accuracy is usually "right country, plausible region, approximate city". Mobile carriers route whole regions through a few gateways, corporate networks exit in another state, and a VPN shows the exit server's location instead of yours. Treat the result as a hint about how the internet sees your connection, not as your address.
What is the difference between the big IP above and the 192.168.x.x address on my router?
They are your two addresses on two different networks. The 192.168.x.x address is private — it exists only inside your home or office network, assigned by your router. The address at the top of this page is public — it is your router's address on the internet, shared by every device behind it, and it is what every website you visit sees. Our guide to public vs private IP addresses explains the split and why it exists.
I'm using a VPN. Whose IP address is shown?
The VPN's. From the internet's point of view your traffic leaves through the VPN provider's exit server, so the lookup shows that server's address, location and ISP — which is precisely what this page is useful for checking. Toggle the VPN off, press Re-check, and the difference between the two results is exactly what the VPN changes (and what it doesn't: the local blocks below, such as your time zone and WebRTC addresses, are read on your device either way).
Why does the local-network section show a strange name ending in .local, or nothing at all?
Modern browsers deliberately mask your real local addresses behind random mDNS names ending in .local, because the real ones were being used to fingerprint people. The section lists the addresses your browser is willing to reveal: on some setups that is the genuine 192.168.x.x or 10.x.x.x address; on others only the masked name, which this page filters out, leaving an honest "not revealed". A masked result is your browser's privacy feature working, not a fault.
Do you store my IP address or fingerprint my browser?
No. This site has no accounts and no server-side storage of visitor data — the page is static files, and the details below are computed in your tab and discarded when you close it. The one external request goes from your browser directly to the lookup provider (ipwho.is or ipapi.co) to answer your IP question; we never see it. The same list of browser details that this page displays openly is, however, a good illustration of what any website can read about a visitor — which is why browsers keep restricting it.
Dev