Port 605SOAP over BEEP

SOAP web-service messages transported over the Blocks Extensible Exchange Protocol (BEEP).

transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
2/10

safe

lookups
0

rank 994 of 1,362 · top 73%

also known as soap-beep

Technical Details

what runs on :605

SOAP over BEEP uses BEEP's session-oriented, channelized framing to exchange XML SOAP messages, with a BEEP greeting and profile negotiation before application traffic. SOAP request/response and fault messages are carried through the SOAP profile; authentication and TLS can be negotiated through BEEP profiles, but are not inherent in SOAP itself. The registry lists both TCP and UDP, although BEEP deployments are normally associated with a reliable connection-oriented transport.

Security Information

exposure of :605

risk score

2/ 10safe

routine exposure. this port is rarely the way in on its own — keep it patched and logged and move on.

web services averages 3.8 across 121 ports — this one sits 1.8 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

By default, SOAP and BEEP traffic need not be encrypted, so credentials and message contents may be exposed unless TLS or equivalent protection is configured. Internet exposure is uncommon; restrict access to known peers and ensure XML parsers and SOAP handlers enforce authentication, input limits, and protection against XML-based attacks.

the 8 most looked-up other ports in web services — 121 ports carry that label.

risk mix of the 8 listed

  • safe13%
  • caution88%

0 of 8 encrypted