Port 9396fjinvmgr

The fjinvmgr service is assigned to TCP and UDP port 9396, with no public protocol details recorded.

transport: tcp · udp
in transit: cleartext
assignment: official
risk: 1/10
lookups: 0

Technical Details

what runs on :9396

fjinvmgr is registered on port :9396 over tcp and udp to Yutaka Ono. We don't have a technical write-up for it beyond the IANA registry entry.

In nmap's internet-wide scan data this port is found open rarely. What's listening is often not the registered service, so check before you assume.

find what's listening on :9396

this machine

# linux
sudo ss -tulpn 'sport = :9396'

# macos / bsd
sudo lsof -nP -i :9396

# windows (then: tasklist /FI "PID eq <pid>")
netstat -ano | findstr :9396

another host

nmap -sV -p T:9396 <host>
sudo nmap -sU -sV -p U:9396 <host>

run it? the handshake, the implementations you meet in the wild and the flags that matter come from the engineers who do.

add technical details

Security Information

exposure of :9396

risk score

1/ 10safe

routine exposure. this port is rarely the way in on its own — keep it patched and logged and move on.

in transit

cleartext

credentials and payloads are readable by anyone on path

assignment

official

registered with iana for this service — scanners fingerprint it by number

reachable over

tcp · udp

udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite

security overview

no security notes recorded for :9396 yet

known exploits, hardening advice, what a compromise looks like — suggest an edit if you know its exposure.

Record

iana registry entry

port: :9396
service: fjinvmgr
transport: TCPUDP
encryption: cleartext
assignment: iana registered
risk: 1/10safe
category: uncategorised
usage: fjinvmgr is the IANA-registered service name for TCP and UDP port 9396. The assignment is registered to Yutaka Ono, but the registry provides no product or protocol context.
lookups: 0rank 993
added: 2026-09-07
updated: 2026-09-07
references: IANA service name registry — port 9396

Something wrong?

This record is maintained by the engineers who use port 9396. Every field on it is editable — change what's wrong, say how you know, and a reviewer publishes it, usually within a minute. Last touched 2026-09-07.

01edit any field on a page of its own
02a model checks it for accuracy and spam
03clean and confident goes live immediately

edit this record →back to the registry

Related Ports

browse categories →

ports registered around :9396, by lookups.

port	service	proto	category	risk	views
:9421	MooseFS Master Server	TCP	Databases	caution	10.2k
:9418	Git Pack Transfer	TCPUDP	File Transfer	caution	10.2k
:9422	MooseFS Chunk Servers	TCP	File Transfer	caution	9.9k
:9420	MooseFS Master-Chunk	TCP	File Transfer	caution	9.0k
:9400	Samsung TWAIN for Network Server	TCPUDP	—	safe	0
:9443	WSO2 Tungsten HTTPS	TCPUDPtls	Web Services	risk	0
:9397	MpIdcAgt	TCPUDP	—	safe	0
:9444	WSO2 ESB Administration Console	TCPUDPtls	Web Services	risk	0

risk mix of the 8 listed

safe25%
caution50%
risk25%

2 of 8 encrypted

Port :9396fjinvmgr

Technical Details

Security Information

Related Ports

Port 9396fjinvmgr