What happens when you type a URL and hit Enter?
The choreography of systems that runs in under a second: from name to IP, the connection, the request and the render.
Learning path
How a secure web request works
Follow the complete journey from entering a URL to receiving a secure application response.
By the end you'll understand
how a web request travels end to end —from name to encrypted response— and why each layer matters for security and performance.
DNS: the address book of the internet (and when it lies)
How a name becomes an IP, why a change "takes time to propagate", and what you see —and don't— when DNS fails.
TCP vs UDP: delivery control versus lower latency
TCP prioritizes ordering, verification and retransmission. UDP cuts coordination when losing or reordering some data beats waiting.
HTTP and HTTPS: what travels in the clear and what the padlock protects
What an HTTP request really is, what TLS adds, and what the browser padlock does —and does not— tell you.
Symmetric and asymmetric encryption: why they're used together
Two families of keys with opposite strengths. Why TLS doesn't pick one, but combines both.
Digital certificates: why your browser trusts a site
What a certificate is, who signs it, and how the chain of trust that holds up the web is built.