Port 80803 services

3 entries are registered on port 8080. It is a registered port (1024–49151) — IANA records an assignee, but nothing stops other software from listening here, which is why the number carries more than one entry.

entries
3

services registered on this number

transport
tcp · udp

2 transports in use

in transit
1/3

entries encrypted on the wire

worst risk
5/10

1 of 3 iana-registered

Services on this port

ranked by lookups
portservicerisk
:8080HTTP Alternatecaution
:8080Apache Tomcatcaution
:8080FilePhile Relaycaution

01HTTP Alternatetcp · iana-registered · risk 5/10

Port 8080 is a widely used alternative to the default HTTP port 80. It is often utilized for web proxies, caching servers, and development or administrative web interfaces running on non-root privileges. Its versatility makes it prevalent in web server management and testing environments, especially when the default port 80 is already occupied or restricted.

port 8080 as HTTP Alternate

02Apache Tomcattcp · unofficial · risk 4/10

Port 8080 is commonly used by Apache Tomcat, an open-source Java Servlet Container developed by the Apache Software Foundation. As an alternative HTTP port to the default port 80, it facilitates the development, deployment, and management of Java-based web applications. Due to widespread adoption, it's a key component for Java web application hosting and testing environments.

port 8080 as Apache Tomcat

03FilePhile Relayudp · unofficial · risk 4/10

FilePhile Master/Relay operates over UDP port 8080, facilitating peer-to-peer file transfers with a master/relay mode that helps clients communicate indirectly. It is an unofficial usage of port 8080, which is commonly used as an alternative HTTP port, but serves here as a medium for efficient, distributed file sharing.

port 8080 as FilePhile Relay

Which one is on your host

ask the machine, not the registry

The registry says what 8080 is registered to. What is listening on it right now is decided by the host, and only the host can be asked. Each of these prints the process behind the socket.

linux
ss -ltnp | grep ':8080\b'
macos
lsof -nP -iTCP:8080 -sTCP:LISTEN
windows
netstat -ano | findstr :8080

On Linux and Windows the process name comes back with the socket; on macOS lsof needs sudo to name a process that isn't yours. Match what it prints against the 3 entries above.

A port number is not a service. Anything may listen on 8080 — what you actually met is decided by the host, not the registry. If a service is missing here, it belongs in the registry.

contribute an entry