Instant public IP view
See the IPv4 or IPv6 address websites can actually see.
See what websites can see about your connection: public IP, rough location, ISP, ASN, and privacy clues in one place. Run free diagnostics, understand the result, and decide what to fix next.
See the IPv4 or IPv6 address websites can actually see.
Run DNS, WebRTC, proxy, and blacklist checks from one place.
Understand ISP, ASN, location hints, and routing clues quickly.
Move from a symptom to a fix with practical tools and guides.
Your public IP is visible right now. If you want websites to see a VPN server instead, use a provider with leak protection and verify the result after connecting.
Checks and privacy next steps
Enter a domain name to look up its records including A, AAAA, MX, TXT, NS, and CNAME records.
Every time you visit a website, your device shares its public IP address with that site. This is how the internet routes data back to you, but it also means anyone running a server can see your IP. From that single number, observers can typically determine your approximate city or region, your ISP and ASN, and whether you are connecting through a VPN, proxy, or Tor exit node.
Your IP alone does not reveal your exact street address or identity, but combined with other signals like browser fingerprinting, cookies, and DNS queries it contributes to a surprisingly detailed profile. That is why checking your IP is the first step in any privacy audit. Once you know what is visible, you can decide what to protect.
Most connections still use IPv4 (e.g., 203.0.113.45), but IPv6 adoption is growing. IPv6 addresses are longer and can sometimes leak your real location even when a VPN is active. Learn the difference.
Your router has a public IP visible to the internet and assigns private IPs (like 192.168.x.x) to devices on your local network. Only the public IP appears in the result above. Read more about public vs private IP.
If you are using a VPN, the IP shown should belong to your VPN provider, not your ISP. If it still shows your real ISP, your VPN may be leaking. Verify your VPN.
Even with a VPN, DNS requests or WebRTC connections can bypass the tunnel and expose your real IP. Run a DNS leak test and WebRTC leak test to be sure.
If you want the clearest next steps after checking your result, move through the IP/privacy path: read why your IP location can look wrong, learn what someone can actually do with your IP, compare public vs private IP, and then decide how to hide your IP.

Carrier-grade NAT prevents inbound connections before they reach your router. Check WAN vs public IP and fix it with public IPv4, IPv6, or a reverse tunnel.

Learn the most common reserved IP ranges: private IPs, CGNAT, loopback, link-local, and documentation blocks.

Are VPNs legal in 2026? The Utah VPN law, age-verification rules, where VPNs are banned, and what stays perfectly legal explained for normal users.
Pick the path that matches your goal, from fixing a strange result to understanding the networking basics behind it.
Start with the symptom that sent you here.
Build a clearer mental model of what you are seeing.
Reduce exposure and harden the parts that matter most.
Jump into the deeper tools when you need exact answers.