IP checker
Your public IP address
- Location
- -
- ISP / ASN
- -
- Timezone
- -
- Connection type
- -
- Last checked
- Never
Network privacy diagnostics
Run quick tests before using a VPN, proxy, travel network, or privacy-focused browser. Results stay in your browser except for the public lookup APIs needed to perform each test.
IP checker
DNS leak test
Browsers cannot directly read your operating system DNS servers. This test compares public resolver responses and checks whether DNS-over-HTTPS endpoints reveal resolver metadata. A full commercial DNS leak test needs a backend with authoritative DNS logging.
VPN protection
The score combines public IP identity, DNS resolver signals, WebRTC exposure, and browser locale consistency. A full VPN audit still needs backend DNS logging.
Browser fingerprint
How it works
The site requests public lookup services to show the IP address, network, approximate city, country, ASN, and timezone visible to websites you visit.
Frontend-only DNS tests are limited by browser security. For the strongest leak detection, deploy a server endpoint that creates a unique hostname and records which resolver queries it.
The score checks whether public IP, DNS resolver, WebRTC, timezone, and language signals look consistent or expose information that a VPN user may want to review.
Browser, display, language, timezone, hardware, canvas, and WebGL signals are combined into a local hash so visitors can see how distinctive their browser appears.
FAQ
The score estimates visible browser-side VPN protection by checking public IP identity, DNS resolver signals, WebRTC exposure, timezone consistency, and browser language region.
No. Browser-only DNS checks can compare public resolver signals, but a complete DNS leak test needs a backend with authoritative DNS logging for unique test hostnames.
The browser fingerprint hash is calculated locally in the visitor's browser. Public lookup APIs are only used for the network tests needed to show IP and DNS-related signals.
Privacy guide
Reconnect your VPN, choose a closer server, clear browser proxy settings, and rerun the IP check.
Enable the VPN provider's private DNS option, disable split tunneling for the browser, and retest.
Reduce extensions, use a mainstream browser profile, avoid uncommon fonts, and keep privacy settings consistent.