01 / Names
DNS is a starting point
A browser first needs an address for a name. A slow or stale answer can look like a broken website, even when the server is healthy.
Practical network notes
Short explanations of the everyday systems behind a reliable connection: names, routes, latency and secure transport.
01 / Names
A browser first needs an address for a name. A slow or stale answer can look like a broken website, even when the server is healthy.
02 / Routes
A service can work from one network and fail from another. Compare paths from several providers before blaming an application.
03 / Transport
A successful TCP handshake is only the beginning. Certificate validation, request delivery and response timing matter too.