Common attacks and weaknesses
- Traffic can be read and modified on the path (credentials, session cookies, injected content).
- Serves as the entry point for SSL stripping when HTTPS is not enforced.
- Same application-level risks as HTTPS.
Unencrypted web traffic. Today it should only redirect visitors to HTTPS.
A browser sends an HTTP request to port 80 and the HTTP server sends the page back. It travels in clear text: anyone on the path can read it, passwords included.
| Service | Port | Transport | Description | Reference | Updated |
|---|---|---|---|---|---|
| http | 80 | TCP, UDP, SCTP | World Wide Web HTTP | RFC 9110 | 2021-10-01 |
| www | 80 | TCP, UDP | World Wide Web HTTP | RFC 9110 | 2021-10-01 |
| www-http | 80 | TCP, UDP | World Wide Web HTTP | - | - |
// source: IANA service name and port number registry
Linux
sudo ss -ltnup 'sport = :80' # process listening on 80
sudo lsof -nP -i :80macOS
sudo lsof -nP -i :80
Windows (PowerShell)
Get-NetTCPConnection -LocalPort 80 -State Listen | Select LocalAddress, OwningProcess Get-NetUDPEndpoint -LocalPort 80 netstat -ano | findstr :80
From another machine
nmap -p 80 -sV <host> sudo nmap -sU -p 80 <host> nc -zv <host> 80
Block it in the firewall
sudo ufw deny 80/tcp # Linux (ufw) New-NetFirewallRule -DisplayName "Block 80" -Direction Inbound -LocalPort 80 -Protocol TCP -Action Block # Windows
Unencrypted web traffic. Today it should only redirect visitors to HTTPS.
Port 80 is registered for TCP and UDP and SCTP. In practice the service mostly uses TCP.
It is rated 4/10 (moderate) when exposed to the Internet. Traffic can be read and modified on the path (credentials, session cookies, injected content). Redirect every request to HTTPS with a 301 and enable HSTS.
On Linux run "ss -ltnup 'sport = :80'", on macOS "lsof -nP -i :80", and on Windows "netstat -ano | findstr :80" to see the local process. From another machine, "nmap -p 80 <host>" shows whether it is reachable.