Application Protocols: HTTP, DNS, Email and Proxies
Application protocols define the messages and operations used by software. Their semantics remain distinct from the transport that carries them.
Curated learning paths from Protocol Explorer · Editorial approach and simulation limits
The pages below focus on what an application asks for, what a response means and which parts of an exchange are visible in a capture. Several protocols can use the same transport while behaving very differently.
Start with the operation the application is asking for
Application protocols define request meaning, response meaning and the state that an application maintains. A port can suggest what to inspect, but it does not prove which protocol is present: services can move ports, use encryption, or share a transport. Read the message syntax and sequence. An HTTP status code answers a different question from a successful TCP acknowledgment; an SMTP reply describes one mail-transfer step, not final inbox delivery.
Choose a starting protocol by the task: HTTP for web requests and responses, DNS for name lookup, SMTP for message submission or transfer, IMAP and POP3 for mailbox access, and SMB or FTP for file operations. Then trace the first application message, its identifiers or tags, and the response that matches it. For encrypted sessions, a network capture may reveal endpoints, timing and record sizes without exposing the application payload.
When moving across this collection, compare protocols that share a purpose but differ in state and trust. DNS over HTTPS carries DNS messages through HTTP; a proxy forwards or tunnels another client’s traffic; WebSocket changes an HTTP opening exchange into bidirectional framing. These relationships help explain a trace without confusing the application contract with the TCP, UDP or QUIC transport beneath it.
Explore protocols in this topic
- DNS over HTTPS
DNS query and response messages mapped into an HTTP exchange.
- FTP
File commands over a control connection and transfers over a separate data path.
- HTTP
Requests, responses, status codes and resource semantics.
- HTTP Proxy
Forwarded HTTP requests and CONNECT tunnels for HTTPS.
- IMAP
Mailbox selection, message fetches, flags and synchronization.
- Modbus
Industrial request and response messages identified by function codes.
- POP3
Mailbox retrieval commands and session update behavior.
- Reverse Proxy
Inbound request routing from a public service to upstream servers.
- SMB
Negotiated sessions, share connections and network file operations.
- SMTP
Mail transfer commands, replies and hop-by-hop acceptance.
- SOCKS5
Proxy method negotiation and TCP or UDP relaying.
- WebRTC
Signaling, ICE path checks and secure real-time media transport.
- WebSocket
An HTTP opening handshake followed by bidirectional frames.
Read the application contract, not just the port
A familiar port number can suggest a protocol, but the actual message format and negotiated behavior provide stronger evidence. The same TCP connection can carry HTTP, SSH or mail, while DNS over HTTPS uses an HTTP exchange to carry DNS messages.
Keep framing and delivery separate
TCP supplies a byte stream, so an application needs its own message framing. UDP preserves datagrams, while QUIC supplies independent ordered streams. A transport acknowledgment or successful proxy connection is not the same as an application-level success response.
Continue from one message family to another
Follow the DNS privacy and DNSSEC comparison, or start with the packet-reading guide to trace one exchange from the user action downward.