LOCAL TELEMETRY CONSOLE

IP // CLIENT PRIVACY INSPECTOR

Know what your browser reveals. Everything is processed locally; only public IP lookups leave this page.

IDLE

Runs all diagnostics locally. Public IP lookups use third-party APIs.

PUBLIC IPidle

LOCATIONidle

ISP / ORGidle

PRIVACY POSTUREidle

LIVE DIAGNOSTIC LOG

Awaiting scan...

01 // PUBLIC NETWORK IDENTITY

Resolved via third-party APIs with automatic fallback.

PUBLIC NETWORK IDENTITY

Awaiting lookup...

02 // CLIENT FINGERPRINT SURFACE

Collected locally from your browser.

CLIENT FINGERPRINT SURFACE

Awaiting collection...

03 // GPU / WEBGL

Read via WEBGL_debug_renderer_info when available.

GPU / WEBGL

Awaiting detection...

04 // WEBRTC LEAK TEST

Detects whether local IPs leak via WebRTC candidates. Modern browsers may hide them.

WEBRTC LEAK TEST

Awaiting test...

05 // CONNECTION DIAGNOSTICS

Latency measured against the same origin.

CONNECTION DIAGNOSTICS

Awaiting test...

06 // BROWSER CAPABILITIES

What the browser can and cannot expose about the connection.

BROWSER CAPABILITIES

Awaiting check...

07 // TRACE ROUTE SIMULATION

A visual simulation for demonstration. It makes no network requests and is not a real traceroute.

TRACE ROUTE SIMULATION

SIMULATION - NOT A REAL TRACEROUTE

REPORT & PRIVACY

How this works

Every diagnostic runs in your browser. No diagnostic data is stored or sent to any backend. The only network requests are the public IP lookup (to the third-party API shown in the report) and a same-origin latency check. Browsers cannot expose response headers, the TLS cipher, or the negotiated HTTP version to page JavaScript, so those fields report as unavailable rather than guessed.

Copies a structured text report of the current scan.