WebRTC and Public IP Privacy Test tool
Privacy result
Connection summary
WebRTC candidates
0 candidates| Address | Type | Protocol | Classification |
|---|---|---|---|
| No test has been run. | |||
View raw report
{}
What this privacy test checks
The test compares the public IP observed by OceanofTools with addresses exposed while the browser creates WebRTC ICE candidates. Modern browsers often replace local addresses with random .local mDNS names, which is a privacy improvement.
- A matching server-reflexive address is usually expected.
- A different public host address may reveal a second interface or route outside a VPN.
- Carrier-grade NAT, IPv4/IPv6 dual stack and corporate networks can legitimately expose more than one public address.
This page cannot identify the DNS resolver used by your operating system. Any tool claiming resolver names without operating a dedicated DNS test domain may be presenting guessed or unrelated data.
Frequently Asked Questions
Does this test identify my DNS server?
No. It honestly tests public-IP and WebRTC exposure. Identifying DNS resolvers requires a dedicated authoritative DNS testing service.
Does a different WebRTC address always mean a leak?
No. VPN routing, IPv4 and IPv6, carrier networks, relays and multiple interfaces can create different public candidates. Treat it as a signal to review.
Why do I see an address ending in .local?
Modern browsers use mDNS hostnames to hide private local IP addresses from websites.