CyberHunter
Local dataset, no network
// Directory & authentication

Port 3539: IBM Directory Server SSL

Port 3539 is assigned by IANA to ibm-diradm-ssl (IBM Directory Server SSL).

3539

How ibm-diradm-ssl works

Directory & authentication
userdirectoryibm-diradm-sslresponse userdirectoryibm-diradm-sslresponse

The client proves who it is on port 3539 and gets an answer (or a ticket) it can use with other services.

Transport
TCP · UDP
Exposure risk
not rated depends on the program listening
Encryption
Unknownnot stated by the registry
IANA status
Assigned1 registered service
Range
Registered (1024-49151)
01 Security

Is port 3539 dangerous?

We have no specific security note for port 3539. Its risk depends on the program actually listening on it. General advice for directory & authentication services:

  • Keep directory and authentication services on internal networks.
  • Require signing or TLS and disable anonymous queries.
  • Monitor authentication failures for spraying and brute force.
02 Registry

IANA registry entries for port 3539

ServicePortTransportDescriptionReferenceUpdated
ibm-diradm-ssl 3539 TCP, UDP IBM Directory Server SSL - 2002-07

// source: IANA service name and port number registry

03 Check it

Which program uses port 3539, and is it reachable?

Linux

sudo ss -ltnup 'sport = :3539'      # process listening on 3539
sudo lsof -nP -i :3539

macOS

sudo lsof -nP -i :3539

Windows (PowerShell)

Get-NetTCPConnection -LocalPort 3539 -State Listen | Select LocalAddress, OwningProcess
Get-NetUDPEndpoint -LocalPort 3539
netstat -ano | findstr :3539

From another machine

nmap -p 3539 -sV <host>
sudo nmap -sU -p 3539 <host>
nc -zv <host> 3539

Block it in the firewall

sudo ufw deny 3539/tcp                                         # Linux (ufw)
New-NetFirewallRule -DisplayName "Block 3539" -Direction Inbound -LocalPort 3539 -Protocol TCP -Action Block  # Windows
04 FAQ
What is port 3539 used for?

Port 3539 is assigned by IANA to ibm-diradm-ssl (IBM Directory Server SSL).

Is port 3539 TCP or UDP?

Port 3539 is registered for TCP and UDP.

Is it safe to open port 3539?

It depends on the program that listens on it. Open it only for a service you know and only to the networks that need it. Keep directory and authentication services on internal networks.

How do I check if port 3539 is open?

On Linux run "ss -ltnup 'sport = :3539'", on macOS "lsof -nP -i :3539", and on Windows "netstat -ano | findstr :3539" to see the local process. From another machine, "nmap -p 3539 <host>" shows whether it is reachable.

05 Related

Latest vulnerability news

All news