Port 135DCE/RPC Endpoint Mapper

_Port 135 is primarily used by Microsoft RPC Endpoint Mapper, a crucial function for locating network services used by Windows systems and DCE/RPC frameworks. It facilitates communication between clients and available services by helping clients determine what dynamic ports specific RPC services are listening on._.

transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
4/10

caution

lookups
16,691

rank 172 of 993 · top 17%

1 other service is registered on port 135. compare all 2

Technical Details

what runs on :135

Port 135 is designated for the DCE/RPC Endpoint Mapper, which is fundamental to the operation of distributed computing environments — particularly within Windows networks. When a Remote Procedure Call (RPC) is initiated, it first contacts the Endpoint Mapper on port 135 to discover the dynamically-assigned port number for the specific service required. This applies to numerous RPC-based Microsoft services, including DCOM, MS Exchange, Active Directory, and more.

The Endpoint Mapper listens over both TCP and UDP, acting as a directory service for applications to publish and query network endpoints. It enables seamless client-server communication by providing the necessary network endpoint details, typically on dynamically allocated high-numbered ephemeral ports.

Distributed Computing Environment (DCE) RPC and Microsoft’s implementation use port 135 as the starting point for service discovery, after which the actual communication occurs through dynamically assigned ports negotiated by the mapper. This multi-port architecture underpins many core Windows administrative and service protocols.

Security Information

exposure of :135

risk score

4/ 10caution

worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.

remote access averages 4.0 across 110 ports — this one sits level with it.

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

Common Vulnerabilities

  • Exposure of Port 135 can enable network reconnaissance and enumeration, aiding attackers in identifying available RPC services for exploitation.
  • Exploitable attack surface for vulnerabilities like MS03-026 (Blaster worm) and MS08-067 (Conficker worm), both targeting flaws in RPC services.
  • Allows for lateral movement if exploited, providing access to sensitive Windows services such as SMB sharing and remote management.
  • Can be leveraged in denial of service attacks, causing disruptions to RPC-dependent services.

Common Mitigations

  • Restrict access to port 135 at network boundaries using firewalls or access control lists, especially from untrusted networks.
  • Apply the latest security patches to RPC services and Windows systems to mitigate known vulnerabilities.
  • Use host-based firewalls to limit RPC exposure on endpoints.
  • Implement network segmentation to isolate critical systems, minimizing lateral movement.
  • Prefer secure alternatives or tunnels (e.g., VPNs) when remote RPC management is required, avoiding direct exposure.
  • Leverage intrusion detection and monitoring for unusual activity patterns associated with RPC use or exploitation.

the 8 most looked-up other ports in remote access — 110 ports carry that label.

risk mix of the 8 listed

  • safe13%
  • caution88%

0 of 8 encrypted