Port 650OBEX

OBEX object-exchange traffic for legacy device file, contact, and media transfers.

transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
1/10

safe

lookups
0

rank 994 of 3,509 · top 28%

also known as Object Exchange, IrOBEX

Technical Details

what runs on :650

OBEX is a compact binary request/response protocol with a CONNECT negotiation followed by operations such as PUT, GET, SETPATH, and DISCONNECT. Messages contain response codes and length-prefixed headers; authentication is optional and the protocol itself does not provide encryption. IANA assigns this service on both TCP and UDP, although real-world OBEX profiles commonly use IrDA or Bluetooth RFCOMM instead of directly exposing port 650.

Security Information

exposure of :650

risk score

1/ 10safe

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

file transfer averages 3.6 across 159 ports — this one sits 2.6 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

OBEX is not encrypted by default, and authentication and authorization depend on the underlying device profile and implementation. Internet exposure is unnecessary and could permit unauthorized object access or denial-of-service attacks against legacy implementations; restrict it to the expected local device transport.

the 8 most looked-up other ports in file transfer — 159 ports carry that label.

risk mix of the 8 listed

  • caution100%

1 of 8 encrypted