Browser & Identity Consistency Checker
Audit your browser fingerprint integrity. Probe for WebRTC public IP leaks, verify User-Agent Client Hints, and detect profile spoofing anomalies in real time without uploading data to any server.
Audits WebRTC IP leaks, timezone integrity, user-agent client hints, and anti-spoofing heuristics
Reserved banner container configured with strict Core Web Vitals CLS = 0 layout preservation.
How Anti-Fingerprint Tools & Proxies Get Flagged
Privacy extensions, web scrapers, and anti-detect browsers attempt to alter browser headers to simulate clean identities. However, modern fingerprinting engines cross-reference lower-level JavaScript APIs against HTTP headers. The reference matrix below outlines the most common giveaways that expose spoofed browser sessions:
| Spoofed Attribute | Common Flaw / Giveaway | Detection Method | Risk Severity |
|---|---|---|---|
| Operating System | UA header claims Windows 10, but navigator.platform reports MacIntel | JS API Cross-Check | Critical |
| Timezone Integrity | IP geolocation points to Frankfurt (UTC+1), but browser clock reports UTC-5 | GeoIP vs getTimezoneOffset() | High |
| Mobile Emulation | UA claims iPhone 15, but WebGL debug vendor outputs NVIDIA GeForce RTX | WebGL Debug Renderer Query | Critical |
| WebRTC Leak | Browser proxy or extension VPN is active, but STUN server returns host ISP address | ICE Candidate Harvesting | Critical |
| Touch Digitizer | Desktop Windows/macOS profile reporting ontouchstart with >10 touch points | navigator.maxTouchPoints | Medium |
What is a WebRTC Leak and How Does It Work?
Web Real-Time Communication (WebRTC) allows web browsers to exchange real-time voice, video, and data directly with peer devices without requiring an intermediary media server. To establish peer-to-peer connections between two computers located behind residential NAT firewalls or corporate routers, the browser uses the Interactive Connectivity Establishment (ICE) framework.
During ICE negotiation, the browser contacts a STUN (Session Traversal Utilities for NAT) server (such as Google's public STUN endpoint at stun.l.google.com:19302). The STUN server inspects the incoming UDP packet and responds with the sender's public socket endpoint—known as a Server Reflexive (srflx) candidate.
ICE Candidate String Decomposition (RFC 5245)
candidate:842163049 1 udp 1686052607 198.51.100.24 54822 typ srflx raddr 10.0.0.12 rport 54822
• Field 4 (198.51.100.24): The true public WAN IP address discovered by the STUN server.
• Field 7 (typ srflx): Indicates a server reflexive candidate discovered via NAT traversal.
Because browser proxy extensions (and some VPN plugins) only intercept standard TCP HTTP/HTTPS traffic, WebRTC UDP packets bypass the encrypted tunnel entirely, leaking the user's physical ISP IP address to any website requesting a basic peer connection.
Understanding Client Hints vs. Legacy User-Agent Reduction
For decades, web browsers broadcasted an exhaustive, unprompted identity string in every HTTP request header via User-Agent. A typical string revealed the browser rendering engine, major and minor build revisions, exact operating system patch level, and CPU architecture.
To mitigate cross-site tracking and reduce passive surface area, the W3C and Chromium introduced User-Agent Client Hints (UA-CH). Under this architecture:
- Low-Entropy Hints (Sent by Default): Modern browsers broadcast only high-level information by default: the brand (e.g.,
"Chromium";v="120"), whether the device is mobile (?0or?1), and the general platform ("macOS"or"Windows"). - High-Entropy Hints (Opt-In Only): Detailed parameters—such as exact platform versions (e.g.,
15.0.0), CPU bitness ("64"), architecture ("arm"or"x86"), and full version lists—are only exposed when servers explicitly request theAccept-CHHTTP header or through JavaScript vianavigator.userAgentData.getHighEntropyValues().
Explore Complementary Diagnostic & Network Tools
Pair your identity consistency audit with our deep network and system inspection utilities:
My IP & Geolocation Map
Public WAN IP, WebRTC LAN probe, and OpenStreetMap ISP PoP map.
Visual Route Tracer & Map
Map intermediate router hops and visualize packet journeys across the globe.
Fingerprint Hash Generator
Generate Canvas 2D and Web Audio SHA-256 hashes & test noise injection.
My System Specs
Inspect unmasked GPU model, CPU threads, display Hz, and RAM tier.
Subnet & CIDR Planner
Calculate RFC 1918 host scopes and prevent VPN address collisions.
Network Jitter Test
Real-time edge ping jitter graph and bufferbloat quality grading.
PCAP Dump Viewer
Drop packet capture files to view protocol breakdown and plaintext leaks.
Frequently Asked Questions (FAQ)
WebRTC (Web Real-Time Communication) is an HTML5 standard that allows browsers to establish direct, low-latency peer-to-peer audio and video connections. To connect directly with peers across Network Address Translation (NAT) firewalls, WebRTC uses the STUN protocol (Session Traversal Utilities for NAT). When a browser initiates a STUN request, it creates a raw UDP socket that frequently bypasses standard HTTP/SOCKS5 browser proxy extensions, allowing remote websites to learn your true ISP public IP address.
Reserved banner container configured with strict Core Web Vitals CLS = 0 layout preservation.