WebRTC leak test
Checks whether WebRTC exposes an additional network address beyond your visible public IP.
See the public IP address your connection shares with websites, then run quick privacy and connection checks from your browser.
Network owner and approximate location for the public IP address you entered.
IP-based locations are approximate. They do not identify a person or reveal an exact home address.
No account or software installation required.
Checks whether WebRTC exposes an additional network address beyond your visible public IP.
Verifies that your browser can reach an encrypted DNS resolver and receive a valid response.
Estimates current download throughput using a small test file. Results may vary.
A summary of common details your browser provides automatically.
Your public IP can identify your internet provider and approximate area, but it does not normally reveal your exact street address. A VPN or proxy may replace the address websites see.
WebRTC enables real-time browser communication. In some configurations it may expose another network address, even while a VPN is active.
A DNS leak occurs when domain lookups bypass the DNS service you expected to use. A complete resolver identity test requires dedicated server-side test domains; this page checks encrypted DNS connectivity.
This lightweight test is a fast estimate. Wi-Fi quality, server distance, VPN use, browser activity, and network congestion can change the result.
Results are informational and may be affected by VPNs, proxies, privacy settings, browser restrictions, and mobile carrier routing.
Your public IP address helps websites and online services return information to your internet connection. It can reveal useful network details, but it should not be confused with a precise physical location or a complete picture of your identity.
A public IP address is the internet-facing address visible to websites and services you contact. It is normally assigned by your internet service provider, business network, mobile carrier, or VPN provider. Multiple devices in one home can appear online through the same public address because the router shares the connection.
Private IP addresses are used inside local networks. Common examples begin with 192.168, 10, or certain 172 ranges. They help your router identify phones, computers, televisions, and other devices at home, but those private addresses are not normally reachable directly from the public internet.
IPv4 is the familiar shorter format made from four groups of numbers. Its limited address supply led internet providers to rely heavily on address sharing technologies such as Network Address Translation. IPv4 remains common and is still supported across most websites and networks.
IPv6 uses a much longer hexadecimal format and provides an extremely large address space. A connection may support IPv4, IPv6, or both at the same time. The version shown by this page is based on the address used to reach the lookup service, so another service may use a different version when both are available.
An IP lookup can often identify the internet provider or organization responsible for an address range. It may also estimate a country, region, city, time zone, or broad network area. These details come from registration records, routing information, and commercial geolocation databases.
An IP address does not normally reveal a visitor's name, exact home address, apartment, or live GPS position. Location accuracy varies by provider and network. The city displayed may be the location of an ISP gateway or registration office rather than the place where the device is physically being used.
Many residential and mobile connections use dynamic addresses that can change after reconnecting, restarting network equipment, or moving between cellular towers. Mobile carriers may route traffic through regional gateways located far from the user.
A VPN or proxy can replace the address websites see with the public address of an intermediary server. Business networks, satellite connections, public Wi-Fi, privacy relays, and recently reassigned address ranges can also produce a city or provider result that looks unfamiliar.
A VPN usually hides the public address assigned directly by your internet provider from the websites you visit. Those websites see the VPN server address instead. This can reduce direct IP-based location exposure and protect traffic on an untrusted local network when the VPN is configured correctly.
A changed IP address does not make a person completely anonymous. Cookies, account logins, browser fingerprinting, analytics identifiers, and information voluntarily submitted to a website can still connect activity across sessions. A VPN provider may also receive connection information, so its security practices and privacy policy matter.
WebRTC supports real-time audio, video, and data communication in modern browsers. The WebRTC test looks for additional network addresses made available to the page. Modern privacy protections may hide or replace local addresses, so a limited result does not necessarily mean the browser is malfunctioning.
The DNS check on this page verifies connectivity to an encrypted DNS endpoint. It is not a complete resolver identity test. A full DNS leak test needs dedicated domains and server-side observation. Browser and device information is collected locally from standard properties that websites can request automatically.
The download test transfers a small test file and calculates an approximate rate from the amount of data received and the elapsed time. It is designed for a quick browser check, not as a replacement for a controlled broadband benchmark. Wi-Fi signal quality, other devices using the connection, browser extensions, VPN overhead, server distance, temporary congestion, and cached data can all influence the result. For a clearer picture, repeat the test at different times and compare it with a wired connection or a test provided by your internet service provider.
Quick answers to common questions about public IP addresses, location estimates, privacy checks, and connection testing.