This is the kind of information that all the sites you visit, as well as their advertisers and any embedded widget, can see and collect about you.
Your IP addresses

Browser default:
Fallback:
Your IP addresses - WebRTC detection
If you are now connected to a VPN and you see your ISP IP, then your system is leaking WebRTC requests
DNS detection - Pending, please wait
If you are now connected to a VPN and between the detected DNS you see your ISP DNS, then your system is leaking DNS requests
Torrent Address detection
Activate
Geolocation map (Google Map) based on browser
Activate
(may prompt a user permission on the browser)
If the above map is your correct location and you don't want to allow this kind of tracking, ensure that geolocation feature of your browser is disabled or asking a permission, or install an extension that fake your position.
IP Address details
IP: 216.73.216.131
ISP: Amazon.com, Inc.
AirVPN: no No
ASN: 16509
Network: 216.73.216.0/22
Continent: North America (NA)
Country: United States United States (US)
European Union: no No
Registered country: United States United States (US)
Region: Ohio (OH)
City: Columbus
Time Zone: America/New_York
Latitude & Longitude: 39.9587 , -82.9987
Geolocation map (Google Map) based on IP Address
Activate
Accuracy Radius:20 KM
Last data update:Fri, 09 Oct 2026 21:25:10 +0000
Detected information
Your User Agent: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
What document you can accept: */*
What encoding you can accept: gzip, br, zstd, deflate
System information
(your browser, your language, your operating system, etc)
Screen information
(your display hardware)
HTTP Request Headers
Accept-Encoding: gzip, br, zstd, deflate
User-Agent: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)
Accept: */*
Host: ipleak.net

What are WebRTC leaks?

WebRTC can use STUN (Session Traversal Utilities for NAT) to learn your public IP. A VPN leak is when that public IP is your ISP address while you expect the VPN exit. Chromium browsers often hide the LAN address behind an mDNS name ending in .local — that is not a public leak by itself. An old browser tab can keep a pre-VPN address; test again in a new tab after connecting.

To disable WebRTC:

  • Mozilla Firefox: open about:config, set media.peerconnection.enabled to false.
  • Google Chrome / Chromium: there is no built-in full off switch. Use a trusted extension that disables WebRTC, or another browser. The old "WebRTC Network Limiter" extension is obsolete.
  • Safari: WebRTC does not expose extra IPs unless media permission is granted.

What are DNS leaks?

In this context, a DNS leak means name lookups leave the VPN tunnel. The resolvers listed above are the ones that answered our probes. If you are on a VPN and you see your ISP (or another unexpected) resolver there, DNS is not confined to the tunnel.

Why does my system leak DNS queries?

On Windows, each network interface can have its own DNS. The system process svchost.exe may send queries that ignore the VPN default gateway — a classic cause.

Other common causes today:

  • Browser DNS-over-HTTPS / DNS-over-TLS (Chrome, Firefox, and others) resolving outside the system VPN path.
  • Per-app DNS (Android Private DNS, some apps with their own resolver, split tunneling).
  • OS or router resolvers (for example systemd-resolved) that use a path outside the tunnel.
  • IPv6 DNS while the VPN only covers IPv4.

Should I be worried about a DNS leak?

If you do not want your ISP, or anyone who can monitor that path, to see which names your system resolves (and therefore which sites you visit), you must stop DNS leaks. In a hostile jurisdiction, or if that knowledge could harm you, fix it before you rely on the VPN alone.

How does torrent detection work?

To detect data from your torrent client we provide a magnet link to a fake file. The magnet contains an HTTP URL of a tracker we control, which records what the torrent client sends.

API

No key. Put json, xml, or php in the path. ipv4.ipleak.net and ipv6.ipleak.net force one address family. For DNS, keep the same 40-character session and use a new label on every request.

https://ipleak.net/json/
https://ipleak.net/json/8.8.8.8
https://ipleak.net/json/example.com
https://{session}-{label}.ipleak.net/dnsdetection/

Service available on IPv4 and IPv6, also on alternative ports: :8000 (IPv4,IPv6) and :62222 (IPv4,IPv6) (for detection of routing based on destination ports). Look at the forum for support and feedback.

Data partially based on MaxMind database. Results may be cached, refer to MaxMind for more accuracy.