RiggedTLS Inspector

A closer look at
your browser.

Real TLS evidence. Reported browser claims.
A clear view of what doesn’t add up.

Runs only when you ask. No sign-in.
Ready for inspectionNo report yet

Evidence before assumptions.

Start an inspection to capture your TLS handshake and check your browser’s reported identity.

Four core groups · Extended identity checks

Checks read browser identity, Client Hints, a separate worker context, automation flags, languages, timezone, cookies, and graphics. Browser claims are returned to you, not stored. Normal request logs are retained. Understand the limits

Inspection evidence

Measured facts and reported claims, kept separate

Your evidence will appear here.

The report includes TLS fingerprints, browser comparisons, and the reasons behind every score.

A score you can inspect.

Points reflect observable signals, not the likelihood of malicious activity. The score is withheld until all four evidence groups are available.

Identity is always unverified. A zero only means no implemented rule matched. Customization, privacy tools, and legitimate automation can affect these checks. Sophisticated modifications may go undetected.

Browser reports WebDriver+45
User-Agent names automation+25
HTTP and JavaScript identities disagree+20
Browser language claims disagree+10
Client Hint and worker rule weights
header engine mismatch+30
header version mismatch+20
header platform mismatch+15
js hint engine mismatch+30
js hint version mismatch+20
hint platform mismatch+20
hint mobile mismatch+15
worker ua mismatch+30
worker platform mismatch+15
navigator override+15

Additive heuristic · Capped at 100 · Related clues may overlap · Missing data adds no points