Inputs
Example
Open the tool to see the same-origin address evidence, then request Geo-IP/ASN or map details separately only if needed.
What is my IP?
Shows the canonical public address, observed peer, trusted-proxy evidence, browser metadata, and forwarded headers; Geo-IP/ASN and map requests require separate clicks.
Use it to see the canonical address, observed peer, trusted-proxy evidence, browser metadata, and forwarded headers received by this site.
The address the world actually sees
Behind a VPN, a corporate proxy, carrier-grade NAT, or a dual-stack connection, the question "what is my IP" stops having an obvious answer — different services may legitimately see different addresses for the same machine at the same moment. What this page shows is one precisely defined truth: the public address from which this site received your request, together with the request context that arrived with it.
Around that primary answer, the page assembles the metadata that makes it interpretable: the observed address family, the directly observed peer, trusted-proxy decision, forwarded-header claims, browser language, time zone, and user agent. Geo-IP, ASN details, and the map are separate click-gated actions, because the same-origin address answer does not require a third-party lookup.
Reading the context around one number
Take the primary IP first — it answers the common cases: is the VPN actually engaged, does the office exit where you think, which address should go into an allowlist. Then read the context around it. The IP version matters more than it looks: a dual-stack client can reach one service over IPv6 and another over IPv4, which produces exactly the confusing situation where two IP checkers disagree and both are right.
Use the deeper layers when the question warrants them. Forwarded headers show what proxies and CDNs claimed about the original client — displayed as claims, not as trusted identity, because that is what they are. Geo-IP places the address approximately; the ASN detail answers whose network it belongs to, which is often the operationally interesting fact. The map is last and loads only on click, as a separate Google Maps iframe — coordinates from Geo-IP data are neighborhood-accurate at best.
Enrichment on your terms
The primary answer comes from the same-origin /api/ip.php endpoint on page load. REMOTE_ADDR remains the directly observed peer; CF-Connecting-IP becomes primary only when that peer belongs to the verified Cloudflare network list and the claim is a canonical public address. X-Forwarded-For and other proxy claims are preserved but not trusted. Geo-IP/ASN is requested from api.ip.sb only after the Geo button, and the Google Maps iframe only after its own second opt-in. One request path observes one address family and does not prove dual-stack capability.
Frequently asked questions
Why does this differ from another IP checker?
Different checkers sit behind different CDNs, resolver paths, IPv4/IPv6 preferences, and proxy-header interpretations. Each reports what it sees; this page reports what this site saw for this request — with the surrounding context to explain disagreements.
Does this page expose local private addresses?
No. Modern browsers do not reveal local or private addresses to a web page. What you see is the public remote address from the web server's perspective — your router's outside face, typically.
When exactly is the map loaded?
Only after coordinates exist and you press the map button. The map is a separate Google Maps iframe, deliberately excluded from the initial page render so the basic check involves no maps provider at all.
How accurate is Geo-IP?
City-level at best, and honestly wrong at times: VPN exits, mobile carriers, corporate egress points, and recently reassigned prefixes all mislead it. Country is usually reliable; street-level precision is a myth.
What are forwarded headers, and can I trust them?
Entries like X-Forwarded-For that proxies and CDNs add to describe the original client. They are useful diagnostic claims, but any hop can set them to anything — which is why this page displays rather than trusts them.
Why do I see an IPv6 address when I expected IPv4?
Dual-stack connections prefer IPv6 when it is available end to end. Another service without IPv6 would see your IPv4 address — both observations are correct, each for its own path.