Check Your Public IP, Latency and WebRTC Leaks

This page measures four separate things. The first section shows your public IP, the name of your internet provider, your country and an approximate city, exactly what any website sees the moment your connection opens. The second measures latency to three cloud edges: two Cloudflare servers and one Google server. This is not an ICMP ping; a real HTTP request is sent and the round trip is timed, three samples are taken and the best is shown. Because the TLS handshake sits inside that round trip, the number runs higher than a raw ping, which makes it useful for comparing the three destinations rather than for an absolute figure. The third section is a WebRTC leak test: to place direct calls, the browser advertises its own network addresses in ICE candidates, and some browsers expose the real address even behind a VPN, if a public address it reports matches your real IP, you get a leak warning. The fourth resolves a domain’s A records over DNS-over-HTTPS and lists each record with its TTL. All of these requests go from your browser straight to outside services (ipapi.co, ipify, ip-api.com, Cloudflare and Google), so those services see your IP; nothing passes through our server and no result is stored. If one of them is unreachable on your network, that row shows a dash or a cross and the rest of the page keeps working.

This tool runs entirely in your browser. No data is sent to any server.

How to use it

1. 1

   Open the page; the IP and approximate location fill in immediately (if they stay blank, check your connection or network filtering).

2. 2

   Look at the WebRTC and latency sections; latency takes a few seconds because three samples are taken per destination.

3. 3

   For the DNS test, type a domain name and press the button to get its A records and TTLs.

Frequently asked questions

Is this the same as the ping command?

No. A browser cannot send ICMP packets, so what is timed here is a full HTTP request, including DNS, the TLS handshake and the server’s reply. That is why the number is higher than a raw ping; it is meant for comparing destinations and spotting a slow path, not as an absolute figure.

What is a WebRTC leak and why does it matter?

With a VPN on, website traffic goes through the tunnel, but WebRTC can advertise your real network address in ICE candidates in order to set up direct calls, and those candidates reach the site on the other side. If a public address appears here that matches your real IP, the VPN is not covering everything. One technical caveat: the comparison uses the public IP shown at the top of the page, so on an IPv6 connection with WebRTC announcing an IPv4 address no leak warning is raised, read the rows themselves as well. Current browsers often obfuscate those addresses with mDNS, in which case nothing is listed.

Why do some rows show a dash or a cross?

Because the data comes from outside services and one of them may be filtered, slow or temporarily down on your network. Each row is independent, the other sections keep working, and reloading the page tries again.