Lessons › Servers & virtualisation
What happens when you open a website
▶ Start the interactive lesson
A user types intranet.burrow.local and presses Enter. In under a second, half a dozen protocols take turns. When it fails, the error tells you exactly which turn broke, if you know the order.
Key points
- 1. DNS: the PC asks its DNS server (UDP 53) for the name's A record (IPv4) or AAAA (IPv6). No answer or NXDOMAIN, and nothing else happens.
- 2. TCP: the browser opens a connection to that IP on port 80 (HTTP) or 443 (HTTPS) through the gateway, routers and firewalls.
- 3. TLS (HTTPS only): the server proves its identity with a certificate and both sides agree encryption keys. Name mismatches or expired certificates give browser warnings.
- 4. HTTP: the browser sends a request (GET /) and gets a status code: 200 OK, 301/302 redirect, 401/403 not allowed, 404 not found, 500 server error, 502/503 a proxy or backend is down.
- Read the failure: "can't resolve" = DNS. "Refused" = web service down. "Timed out" = path or firewall. Certificate warning = TLS. 4xx/5xx = the web app itself.
The full lesson has more: animations, a hands-on exercise, 3 quiz questions and spaced review cards. Open it free →