L3·L4·TLS·QUIC·JS

Parity

session —

A coherence witness. Each layer is read at its own vantage point and asked the same question — which OS and device are you? The verdict below flags where the layers disagree, because disagreement, not any single value, is the detectable signal. Server-side rows arrive embedded; the browser layer is read on this page and posted back, after which the server returns its authoritative cross-layer verdict.

reading layers…

Server vantage

TCP / IPp0f

no p0f data

TLS ClientHelloJA3 / JA4 / h2

no TLS data

QUIC / HTTP3h3 endpoint

No QUIC layer yet. Stand terminates TLS over TCP (:443) via fingerproxy, which can't see UDP/QUIC. Needs a dedicated HTTP/3 terminator on :443/udp to capture QUIC Initial + transport params — roadmap item.

Browser vantage · this page

Navigatorthis page

Client Hints (UA-CH)this page

Display & Localethis page

WebGLthis page

Canvas / Audiothis page

WebRTCthis page

Each layer is read at a different vantage: p0f reads the TCP/IP stack off the wire, the TLS terminator emits JA3/JA4/HTTP2 as request headers, and this page reads the JS layer. A session id joins them; the server's CoherenceEngine compares OS and device across all layers — an L4=Linux / UA=macOS split lights the lamp.