01 / THE CHALLENGE
Understanding the problem.
This project explores a browser extension for privacy checks focused on DNS and TLS verification. It builds on my interest in network behaviour, authentication and software resilience.
- 01DNS + TLS questions
- 02Verification architecture
- 03Implementation ahead
02 / MY INVESTIGATION
Following the evidence.
The architectural question is what a browser-based check can actually observe, and what that evidence would allow a user to conclude.
DNS and TLS verification are the current focus. The work remains at the architecture stage, so the portfolio does not present it as a deployed security product.
03 / CURRENT WORK
Developing the approach.
- 01
Developing the architecture for browser privacy checks around DNS and TLS.
- 02
Considering how verification results and their limits should be explained to a user.
- 03
Continuing the research alongside hands-on infrastructure and security learning in the lab.
04 / OUTCOME & EVIDENCE
What the work delivered.
Architecture in development. The project is an exploration of verification and evidence, with implementation and validation still ahead.
Current maturity
Architecture in development; no released extension or validated protection claims.
Research direction
DNS and TLS verification, with attention to what the available evidence can support.
Work in progress. This page describes a direction of investigation, not a released product or a guarantee of privacy.
05 / ENGINEERING PERSPECTIVE
What I take forward.
A useful verification tool needs to be clear about uncertainty. Explaining the limits of a check is part of the design, especially when someone may rely on its result.
Organisation names are generalised. These accounts describe my work without publishing client systems, internal logs or proprietary source code.