Port 601Reliable Syslog

Reliable Syslog transports log messages between clients and collectors, typically over a persistent TCP connection.

transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
3/10

caution

lookups
0

rank 994 of 2,020 · top 49%

also known as syslog-conn, RFC 3195 Reliable Syslog, BEEP Syslog

Technical Details

what runs on :601

The registry assigns this service to both TCP and UDP, although the standardized Reliable Syslog deployment uses a persistent TCP connection with BEEP session negotiation and framed messages. BEEP provides channel management and message framing around syslog records; encryption is not enabled by default. Traditional UDP syslog commonly uses port 514, while Syslog over TLS uses TCP port 6514.

Security Information

exposure of :601

risk score

3/ 10caution

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

network services averages 3.2 across 870 ports — this one sits 0.2 below.

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

Reliable Syslog is normally cleartext unless protected by an additional TLS tunnel or equivalent control, so exposed traffic can disclose log contents and permit message spoofing or injection. Internet-facing collectors may also be abused for log flooding and resource exhaustion; restrict access to known senders and prefer port 6514 for encrypted transport.

the 8 most looked-up other ports in network services — 870 ports carry that label.

risk mix of the 8 listed

  • caution100%

0 of 8 encrypted