Senior Backend Engineer / Stage 1 · Foundations
Follow a browser request through DNS, TCP and TLS
"Already know" meets prerequisites. "Not relevant" removes the topic from your total but leaves what builds on it waiting.
Self-check
- You open https://shop.example/orders in a fresh browser. Draw DNS lookup, TCP connection, TLS authentication and the HTTP exchange. Mark where a wrong certificate stops the request.
- Evidence to include: Label the client, resolver and server, and distinguish name resolution from certificate validation.
Try it without the material first, then compare. Save your answer in your notes below. Report a problem with this self-check
Learning activities
9 activities- Not done1 min
- Not done7 min
- Not done3 min
- Not done5 min
- Not done3 min
- Not done5 min
- Not doneHow the web works (opens another site)
A short walk from typing an address to a rendered page, with DNS, packets and HTTP named in order.
9 min - Not doneHow DNS Works (opens another site)
A comic in six episodes that follows one lookup through the root, TLD and authoritative servers.
20 min - Not doneTransport Layer Security (TLS) (opens another site)
Covers the handshake and server authentication, which is where the certificate boundary sits.
5 min