Browser privacy check
Checks start automatically. Browser information is checked on your device; WebRTC and DNS tests also contact external services. Results are not sent to the application backend and do not change the IP risk score.
Browser checks and external requests
IP risk lookups are processed by our server. Some browser information is checked on your device; WebRTC and DNS tests also contact external services. We do not send WebRTC addresses, DNS resolver addresses or browser fingerprint results collected by these checks to Ping123's application backend or Google Analytics.
Understanding the results
Inspect signals exposed by the browser
This page checks signals related to WebRTC, DNS, time zone, language and browser fingerprinting. They help identify differences to review, do not contribute to the IP risk score and cannot establish complete anonymity.
Local evaluation can still require network requests
The diagnostic code does not upload raw WebRTC addresses, DNS resolver addresses or fingerprint components to the Ping123 diagnostic API. WebRTC and DNS checks still contact external services, which may see network information from those requests.
Frequently asked questions
Does a warning necessarily mean a privacy leak?
No. Differences in time zone, language or DNS organizations may have ordinary explanations. A warning asks you to review that evidence; a single difference does not establish a privacy leak.
Am I completely anonymous if no issue is found?
No. The result covers only checks supported by this browser and completed during this run, not every tracking method. Extensions, browser permissions and network settings may also affect detection.
How is unavailable different from no issue found?
Unavailable means there is insufficient test data, for example because the browser lacks support or an external probe failed. No issue found means completed checks did not trigger the current rules. These are different outcomes.