Case AE85D6 · Network · L1 Foundations
Typing a URL, Securely
Interview questionWalk me through what happens when you type a URL into a browser and press Enter, and point out the security controls along the way.
- 01 Answer
- 02 Example
- 03 Trade-offs
What a strong answer covers
Try it out loud first. Then check yourself:
- DNS: cache, then resolver lookup; risks are spoofing and hijack, mitigated by DNSSEC, DoH/DoT and trusted resolvers
- TCP handshake then TLS: SNI, certificate chain and hostname validation, key exchange giving forward secrecy
- HSTS (and preload) forces HTTPS before any request, stopping SSL stripping on the first plaintext hop
- HTTP request carries cookies scoped by Secure, HttpOnly and SameSite; response headers like CSP set browser policy
- Rendering runs under the same-origin policy; a strong answer names where a proxy, WAF or CDN sits and what it sees
If the interviewer pushes back
- At which step could a corporate TLS inspection proxy see the traffic, and how does the browser trust it?