What a TLS hello tells you before any decryption

You don't always need decrypted application traffic to find something interesting.

In our small TLS capture, a client contacts port 443. The useful clues are in the ClientHello: SNI names updates.packetlab.test, and ALPNs contains http/1.1.

That's enough to see the hostname the client supplied and the application protocol it offered. The ServerHello selects a TLS 1.2 cipher, 0xc02f.

An offer isn't a request

There is no HTTP request in this capture. The example stops after the two hellos, before a certificate, a completed handshake, or application data. An offered http/1.1 value doesn't give us a URL or prove that an HTTP exchange happened.

That's a useful distinction when exploring your own network: record what a handshake actually reveals, then look for the next piece of evidence.

Try the capture in Netcap's TLSClientHello records, or open it in Wireshark with the display filter tls.handshake. These are generated packets with a fictional hostname, so there's no real server to contact.

Download the capture and inspect the fields. See which clues you can find before opening the walkthrough.