From URL to address
Typing a URL feels like one action, but it begins a chain of independent operations. The browser parses the scheme, hostname, port and path. Before it can contact the origin, it needs an address for the hostname. That usually comes from local DNS caches or a recursive resolver. A name can resolve to several IPv4 or IPv6 addresses, and the browser may try more than one.
For a conventional HTTPS connection over TCP, the client establishes a TCP connection, usually on port 443. HTTP/3 takes a different route: it runs over QUIC, which uses UDP and integrates TLS 1.3 into its handshake.
How TLS establishes trust
During the TLS handshake, the client and server agree on cryptographic parameters and derive traffic keys. The server normally sends a certificate chain. The browser checks that the certificate is valid for the requested name, is within its validity period, and chains to a trusted certification authority.
With TLS 1.3, ephemeral key exchange enables forward secrecy: stealing a server’s long-term signing key later does not, by itself, decrypt previously recorded sessions.
HTTPS means the connection is authenticated and encrypted. It does not mean the page content is accurate or that the operator is trustworthy.
Where HTTP begins
Only after the secure transport is ready does the browser exchange HTTP requests and responses, such as GET /, 200 OK, response headers and HTML. The page may then request CSS, JavaScript, fonts and images. HTTP/2 can multiplex requests on a single connection; HTTP/3 provides a similar capability using QUIC streams.
Ordinary network observers cannot read an HTTPS path, cookie or response body. They can usually still see source and destination IP addresses, traffic timing and volume. DNS and the requested hostname may reveal additional information depending on the client’s configuration, DNS transport and whether Encrypted Client Hello is in use.
Inspect a real connection
These commands are useful for an initial check. They do not replace certificate validation by a browser, but they help inspect the endpoint.
curl -I https://hideout64.org/
openssl s_client -connect hideout64.org:443 -servername hideout64.org
The first displays HTTP response headers. The second examines the TLS handshake and presented certificate chain. On Windows, curl.exe -I avoids a possible PowerShell alias for curl in older shells.