You type https://example.com/page into a browser and press Enter. Walk through what happens until the page appears.
Show the explanation
Model answer (in order).
- URL parsing and checking caches (browser, OS) for the page and for DNS.
- DNS resolution: the resolver finds the IP address (recursive lookup: root → .com → example.com name servers), results are cached with a TTL.
- TCP connection to port 443 (three-way handshake), then a TLS handshake: the server proves its identity with a certificate, and both sides agree keys for encryption.
- HTTP request (
GET /page, headers, cookies) over the encrypted connection; possibly HTTP/2 or HTTP/3. - The server (often behind a load balancer/CDN) processes it and returns a response: status code, headers, HTML.
- The browser parses HTML, builds the DOM, fetches CSS/JS/images (more requests), builds the CSSOM, runs JavaScript, then does layout and paint.
Good answers mention caching at each layer and that HTTPS protects content but the DNS lookup and server name can still be visible.
Original UniCircle question. Last reviewed 21 Oct 2026.
