Port 80/tcp: HTTP (Hypertext Transfer Protocol)
Category: Web & Application. Range: well-known. Status: iana registered.
What runs here
HTTP is the application-layer protocol underlying the World Wide Web: a stateless request/response protocol where a client requests a resource by method, path, and headers, and a server returns a status code, headers, and a body. Port 80/tcp is its IANA-registered default, governed by RFC 9110 (HTTP Semantics). Traffic on 80 is plaintext by default, with no confidentiality or integrity protection unless something above the transport adds it.
Why it matters
Because it is plaintext, HTTP on port 80 is directly readable in a packet capture or proxy log: full URLs, headers, cookies, and any unencrypted credentials or tokens transiting the wire, making it forensically valuable whenever it turns up in traffic that should otherwise be encrypted. It is also the near-universal fallback: most modern sites use 80 only to redirect to 443, so persistent plaintext traffic on 80 rather than a single redirect can indicate a legacy or misconfigured service, an internal tool, or malware avoiding the overhead of TLS.
Where you see it
Legitimately: web browsing prior to an HTTPS redirect, internal/legacy web applications, load balancer and health-check probes, package/update mirrors. Anomalously/maliciously: plaintext C2 or exfiltration channels using HTTP to blend with common traffic, webshell interaction over unencrypted HTTP, credential harvesting via a spoofed plaintext login form, or a host serving HTTP where only HTTPS is expected.
What to look for
| Signal | What it means |
|---|---|
| Full request line in the clear | The Host header, URI path, and query string are visible as-is, making them the fastest way to spot beaconing patterns, webshell endpoints, or known-malicious User-Agent strings. |
| Redirect behavior | Whether the server issues a 301/308 to HTTPS at all; a live plaintext response instead of a redirect is unusual for a modern public-facing site. |
In practice
A compromised web server accepting POST requests to a webshell over plain port 80 rather than 443 avoids the overhead of a TLS setup, and the commands and output are then fully visible in a packet capture.
Related ports
- 443/tcp: HTTPS (HTTP over TLS/SSL)
- 8080/tcp: HTTP Alternate (http-alt)
- 3128/tcp: Squid HTTP Proxy (de facto; registered as ndl-aas)
ATT&CK techniques
- T1071.001: T1071.001