Registry assignments, software defaults and local listeners are different things. A port number alone does not identify or secure a service.
Software, die diesen Port verwendet (3 Programme)
Community software entries: links are references, not individual verification.
Windows RPC
WindowsRemoteService
DCOM Distributed Component
Distributed
Microsoft RPC
MicrosoftRemoteService
Nutzungshinweise
- Prüfe vor der Verwendung von Port 135, ob er bereits von anderen Diensten belegt ist
- Bei Portkonflikten kannst du andere Ports verwenden oder den Dienst beenden, der den Port belegt
Häufig gestellte Fragen
What is port 135 used for?
Port 135 sits in the System category. This page lists the registered purpose and the software commonly associated with it; to see what is actually listening on a specific machine, check the process with ss/netstat.
Is port 135 TCP or UDP?
The registered protocol on this page is TCP. The same number behaves independently on each protocol: TCP may be listening while UDP is idle, so check them separately.
How do I check if port 135 is in use?
On Linux: sudo ss -tlnp 'sport = :135' for an exact port match. On macOS: sudo lsof -nP -iTCP:135 -sTCP:LISTEN. On Windows PowerShell: Get-NetTCPConnection -LocalPort 135 -State Listen. A listener counts as confirmed only when you can see the bind address and process name; without root/admin you will not see other users' processes.
Is port 135 secure? Should I open it in my firewall?
A port number has no inherent security — it depends on whether the listening service is correctly configured and whether it needs exposure at all. Keep loopback/internal-only services firewalled; where public access is required, pair it with source restrictions, VPN or authentication.
Kurzinfo
- Port
- 135
- Protokoll
- TCP
- Kategorien
- System
- Nutzungsstatus
- 3 Programme nutzen diesen Port
Brauchst du Hilfe?
Wenn du fehlerhafte Angaben findest oder Informationen ergänzen möchtest, reiche bitte eine Korrektur ein.
Korrektur einreichen