| Your public IP | 216.73.217.7 |
|---|---|
| IP version | IPv4 |
| ISP / Organization | Amazon.com (Amazon Technologies Inc.) |
| ASN | AS16509 Amazon.com, Inc. |
| Location (by IP) | United States (US) · America/New_York |
| IP intelligence | NO PROXY FLAG HOSTING/DATACENTER |
| Reverse DNS (PTR) | no PTR record |
| Network type (rDNS) | NO PTR no hostname published for this IP |
| Proxy headers | X-Forwarded-For 216.73.217.7, 104.23.197.39 |
| Accept-Language | — |
ASN, location and flags via ip-api.com, cached for six hours per address — nothing is stored beyond that cache.
| Browser timezone | — |
|---|---|
| Browser languages | — |
A VPN changes your IP, not your browser. If your exit server is in another country, timezone and language still reveal where you really are — sites correlate exactly these signals. No pass/fail here: just check they match the story your VPN location tells.
About the VPN Leak Test
The VPN Leak Test answers the question most leak testers skip: is a VPN even active? The verdict at the top combines a server-side network fingerprint — ASN proxy and hosting flags plus reverse-DNS classification — with the browser-side result, and only reports “protected” when VPN indicators exist and the measurable leak channels are clean. Without that first step, “no leaks found” is meaningless: an unprotected line has nothing to leak. Test 1 lays out the raw HTTP-layer evidence, Test 2 runs the actual WebRTC leak check locally in your browser by comparing every STUN-exposed address against your HTTP IP, and Test 3 surfaces the soft signals — timezone and language — that no VPN changes.
Run it twice — once without and once with your VPN — and the difference tells you exactly what a website can and cannot see. For deeper address digging use the IP & Reverse DNS tool, and check your resolver setup with the DNS Lookup. Nothing on this page is stored: the analysis happens per-request in memory, the WebRTC test runs entirely in your browser, and the one external call — an anonymous ASN lookup of the IP at ip-api.com — is cached for six hours and then discarded.
Because saying "protected" would be a lie. Most leak testers only check whether WebRTC exposes a second address — and without a VPN there is trivially nothing to leak, so they show green on a completely unprotected line. This test first decides whether a VPN is active at all (network flags plus reverse-DNS fingerprint) and only calls a connection protected when VPN indicators exist and both leak channels are clean.
Two independent signals: an ASN lookup of your IP (via ip-api.com) that returns proxy, hosting and mobile flags, and a keyword heuristic on the reverse-DNS hostname. Commercial VPN exits sit in flagged datacenter networks; consumer lines carry ISP patterns like dsl, pool or dyn. It is a heuristic — exotic setups such as a VPN on a residential IP or a corporate static line can land in the "inconclusive" bucket, which is why every raw signal is shown in Test 1.
WebRTC lets browsers connect peer-to-peer for calls and video. To do that, it asks a STUN server "what is my address?" — and that request can bypass some VPN configurations. If the answer differs from the IP your VPN presents over HTTP, any website running three lines of JavaScript can read your real address. That comparison is exactly what this test performs, locally in your browser.
It depends on what that IP is. With a VPN active it means both channels show the VPN address and nothing extra is exposed — good. Without a VPN it simply confirms your real IP on both channels, which is why the verdict at the top factors in whether a VPN was detected at all. Rerun the test whenever you switch networks, browsers or VPN protocols.
Best option: enable your VPN's own WebRTC-leak protection (most good clients have it). Alternatively disable WebRTC in the browser (Firefox: media.peerconnection.enabled = false) or install an extension that restricts it. Chrome offers no full off-switch, only the "disable non-proxied UDP" policy.
Not fully — an honest DNS leak test needs its own wildcard DNS infrastructure with logging resolvers, which a normal web page cannot replicate. This page covers the two leaks a website can genuinely measure: your visible IP with its network fingerprint, and WebRTC exposure. For DNS, check that your VPN client has its own DNS servers configured and its leak protection enabled.
ISPs name consumer lines with patterns like dsl, pool or dyn, while VPN endpoints sit in datacenters whose networks carry hosting and proxy flags. Websites use the same signals: a datacenter fingerprint is a strong hint you are on a VPN — good for privacy, but also why some sites show you more captchas.