Submit
Packet trace comparison

HTTP vs HTTPS: Compare Two Packet Traces

Both traces fetch a page. Follow the two flows side by side and see which layers change when the request uses HTTPS over TCP.

Explore Protocol Explorer & its website →
Protocol Explorer HTTP lesson showing the network diagram and packet flowProtocol Explorer HTTPS lesson with its TCP and TLS stages
What we checked

This exercise compares the HTTP and HTTPS scenarios bundled with Protocol Explorer. The workbench generates sample bytes and timing locally. The traces represent fresh connections over TCP.

Read an HTTP request and reply

  1. Open the HTTP lesson and advance through the steps until Packet flow shows GET / HTTP/1.1. Select the row to inspect the request.
  2. Look for the Host header and the request target /. Together they identify the page being requested in this example.
  3. Inspect the 200 OK response in the same step. Locate Content-Type and Content-Length, then check what begins after the blank line. The example body is <h1>Hello</h1>.

Find what TLS changes

  1. Open the HTTPS lesson and follow the packets through the DNS and TCP stages. Check the transport destination in the TCP handshake.
  2. Advance to Negotiate TLS. Identify the ClientHello and ServerHello rows, then find the encrypted handshake record.
  3. Advance to Send encrypted HTTP and inspect the application records. The packet inspector exposes illustrative TLS bytes. The request line and headers are available to the endpoints after decryption.

Record three differences

Now predict what a repeat page load might omit. A DNS cache can supply the address locally, and an existing connection can carry another request. The sequence in the lab models a fresh visit.

StageHTTP traceHTTPS trace
Name lookupDNS appears before the connectionDNS appears before the connection
TransportTCP to port 80TCP to port 443, followed by TLS
Page exchangeRequest and reply headers are visible in HTTP rowsHTTP travels inside encrypted TLS records
A LITTLE MORE CONTEXT

Common questions

Does HTTPS hide the destination?

The destination IP is still needed for routing. DNS visibility depends on the resolver and whether DNS traffic is encrypted.

Would the same sequence appear for HTTP/3?

HTTP/3 uses QUIC over UDP. Use these two traces to compare HTTP and HTTPS over TCP.

Sources & editorial method

Written by NavSprout Editorial. Published and checked .

Report a correction →
MAKE A THOUGHTFUL CHOICE

Your shortlist, side by side.

Pricing models are indicative. Check each official website for current plans and limits.