What Is My IP
See your public IP address from several independent sources at once — IPv4, IPv6, and our own Cloudflare edge — so you can spot a VPN or proxy split-tunnel rule the instant the page loads. Nothing to click, no sign-up.
What is the What Is My IP tool?
What is my IP? This page answers that question the instant it loads, and it goes one step further than a plain lookup: it asks several independent sources at the same time and shows you what each one sees. You get your public IP address — the single address the rest of the internet uses to send replies back to your connection — from our own Cloudflare edge, an IPv4-only source, an IPv6-only source, and one extra comparison source, each on its own line with its own copy button.
Seeing the same question answered by different servers is the whole point.
A connection often has two addresses at once: an IPv4
address written as four numbers separated by dots (for example
203.0.113.45) and an IPv6 address written as
groups of hexadecimal digits separated by colons (for example
2001:db8::1). On top of that, if you run a VPN or proxy with a
split-tunnel rule — some traffic routed through the proxy, some sent direct —
different destinations can show different exit IPs. Comparing
sources side by side is how you confirm those rules are actually working.
How to use it
- Open the page. Every source starts loading automatically within a second — no button to press.
- Read each row: the source name, the IP it saw, and whether it is IPv4 or IPv6. A source that fails or has no IPv6 says so instead of breaking the others.
- Compare the rows. If a proxy or VPN split-tunnel rule is in effect, some sources will show your real address and others will show the proxy exit — that difference is the signal you are looking for.
- Tap the copy button on any row to put that exact address on your clipboard, ready for a firewall rule, an allowlist, or a support chat. Tap "Refresh all sources" to re-check after toggling a VPN.
The method behind it
A browser cannot read its own public IP — JavaScript only sees the local network address your router hands out, not the address the outside world uses. The only way to learn the public value is to ask a server that received your request to echo it back. This tool does that four times, in parallel, against deliberately different endpoints so you can compare them.
Our own source, /api/ip, runs at Cloudflare's edge and reads the
cf-connecting-ip header plus the rough country and city Cloudflare
derives from it, with Cache-Control: no-store. The IPv4 source
(api.ipify.org) is reachable only over IPv4, so it reports your
IPv4 exit; the IPv6 source (api6.ipify.org) is reachable only over
IPv6, so it reports your IPv6 exit, or says no IPv6 is available if your network
has none. The extra comparison source (api.ip.sb) is a fourth,
independent vantage point.
Why do different sources sometimes show different IPs? Because each request can take a different path out of your machine. A split-tunnel proxy rule may route the connection to one source through the proxy (showing the proxy's exit IP) while another source is contacted directly (showing your real IP). One source may be reached over IPv6 and another over IPv4. That is precisely the behaviour this multi-source view is built to reveal.
Examples
- You set a proxy rule so that only certain sites go through a VPN. You open this page: the IPv4 source shows your real home address while the comparison source shows the proxy's exit — proof the split-tunnel rule is routing the right traffic.
- A developer needs to allowlist their machine on a managed database. They read the exact IPv4 address from the IPv4 row, tap copy, and paste it straight into the database's allowlist.
- A user on home Wi‑Fi sees an IPv6 address in the IPv6 row and an IPv4 address in the IPv4 row at the same time — a quick way to see their connection is dual-stack.
- Someone behind a VPN that should cover everything sees the same proxy exit IP across every source — confirming there is no leak and all traffic is going through the tunnel.
Common use cases
- Verifying a VPN or proxy split-tunnel rule: compare what different sources see to confirm the right traffic is going through the proxy and the rest stays direct — the same job people use ip111-style multi-source pages for.
- Confirming a VPN is actually on: if every source still shows your real address, the tunnel is not active or is leaking.
- Configuring an allowlist: read the exact IPv4 or IPv6 value a server will see and paste it into a firewall, database, or game-server rule.
- Troubleshooting your connection: see at a glance whether your network is IPv4-only, IPv6-only, or dual-stack, and which address each service receives.
Why use this one
Most "what is my IP" sites show a single number, bury it under banners, or quietly log every visitor for ad tracking. This one is different in three concrete ways. First, it is multi-source: IPv4, IPv6, our own edge, and a comparison source side by side, so you can actually verify proxy and VPN routing instead of guessing. Second, it is private by design — our own source reads your address once to show it to you and never logs or stores it, and every third-party source is clearly labelled with whose servers it touches. Third, it stays minimal and mobile-friendly: a clean list of sources, each with one-tap copy, and nothing else getting in your way.
It is part of a small "what is my…" set for checking what your browser and connection reveal. To see the exact identification string your browser sends, use What Is My User Agent; to check the display your device reports, use What Is My Screen Resolution.
Frequently asked questions
Why do different sources show different IPs?
Each request can leave your machine by a different path. A VPN or proxy split-tunnel rule may route the connection to one source through the proxy — showing the proxy's exit IP — while another source is reached directly and shows your real IP. One source may also be contacted over IPv6 and another over IPv4. Comparing the sources is how you confirm those routing rules are working.
Do you log, store, or sell my IP address?
No. Our own /api/ip source reads your IP once, at the edge, only so this page can show it back to you, and never writes it to a database or attaches it to an account. The third-party sources (ipify, IP.SB) receive your request the way any website does and each have their own privacy policies.
Why can't a website just read my IP with JavaScript?
JavaScript running in your browser can only see your device's local network address, not the public IP the rest of the internet sees. The public IP is added by your router and your provider on the way out, so only a server that receives your request can report it back — which is why this tool asks several echo servers for it.
Why does the IPv6 row sometimes say not available?
Not every network has IPv6. The IPv6 source is reachable only over IPv6, so if your connection is IPv4-only that request simply has no route and the row reports that no IPv6 is available — while the IPv4 and edge rows still work normally.
My IP here doesn't match what another site shows — why?
You may be connecting over IPv6 on one site and IPv4 on another, a VPN or proxy split-tunnel rule may be active for some traffic and not others, or another site may have cached an older address. Tap Refresh all sources to re-check what each source sees right now.