CHECK

One-Click Check

Starts with a full report on your exit IP (purity, ownership, risk, platform suitability), then runs six dimensions in one pass — exit network, leaks, regional consistency, browser identity, device fingerprint and platform reachability — and cross-checks IP and environment together into an exportable report.

Ready to run

The check runs in your browser and takes about 20 seconds. It only collects public network and browser characteristics — never accounts, passwords, cookies, form content or local files.

Identifying your exit IP and building the report

Exit network

Exit IP location and type, proxy / datacenter signals, exit consistency across endpoints, RPKI validation

Leaks

Whether WebRTC exposes your real public IP, encrypted DNS availability and DNSSEC

Regional consistency

Whether timezone, language, fonts and exit country agree

Browser identity

UA, client hints and HTTP headers consistency, automation traces, private mode

Device fingerprint

Platform vs GPU contradictions, Canvas / Audio fingerprint stability, TLS fingerprint

Platform reachability

Reachability of major platforms, AI services and streaming, exposed inbound ports

It merges the full exit-IP report with the exit-network, leak, timezone/language, browser-identity, device-fingerprint and reachability checks into a single run and lays the results side by side on one page. Each one can look fine on its own; it is the combination that gives you away — an IP in Germany paired with an Asia/Shanghai timezone, for instance.

What each of the six dimensions looks at

Network identity is layered, and a mismatch at any layer exposes you. This page runs the six common layers at once:

Exit network — the address you actually reach the internet from, its location and operator, whether it is classified as proxy or datacenter, and whether several endpoints see the same exit
Leaks — whether WebRTC bypasses the proxy and reveals your real public IP, and whether encrypted DNS works
Regional consistency — whether the system timezone, browser language, installed fonts and IP location contradict each other
Browser identity — whether the UA, client hints and HTTP headers agree, and whether there are traces of automation or private mode
Device fingerprint — whether platform and GPU contradict, whether Canvas and Audio fingerprints are stable, whether the TLS fingerprint is readable
Platform reachability — whether major platforms, AI services and streaming are accessible, and whether the exit has exposed inbound ports

Reading the score and the three states

Consistency starts at 100 and each issue deducts points by severity. It measures whether the findings agree with each other, not whether the IP itself is clean — so it is a different measure from the purity score on the home page. Each dimension ends in one of three states: pass, attention or anomaly.

When something is flagged red or amber, first ask whether you intended it. A US proxy paired with a Chinese interface and a Beijing timezone is an unambiguous signal to most platforms; IPv4 and IPv6 landing in different regions is common on dual-stack networks.

When to run it

After changing a proxy, VPN or anti-detect browser profile
Before running multiple accounts, to confirm the environments share nothing
After being blocked, to find which layer gave you away
Periodically during normal use — the quality of a proxy's exit addresses drifts over time

Common questions

Does the check store or expose my information?

Fingerprint and leak checks run locally in your browser; only the IP lookup and the optional AI analysis reach our servers. You can export the report yourself, and we do not tie it to any identity.

Why is this score different from the IP purity score on the home page?

The home page scores the IP's own history and reputation; this page scores whether browser, system and network agree with each other. A clean residential IP with a contradictory timezone can have high purity yet lose consistency points.

Why does the city shown differ from my proxy's node?

IP location comes from cross-checking several commercial databases, and the registered location of a datacenter IP often differs from where the hardware physically sits. A city off by one rarely matters; a wrong country does.

WebRTC showed my local network address — is that a problem?

A private address (192.168.x.x and similar) does not identify you. The real risk is WebRTC revealing your public IP, which means the proxy is not covering the browser's peer-to-peer connections.

Will two accounts with identical fingerprints definitely be linked?

Not necessarily, but it raises the odds considerably. Platforms usually weigh fingerprint, IP, behaviour and payment details together — fingerprint is one heavily-weighted input among several.