# WHATPORT(58080)

## NAME

port 58080 — Unassigned — commonly an alternate HTTP port — 8080 with a 5 bolted on: an alternate HTTP port people choose by hand.

Protocol: TCP  
IANA registry

## DESCRIPTION

58080 has no IANA registration — RFC 6335 keeps this range out of the registry — but its shape is not accidental. Administrators pick it as a second or third HTTP port when 80, 8080, and 8081 are already taken, so what usually answers is a servlet container, a reverse proxy, or an application's admin UI. Nmap's nmap-services lists it "unknown" at 0.000380, and SANS ISC records probes without naming a service. An HTTP HEAD request will tell you more in one second than any registry lookup.

## EXPOSURE

**Expose with care.** If it is plain HTTP fronting an admin interface, treat it as never — cleartext credentials on an unusual port are still cleartext credentials. Put it behind TLS and authentication, or behind a VPN.

## CHECK

```sh
curl -s -m 5 -I http://TARGET:58080/
```

## SEE ALSO

- spec — [RFC 6335 — Dynamic Ports (49152-65535)](https://www.rfc-editor.org/rfc/rfc6335.html) (rfc-editor.org)
- iana — [IANA port registry — search 58080 (no assignment)](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?search=58080) (iana.org)
- source — [nmap/nmap — nmap-services frequency data](https://github.com/nmap/nmap/blob/master/nmap-services) (github.com)

---

HTML: <https://whatport.net/58080/> · JSON: <https://whatport.net/58080.json> · full dataset: <https://whatport.net/ports.json>
