The engineering problem
VPN diagnostics must distinguish an observed address or route from a conclusion about where traffic traveled. Leakcheck records multiple signals and preserves inconclusive outcomes when those signals are insufficient.
Protocol-aware observations
DNS, local routing, IPv6, and STUN probes expose different aspects of connectivity. A manual disconnect workflow samples a transition window to help investigate traffic behavior when a tunnel drops.
Uncertainty as part of the interface
Pass, fail, error, and inconclusive results keep unavailable probes and weak evidence visible. Resolver-location heuristics cannot prove tunnel use, and direct STUN probes do not reproduce browser WebRTC policy.
Validation
The local mocked suite passed 24 tests. Live network behavior and VPN disconnect timing were not exercised in the portfolio audit; those require a controlled network and explicit observation of the target configuration.
Current scope
DNS resolver-location heuristics do not prove that traffic uses a tunnel. Direct STUN observations do not reproduce browser WebRTC policy. Results depend on the network and probe availability. The November 2026 mocked test run passed 24 tests; live VPN disconnect behavior was not tested.