Understanding results

A confirmed score measures published observations, with missing evidence kept visible.

Let your agent help troubleshoot

Read-only checks first. Review proposed changes before applying them.

Read with your agent · Markdown

Read the state before the score

Passed means the named observation met its rule during this test. Failed means a defined mismatch was observed. Check failed describes a collection error; unknown means the evidence was insufficient. Uncovered means no reliable implementation exists here.

A timeout, no WebRTC candidate or a familiar country is not proof of isolation. Missing evidence earns zero confirmed points; it is not proof of a defect.

Fixed weights and coverage

The denominator stays 100. We do not rescale covered items or estimate account risk. Location eligibility, browser metadata and official service health provide context without earning network points.

How the 100-point score works

Only verified evidence earns points. Missing, failed or uncovered evidence earns no confirmed points; covered weights are never expanded to manufacture a perfect score. A low score can reflect missing evidence, not a proven fault.

Evidence groupWeightWhat the points mean
Transport10Observable secure connection evidence.
Repeated HTTPS egress35Three same-family rounds with fixed reference and comparison targets. Repeated egress differences do not pass the fixed-exit rule.
Repeated WebRTC egress35Two STUN rounds compared with the same-family HTTPS baseline. Missing public candidates are not proof of safety.
Actual DNS path20Currently uncovered. These 20 points are not awarded.

Sources and scope