PUBLIC IP ADDRESSIPv4 / IPv6
—.—.—.—
Ready to explore your connection
A CLEARER VIEW OF YOUR NETWORK
WebRTC leak test
Inspect connection candidates exposed by this browser. The test uses Google STUN after you press Run; it does not request your camera or microphone.
IPv4, IPv6 & domains supported No sign-up required
WebRTC exposure
Your next insight starts with a single lookup.REPUTATION & RISKⓘ
—/ 100
Not assessed
Verified risk data required.
No guessed scores.
APPROXIMATE IP LOCATION⌖
Location awaiting lookup— ° N — ° E
View approximate location ↗IP databases estimate a network exit, not your device location.
Optional: requires browser location permission. Device coordinates are excluded from reports.
Open device location map ↗AUTONOMOUS SYSTEM—
ORGANIZATION—
TIME ZONE—
DATA SOURCE—
Enable JavaScript to run this tool on demand.
Related network tools
Go deeper. Everything you need to understand your connection.IP intelligence
Geolocation, ASN and network ownership.
DNS lookup
Inspect A, AAAA, MX, TXT and DNSSEC.
WebRTC exposure
See which addresses your browser exposes.
Network exit
Compare IPv4 and IPv6 network exits.
Compare candidates with the expected exit
- Record the public exit you expect, using your network configuration and the IP lookup.
- Run the WebRTC check. Gathering can take several seconds.
- Compare candidate addresses and types with the expected exit. If needed, repeat after one deliberate connection change.
The check gathers candidates from a local peer connection. It does not make an audio/video call or connect two remote users.
Read host, srflx and relay candidates
A host candidate describes a local interface; browser privacy controls may substitute an mDNS hostname. A server-reflexive (srflx) candidate describes an address observed via STUN. A relay candidate describes a TURN relay.
This implementation configures Google STUN and no TURN service, so a missing relay candidate is expected and is not a failure. A private address alone is not evidence that your public IP has escaped a VPN.
An empty result is not a safety certificate
No candidates can reflect browser restrictions, blocked STUN traffic or unavailable networking features. It does not prove the absence of leaks. Conversely, an exposed public candidate needs comparison with your expected route before it can be described as an unexpected exit.
This test does not inspect your system DNS resolver, VPN configuration or every browser application.
Use a reproducible comparison
Read what empty WebRTC results mean, the VPN exit comparison checklist, and the browser privacy guide. The IPv6 test can reveal a separate address-family path.