Try https://grc.com/x/ne.dll?bh0bkyd2
and run the test for System Ports from 1 to 1056.

Port Authority Database
Port 135

Name: dcom-scm
Purpose: DCOM Service Control Manager
Description: Microsoft’s DCOM (Distributed, i.e. networked, COM) Service Control Manager (also known as the RPC Endpoint Mapper) uses this port in a manner similar to SUN’s UNIX use of port 111. The SCM server running on the user’s computer opens port 135 and listens for incoming requests from clients wishing to locate the ports where DCOM services can be found on that machine.
Related Ports: 111

Background and Additional Information: Port 135 is certainly not a port that needs to be, or should be, exposed to the Internet. Hacker tools such as “epdump” (Endpoint Dump) are able to immediately identify every DCOM-related server/service running on the user’s hosting computer and match them up with known exploits against those services.
Any machines placed behind a NAT router (any typical residential or small business broadband IP-sharing router) will be inherently safe. And any good personal software firewall should also be able to easily block port 135 from external exposure. That’s what you want.

In addition, many security conscious ISPs are now blocking port 135 along with the notorious “NetBIOS Trio” of ports (137-139). So even without any of your own proactive security, you may find that port 135 has been blocked and stealthed on your behalf by your ISP.

Going Further: Closing port 135

The widespread exposure and insecurity of this port has generated a great deal of concern among PC gurus. This has resulted in several approaches to shutting down the Windows DCOM server and firmly closing port 135 once and for all. Although applications may be “DCOM enabled” or “DCOM aware”, very few, if any, are actually dependent upon the presence of its services. Consequently, it is usually possible (and generally desirable if you’re comfortable doing such things) to shut down DCOM and close port 135 without any ill effects. (The fewer things running in a Windows system, the fewer things to suck up RAM and slow everything else down.)

If you are curious about taking control of and terminating another unnecessary Windows “service”, the following links will provide you with the information and instructions you’ll need:

For Intrepid Experts ONLY

See the first question on this Microsoft Knowledgebase page under "General COM Security Issues: How do I enable or disable DCOM?

For Windows 2000 users, this page by UK Security Online provides a nice step-by-step approach using Microsoft’s provided DCOM configuration utility.

A page of assorted DCOM info: http://accs-net.com/smallfish/dcom.htm

If your 135 has problems, see: http://www.grc.com/port_135.htm