# WHATPORT(2048)

## NAME

port 2048 — dls-monitor (registration only) — Registered dls-monitor with no documentation; notable mainly for how often UDP scans get a response here.

Protocol: TCP/UDP  
IANA registry

## DESCRIPTION

IANA registers dls-monitor on TCP and UDP 2048 with no description, assignee or reference, paired with dls on 2047. TCP 2048 is as rare as its neighbours, but Nmap's frequency data is an outlier for UDP: 2048/udp responds on roughly 2% of scanned hosts, far above the surrounding ports and without any documented service to explain it. Whatever produces that, the registry name is not a reliable guide to what you have found.

## EXPOSURE

**Expose with care.** The label is meaningless and the UDP responses are unexplained; identify the process on the host before treating anything here as benign or exposing it.

## CHECK

```sh
sudo lsof -nP -iTCP:2048 -sTCP:LISTEN
```

## SEE ALSO

- iana — [IANA Service Name and Transport Protocol Port Number Registry](https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml) (iana.org)
- source — [nmap-services — Nmap port frequency data](https://github.com/nmap/nmap/blob/master/nmap-services) (github.com)

---

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