MyIPScan
edge · browser request current browser signal

Your IP, plainly explained.

A current browser request lookup of your IPv4/IPv6, ISP, ASN, and approximate location signal, processed to display the result in your browser. Public IP visibility is normal for websites and is not automatically a leak.

Reading at the edge
Checking public IP...
Location Network Version User-agent
browser request check
Exposure estimate and receipt limits

IP context matters. Compare before and after VPN or network changes when you are checking routing expectations. Receipt exports use safe categories and remove raw IP address, exact city, and full user-agent values. Read the methodology.

See what Safe Copy includes before sharing or saving a result.

Want the full picture? Run the Privacy Exposure Report.

Combine IP, WebRTC, IPv6, DNS leak, fingerprint, user-agent, and related privacy signals in one report.

Run report Scan website Check email exposure

Quick answer

  • Country, approximate city, ISP — yes, visible to every site you visit
  • Your name, exact home address, what you type — no
  • VPN connected? Sites usually see the VPN exit IP for browser traffic routed through that VPN
  • Mobile/CGNAT can shift cities by hundreds of km — that's expected

What you see on this page

Data typeExampleMeaningVisible to websites?
IPv4203.0.113.7Common 32-bit address formatYes
IPv62001:db8::1Modern 128-bit format; may co-exist with IPv4Yes
Location signalCountry → City (approx.)Estimated from provider dataYes
ISP / ASNAS12345 (Example ISP)Identifies provider networkYes
User-AgentChrome on WindowsBrowser string for compatibilityYes

How it works

  1. Your provider assigns a public IP to your router or gateway (devices at home use private IPs).
  2. Sites see the public IP and look it up in one or more geolocation databases for country/city and ISP/ASN.
  3. Different networks (Wi-Fi vs mobile/VPN) can show different IPs and locations — that's expected.

Accuracy & privacy notes

  • IP geolocation is approximate. It can resolve to an ISP hub or gateway rather than your exact place.
  • VPN/proxy purposely shows the exit server location (by design); mobile/CGNAT can shift cities.
  • No personal name or street address can be derived from an IP alone.

Verify IPv4/IPv6 and common leaks

  1. Run the VPN Leak Test to combine IP, DNS, WebRTC, IPv6, and browser signals.
  2. Run DNS Leak Test to review common DNS exposure signals.
  3. Run WebRTC Leak Test to check whether your browser exposes IP candidates.
  4. Run IPv6 Leak Test if your provider supports IPv6 and you want to compare both stacks.
  5. Read the Methodology to understand what these browser diagnostics can and cannot prove.

Learn more

Check my browser/privacy

What this checks

The public IP route, IP version, approximate network owner, ASN, rough location context, and browser request details visible in this session.

Limits

What this cannot check

It cannot identify your exact home address, inspect every app, certify anonymity, or prove that a VPN, ISP, device, or account is safe.

Read results

How to interpret results

A good result means the visible IP and network owner match the route you expected, such as your normal ISP or a VPN exit, with no unexpected location or ASN change.

Warnings

What a warning means

A mismatch may mean a VPN, proxy, mobile carrier, CGNAT, office network, CDN, or geolocation database is changing how the route appears.

Fix path

What to do next

Compare the IP result with DNS, WebRTC, IPv6, and fingerprint tests before deciding whether a routing setup needs attention.

Retest

When to retest

Retest after connecting a VPN, switching networks, toggling mobile data, changing browser profiles, or updating DNS and IPv6 settings.