01DMAF Casterudp · iana-registered · risk 1/10
UDP port assigned for the DMAF Caster service.
port 3574 as DMAF Caster →Port 35742 services
2 entries are registered on port 3574. 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
- 2
- transport
- udp · tcp
- 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
| port | service | risk | |||
|---|---|---|---|---|---|
| :3574 | DMAF Caster | UDP | — | safe | 0 |
| :3574 | DMAF Server | TCP | — | safe | 0 |
02DMAF Servertcp · iana-registered · risk 1/10
TCP port 3574 is assigned to DMAF Server, but its implementation and normal deployment are undocumented.
port 3574 as DMAF Server →Which one is on your host
The registry says what 3574 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 ':3574\b'- macos
lsof -nP -iTCP:3574 -sTCP:LISTEN- windows
netstat -ano | findstr :3574
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 3574 — 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