Port 1799NETRISK

NETRISK is an uncharacterized service assigned to TCP and UDP port 1799.

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

Technical Details

what runs on :1799

NETRISK is registered on port :1799 over tcp and udp to Kevin Green. 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 :1799

this machine

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

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

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

another host

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

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

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

Record

iana registry entry

port: :1799
service: NETRISK
transport: TCPUDP
encryption: cleartext
assignment: iana registered
risk: 1/10safe
category: uncategorised
usage: Port 1799 is assigned to the NETRISK service on both TCP and UDP. The assignment is registered to Kevin Green, but the registry provides no product, protocol, or deployment details.
lookups: 0rank 993
added: 2026-09-11
updated: 2026-09-11
references: IANA service name registry — port 1799

Something wrong?

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

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

port	service	proto	category	risk	views
:1863	Microsoft Notification Protocol	TCP	Voice and Chat	caution	15.9k
:1755	Microsoft Media Services	TCPUDP	Streaming	caution	13.8k
:1812	RADIUS Auth Protocol	TCPUDP	Security	caution	12.0k
:1801	MSMQ	TCPUDP	Network Services	caution	8.9k
:1813	RADIUS Accounting	TCPUDP	Security	caution	7.2k
:1762	CFT File Transfer	TCPUDP	File Transfer	caution	5.6k
:1761	Zenworks Remote Control	TCP	Remote Access	caution	5.6k
:1761	CFT 0	UDP	Network Services	caution	5.0k

risk mix of the 8 listed

caution100%

0 of 8 encrypted

Port :1799NETRISK

Technical Details

Security Information

Related Ports

Port 1799NETRISK