Port 535Internet Inter-ORB Protocol

CORBA object requests and replies exchanged using the Internet Inter-ORB Protocol (IIOP).

transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
4/10

caution

lookups
0

rank 994 of 2,734 · top 36%

also known as iiop, CORBA IIOP

Technical Details

what runs on :535

IIOP is the Internet mapping of CORBA's GIOP. A typical deployment establishes a TCP connection, exchanges length-framed GIOP messages, and performs request/reply operations against object references whose profiles identify the server endpoint. Standard IIOP is not encrypted; deployments requiring transport protection use SSL/TLS variants such as IIOP over SSL, commonly associated with port 684. Although this registry assignment lists both TCP and UDP, conventional IIOP implementations primarily use TCP.

Security Information

exposure of :535

risk score

4/ 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.0 across 1,020 ports — this one sits 1.0 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 · udp

udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite

security overview

An exposed IIOP endpoint can disclose CORBA object references and expose remotely invokable methods, depending on ORB configuration and application authorization. It should generally remain restricted to trusted application networks; standard IIOP provides neither encryption nor authentication by itself, and ORB parsers and application objects add attack surface.

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

risk mix of the 8 listed

  • caution100%

0 of 8 encrypted