Port 5020zenginkyo-1

The zenginkyo-1 service assignment on TCP and UDP port 5020, registered to Masashi Suzaki.

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

Technical Details

what runs on :5020

zenginkyo-1 is registered on port :5020 over tcp and udp to Masashi Suzaki. 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 :5020

this machine

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

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

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

another host

nmap -sV -p T:5020 <host>
sudo nmap -sU -sV -p U:5020 <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 :5020

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 :5020 yet

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

Record

iana registry entry

port: :5020
service: zenginkyo-1
transport: TCPUDP
encryption: cleartext
assignment: iana registered
risk: 1/10safe
category: uncategorised
usage: IANA assigns TCP and UDP port 5020 to the zenginkyo-1 service. The assignment is registered to Masashi Suzaki, but publicly documented implementation and deployment details are not available here.
lookups: 0rank 993
added: 2026-09-14
updated: 2026-09-14
references: IANA service name registry — port 5020

Something wrong?

This record is maintained by the engineers who use port 5020. 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-14.

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 :5020, by lookups.

port	service	proto	category	risk	views
:5001	Iperf	TCPUDP	Network Services	caution	27.7k
:5001	Commplex-Link	TCP	Network Services	caution	24.9k
:5001	Slingbox	TCP	Streaming	caution	22.4k
:5000	Commplex Main	TCP	Web Services	caution	15.4k
:5070	BFCP	TCP	Network Services	caution	15.2k
:5061	SIP over TLS	TCP	Security	caution	14.4k
:5004	RTP Media Data	TCP	Streaming	safe	13.0k
:5000	UPnP Device Interop	TCP	Network Services	caution	12.7k

risk mix of the 8 listed

safe13%
caution88%

0 of 8 encrypted

Port :5020zenginkyo-1

Technical Details

Security Information

Related Ports

Port 5020zenginkyo-1