Port 8080/tcp: HTTP Alternate (http-alt)
Category: Web & Application. Range: registered. Status: iana registered.
What runs here
Port 8080/tcp carries no protocol of its own: it is registered with IANA simply as http-alt, a designated alternate for port 80, and in practice is used by a wide range of unrelated services: web application servers running without root privileges (which cannot bind to the privileged port 80), reverse proxies, development servers, and device/appliance admin UIs. What is actually spoken on 8080 is ordinary HTTP (or occasionally HTTPS); there is no way to know which without inspecting the traffic.
Why it matters
8080 is a catch-all convention. The port number alone tells an analyst nothing about what is listening there, so it has to be fingerprinted. It is also a very common default for admin and management interfaces of self-hosted tools and appliances, so unexpected exposure or traffic on 8080 is worth identifying the actual application behind before treating it as routine.
Where you see it
Legitimately: non-privileged web/app servers (Node.js, Tomcat, Jenkins, etc.), forward/reverse proxy listeners, local development servers. Anomalously/maliciously: an attacker-planted proxy or C2 listener chosen because 8080 is rarely filtered outbound and is easy to overlook among legitimate proxy traffic, or exposed admin panels scanned and exploited for initial access.
What to look for
| Signal | What it means |
|---|---|
| Actual application banner/response | 8080 must be fingerprinted rather than assumed; the Server header, TLS presence or absence, and response content identify what is really listening. |
Related ports
- 80/tcp: HTTP (Hypertext Transfer Protocol)
- 8443/tcp: HTTPS Alternate (registered as PCsync HTTPS)
- 3128/tcp: Squid HTTP Proxy (de facto; registered as ndl-aas)
ATT&CK techniques
- T1071.001: T1071.001