See what your connection quietly reveals
Every website receives technical signals the moment you load a page. Not your identity — but enough to build a “profile” of your setup over time. This page helps you understand what’s visible and what’s worth tightening.
- Exposure happens BEFORE you log in or share anything — just by loading a page.
- Single signals aren’t “identity”, but combined they create traceability across visits.
- Consistency is the issue: the more stable your signals, the easier you are to recognize over time.
- Goal:CONTROL.First understand visibility. Then reduce what you don’t need to expose.
Three layers of exposure
Click filters to focus. Each layer removes a common “recognition” advantage attackers and trackers love.
Your IP is the “return address” of your connection. It can hint at region, ISP, and wider network patterns. Not your name — but it can still shape risk scoring and recognition.
- Approx region + suspicious timezone mismatch signals
- ISP / ASN patterns and network stability across sessions
- Reputation risk from shared ranges (abuse history on the same network)
Browsers expose tiny details to make sites work — but some also help fingerprint your setup. Even without cookies, a browser can look “unique” based on capabilities and settings.
- WebRTC + permission-based leaks that reveal more than intended
- Fingerprintable settings (rendering, fonts, extensions, preferences)
- Storage tracking beyond basic cookies (local storage, cache behavior)
DNS translates website names to IPs. It’s invisible to most people, but misconfigurations can create “leak” patterns — especially when using VPNs or split tunneling.
- Resolver visibility (who answers your DNS requests)
- Leak patterns from misconfigured VPN / split tunnels
- Consistency across networks (home / mobile / VPN) and what changes
First, take a snapshot of what’s visible today. Then decide what’s worth improving and what’s just normal background noise.
