01JEOL Network Services Dynamic Discovery Protocol 4udp · iana-registered · risk 1/10
JEOL Network Services Dynamic Discovery Protocol 4 uses UDP port 6244 for service discovery.
port 6244 as JEOL Network Services Dynamic Discovery Protocol 4 →Port 62442 services
2 entries are registered on port 6244. 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 | |||
|---|---|---|---|---|---|
| :6244 | JEOL Network Services Dynamic Discovery Protocol 4 | UDP | Network Services | safe | 0 |
| :6244 | JEOL Network Services Data Transport Protocol 4 | TCP | Network Services | safe | 0 |
02JEOL Network Services Data Transport Protocol 4tcp · iana-registered · risk 1/10
TCP port 6244 is assigned to JEOL Network Services Data Transport Protocol 4; broader use is not established.
port 6244 as JEOL Network Services Data Transport Protocol 4 →filed underNetwork Services
Which one is on your host
The registry says what 6244 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 ':6244\b'- macos
lsof -nP -iTCP:6244 -sTCP:LISTEN- windows
netstat -ano | findstr :6244
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 6244 — 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