Account

What new tool do you want?

Developer Tools

What Is My IP Address?

See your public IPv4 and IPv6 address, approximate location, internet provider and what else websites can see about your connection — instantly.

How to use

  1. 1Open the page — your IP address appears automatically.
  2. 2Check the location and provider details.
  3. 3Using a VPN? Confirm it shows the VPN's address.

Frequently asked questions

Can websites see my exact address?

No. An IP address usually locates you to the city or region of your internet provider, not your home.

Why don't I have an IPv6 address?

Your internet provider or router may not support IPv6 yet. Everything still works over IPv4.

Is my IP stored?

No — the lookup happens in your browser and we don't keep it.

Three sources, queried for redundancy

The page calls /cdn-cgi/trace — a diagnostic endpoint Cloudflare exposes on every site it fronts, reporting the visible IP along with the HTTP version, TLS details and which Cloudflare data center handled the request — and in parallel calls api.ipify.org and api64.ipify.org for the IPv4 and IPv6 addresses specifically. It then prefers ipify's IPv4 result, falling back to Cloudflare's trace if that's blocked, since ad blockers and privacy extensions sometimes block one third-party endpoint but not another. Only once an address is settled does it call ipwho.is for the approximate location shown underneath.

Why the IPv6 box is sometimes empty

IPv6 adoption depends on both your ISP and your router supporting and enabling it — plenty of home and mobile networks still only hand out an IPv4 address. When that's the case, the IPv6 card explicitly states 'Not available — your network doesn't use IPv6' rather than showing a blank, which is a router/ISP configuration fact, not something broken on this page or your device; IPv4-only connections work completely normally everywhere IPv6 isn't required.

The browser panel isn't a network lookup at all

The 'What websites can also see' section — user agent, language list, time zone, and screen resolution with device pixel ratio — comes straight from navigator, Intl.DateTimeFormat and screen in your browser, with zero network requests involved. It's shown alongside the IP specifically to make the point that IP address is only one of several signals an ordinary website can read passively; fonts, canvas rendering and other characteristics (fingerprinting) can narrow identity further without ever touching your IP.

Worked example: confirming a VPN is actually active

Connect to a VPN with, say, an Amsterdam exit server, then press 'Check again.' If the VPN is routing traffic correctly, ipify now returns the VPN provider's IP rather than your home ISP's, and the location card updates to show Amsterdam with an ISP name belonging to the VPN or hosting provider — not your actual internet provider. If instead the location and ISP still match your real connection, that's a concrete sign of a VPN leak (a DNS leak or a split-tunneling misconfiguration), which is the main practical reason to run this check rather than trusting the VPN app's own 'Connected' indicator.

The Connection line names an actual Cloudflare data center

When this site is served through Cloudflare, the trace endpoint also returns which protocol handled your request (http/2 or http/3), the TLS version in use, and a three-letter colo code identifying the exact Cloudflare data center that answered — shown as something like "h2 · TLSv1.3 · via Cloudflare AMS" for a request routed through Amsterdam. That colo code is a side effect of how Cloudflare's global network works, not a property of your own connection: it changes if Cloudflare's routing sends you to a different nearby data center on a later visit, which is also why refreshing occasionally shows a different colo even though your actual IP and location haven't moved at all.

Related tools

More: Developer Tools