Port 3159NavegaWeb Tarification

Port 3159 is assigned to NavegaWeb Tarification, registered to Miguel Angel Fernand.

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

also known as navegaweb-port

Technical Details

what runs on :3159

NavegaWeb Tarification is registered on port :3159 over tcp and udp to Miguel Angel Fernand. 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 :3159

this machine

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

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

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

another host

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

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

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

Record

iana registry entry

port: :3159
service: NavegaWeb Tarification
transport: TCPUDP
encryption: cleartext
assignment: iana registered
risk: 1/10safe
category: uncategorised
usage: IANA assigns TCP and UDP port 3159 to NavegaWeb Tarification and lists Miguel Angel Fernand as the registrant. No established implementation or common deployment is known.
lookups: 0rank 993
added: 2026-09-27
updated: 2026-09-27
references: IANA service name registry — port 3159

Something wrong?

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

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

port	service	proto	category	risk	views
:3128	Tatsoft Default HTTP Proxy	TCP	Web Services	caution	46.8k
:3128	Squid Proxy HTTP	TCP	Web Services	caution	45.8k
:3100	Tatsoft HTTP Port	TCP	Web Services	caution	19.4k
:3101	BlackBerry BES Cloud Comm	TCP	Cloud	caution	7.1k
:3162	SFLM	TCPUDP	—	safe	0
:3141	VMODEM	TCPUDP	—	safe	0
:3211	Avocent Secure Management	TCPUDPtls	Security	safe	0
:3170	SERVERVIEW-ASN	TCPUDP	—	safe	0

risk mix of the 8 listed

safe50%
caution50%

1 of 8 encrypted

Port :3159NavegaWeb Tarification

Technical Details

Security Information

Related Ports

Port 3159NavegaWeb Tarification