01DTAGtcp · udp · iana-registered · risk 1/10
Legacy DTAG service assignment using TCP and UDP port 352.
port 352 as DTAG →Port 3522 services
2 entries are registered on port 352. It is a well-known port (0–1023) — assignments here are IANA's, and a service found on one is usually the service that was assigned it.
- entries
- 2
- transport
- tcp · udp
- in transit
- 0/2
- worst risk
- 1/10
services registered on this number
2 transports in use
entries encrypted on the wire
2 of 2 iana-registered
Services on this port
02bhoedap4tcp · udp · iana-registered · risk 1/10
bhoedap4 is an obscure TCP/UDP service assignment with no identified public protocol or current observed deployments.
port 352 as bhoedap4 →Which one is on your host
The registry says what 352 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 ':352\b'- macos
lsof -nP -iTCP:352 -sTCP:LISTEN- windows
netstat -ano | findstr :352
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 2 entries above.
A port number is not a service. Anything may listen on 352 — 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