Port 6716Princity Agent

TCP port 6716 is assigned to Princity Agent, registered by ENSTEAM Sp. z o.o.

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

Technical Details

what runs on :6716

Princity Agent is registered on port :6716 over tcp to ENSTEAM Sp z.o.o., assigned July 2014. 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 :6716

this machine

# linux
sudo ss -tlpn 'sport = :6716'

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

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

another host

nmap -sV -p T:6716 <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 :6716

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

every listening transport is another surface to filter at the edge

security overview

no security notes recorded for :6716 yet

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

Record

iana registry entry

port: :6716
service: Princity Agent
transport: TCP
encryption: cleartext
assignment: iana registered
risk: 1/10safe
category: uncategorised
usage: IANA assigns this port to Princity Agent and lists ENSTEAM Sp. z o.o. as the registrant. The assignment alone does not establish what software commonly listens on it or how it is used.
lookups: 0rank 993
added: 2026-10-11
updated: 2026-10-11
references: IANA service name registry — port 6716

Something wrong?

This record is maintained by the engineers who use port 6716. 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-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 :6716, by lookups.

port	service	proto	category	risk	views
:6697	IRC over SSL	TCPtls	Security	caution	16.4k
:6679	IRC SSL	TCPtls	Security	caution	15.7k
:6771	Polycom Broadcast	UDP	Network Services	caution	13.2k
:6665	IRC	TCP	Network Services	caution	10.5k
:6660	IRC	TCP	Voice and Chat	caution	10.2k
:6699	WinMX	TCP	File Transfer	caution	4.5k
:6767	BMC Perform Agent	TCPUDP	System	safe	0
:6703	e-Design web	TCPUDP	Web Services	safe	0

risk mix of the 8 listed

safe25%
caution75%

2 of 8 encrypted

Port :6716Princity Agent

Technical Details

Security Information

Related Ports

Port 6716Princity Agent