whatportis.com
suggest an edit →

Port 604TUNNEL Profile (BEEP)

The TUNNEL Profile for BEEP (Blocks Extensible Exchange Protocol) enables the creation of application-layer tunnels over TCP. This facilitates encapsulating various application protocols transparently, allowing peer-to-peer communication, protocol multiplexing, and flexible data flow management within the BEEP framework. It is a versatile mechanism mainly employed in network services and security contexts where tunneling is required without developing new transport protocols..

inSecurityNetwork Services
transport
tcp

single transport

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
4/10

caution

lookups
5,145

rank 907 of 993 · top 91%

Technical Details

what runs on :604

The TUNNEL Profile is developed within the framework of BEEP, a protocol framework designed for building application protocols with features like framing, multiplexing, and channel management over a single transport connection. The TUNNEL profile extends BEEP's capabilities by enabling peers to form an application-layer tunnel, which essentially acts like a virtual point-to-point link between two endpoints operating over the existing BEEP session.

This tunnel allows encapsulated application data, potentially from diverse protocols, to traverse a single TCP connection in an efficient, multiplexed manner. It supports multiple logical communication streams within one connection, reducing overhead and simplifying the management of transport sessions. Encapsulation via tunneling also aids in working through NAT devices and firewalls facilitating application-layer protocol negotiations and data transfer.

TUNNEL Profile operates exclusively over TCP, leveraging BEEP's framing features to maintain reliable, ordered delivery of encapsulated data streams. Because BEEP and its profiles are designed to be transport independent within TCP, SCTP is generally not used here. The tunneling capability is instrumental for protocol bridging, firewall traversal, and dynamic network services where normal protocol operation is limited by network constraints.

Security Information

exposure of :604

risk score

4/ 10caution

worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.

security averages 3.8 across 216 ports — this one sits 0.2 above.

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

Common Vulnerabilities:

  • Since TUNNEL Profile facilitates application tunneling, it might be exploited for bypassing network security controls, such as firewalls or intrusion detection systems.
  • The lack of encryption in the protocol exposes tunneled data to potential eavesdropping or interception.
  • Without strict authentication, unauthorized peers could establish tunnels leading to data leakage or exploitation.

Common Mitigations:

  • Implement strong authentication mechanisms between peers to ensure tunnels are established only with trusted entities.
  • Employ encryption protocols (e.g., TLS) alongside BEEP tunneling sessions to protect data in transit.
  • Monitor network perimeter devices to detect and block unauthorized tunnel creation or suspicious activity on port 604.
  • Apply strict access controls and logging to quickly identify anomalous tunnel usage.

Related Ports

all 216 in security →

the 8 most looked-up other ports in security — 216 ports carry that label.

portservicerisk
:8881Atlasz Secure Servercaution
:443HTTPScaution
:8291Winbox MikroTik Admincaution
:3268Microsoft Global Catalog (GC)caution
:135Microsoft EPMAPcaution
:3128Squid Proxy HTTPcaution
:8080HTTP Alternatecaution
:7000Vuze HTTPS Trackercaution

risk mix of the 8 listed

  • caution100%

3 of 8 encrypted