- Close the port if nothing on the host needs it.
- Identify the process that listens on it (commands below) before opening it in a firewall.
- Expose a service only to the networks that use it.
Port 136: PROFILE Naming System
Port 136 is assigned by IANA to profile (PROFILE Naming System).
How profile works
Other servicesThe client sends a request to port 136 and the profile service answers.
- Transport
- TCP · UDP
- Exposure risk
- not rated depends on the program listening
- Encryption
- Unknownnot stated by the registry
- IANA status
- Assigned1 registered service
- Range
- Well-known (0-1023)
- Category
- Other services
Is port 136 dangerous?
We have no specific security note for port 136. Its risk depends on the program actually listening on it. General advice for other services services:
IANA registry entries for port 136
| Service | Port | Transport | Description | Reference | Updated |
|---|---|---|---|---|---|
| profile | 136 | TCP, UDP | PROFILE Naming System | - | - |
// source: IANA service name and port number registry
Which program uses port 136, and is it reachable?
Linux
sudo ss -ltnup 'sport = :136' # process listening on 136
sudo lsof -nP -i :136macOS
sudo lsof -nP -i :136
Windows (PowerShell)
Get-NetTCPConnection -LocalPort 136 -State Listen | Select LocalAddress, OwningProcess Get-NetUDPEndpoint -LocalPort 136 netstat -ano | findstr :136
From another machine
nmap -p 136 -sV <host> sudo nmap -sU -p 136 <host> nc -zv <host> 136
Block it in the firewall
sudo ufw deny 136/tcp # Linux (ufw) New-NetFirewallRule -DisplayName "Block 136" -Direction Inbound -LocalPort 136 -Protocol TCP -Action Block # Windows
What is port 136 used for?
Port 136 is assigned by IANA to profile (PROFILE Naming System).
Is port 136 TCP or UDP?
Port 136 is registered for TCP and UDP.
Is it safe to open port 136?
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. Close the port if nothing on the host needs it.
How do I check if port 136 is open?
On Linux run "ss -ltnup 'sport = :136'", on macOS "lsof -nP -i :136", and on Windows "netstat -ano | findstr :136" to see the local process. From another machine, "nmap -p 136 <host>" shows whether it is reachable.