What's My IP
See your public IP address and what your browser reveals.
How to use the What's My IP
- Open the page — your details load automatically.
- Read your public IP and browser information.
- Nothing here is stored or logged.
About the What's My IP
Your browser cannot see its own public IP address, so this tool asks a server to report it back. Our own tiny PHP endpoint reads the address from your request — REMOTE_ADDR, or the validated first hop of X-Forwarded-For when the site sits behind its host’s proxy — and also returns the language your browser advertises and your full user-agent string. Nothing on our side is stored or logged.
A single web request only ever reveals the address for the one protocol it travelled over, so to show both your IPv4 and your IPv6 the page makes two extra lookups to ipify.org, a long-running free service — one endpoint that answers only over IPv4 and one that prefers IPv6. That means those two checks send your IP to ipify as well as to us; it is the standard way every dual-stack “what’s my IP” tool works, and if ipify is unreachable the page quietly falls back to the single address our own server saw. If a protocol shows “not detected”, your connection simply is not using it — many home connections are still IPv4-only, and some mobile networks are IPv6-first.
This is your public, network-facing IP as seen by servers, not your device’s private LAN address, and it can be shared through carrier-grade NAT or replaced entirely by a VPN or proxy — a quick way to confirm a VPN is actually active. It does not reveal your street address, at most a rough region, which this tool does not look up. To break down a web address instead of an IP, try the URL parser, or fingerprint some text with the hash generator.
Frequently asked questions
How does it find my IP address?
Our own server reads the address from your request and sends it back, and the page loads it automatically. To show both IPv4 and IPv6, it also queries ipify.org, because a single request only reveals the protocol it used.
Why does it use ipify.org as well as your own server?
One HTTP request can only show the address for the protocol it travelled over. Showing both your IPv4 and IPv6 needs one lookup forced over each, and ipify provides free endpoints for exactly that. Those two checks do send your IP to ipify.
Why is one of my addresses shown as "not detected"?
Because your connection is not using that protocol. Many home and office connections are still IPv4-only, so no IPv6 is found; some mobile networks are IPv6-first, so no public IPv4 is found. That is normal, not an error.
Is this my private (LAN) IP?
No. It is your public, network-facing IP as seen by servers. Your device’s private LAN address, often something like 192.168.x.x, is different and is not visible from the internet.
Does this reveal my exact location, and do you store it?
No to both. An IP maps to a rough region at best, and this tool does not even look that up. Our own endpoint stores nothing and returns a no-store header; ipify is queried only to read your address for the dual-stack check.