Port 25900TASP Network Comm

IANA lists TCP/UDP port 25900 as TASP Network Comm, registered to Martin Ellis; no established public deployment is known.

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

Technical Details

what runs on :25900

TASP Network Comm is registered on port :25900 over tcp and udp to Martin Ellis, assigned November 2004. 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 never observed open, so if it's open on your network it's more likely a custom or misconfigured service than the registered one.

find what's listening on :25900

this machine

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

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

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

another host

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

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

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

Record

iana registry entry

port: :25900
service: TASP Network Comm
transport: TCPUDP
encryption: cleartext
assignment: iana registered
risk: 1/10safe
category: uncategorised
usage: The registry assigns this port to TASP Network Comm and lists Martin Ellis as the registrant. Nmap scan data has not observed it open, and no widely recognized use is known.
lookups: 0rank 993
added: 2026-10-19
updated: 2026-10-19
references: IANA service name registry — port 25900

Something wrong?

This record is maintained by the engineers who use port 25900. 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-10-19.

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

port	service	proto	category	risk	views
:25888	Xfire Game Server Tracking	UDP	Gaming	caution	13.4k
:25901	NIObserver	TCPUDP	—	safe	0
:25902	NILinkAnalyst	TCPUDP	—	safe	0
:25903	NIProbe	TCPUDP	—	safe	0
:25954	Bitfighter game server	UDP	Gaming	safe	0
:25955	Bitfighter master server	UDP	Gaming	safe	0

risk mix of the 6 listed

safe83%
caution17%

0 of 6 encrypted

Port :25900TASP Network Comm

Technical Details

Security Information

Related Ports

Port 25900TASP Network Comm