TCP/UDP Port Finder
Search results for "known"
Port: 135/UDP
135/UDP - Known port assignments (20 records found)
- ServiceDetailsSource
- epmapDCE endpoint resolutionIANA
- Microsoft EPMAP (End Point Mapper), also known as DCE/RPC Locator service, used to remotely manage services including DHCP server, DNS server and WINS. Also used by DCOM (Unofficial)WIKI
- DCE endpoint resolution (Official)WIKI
- loc-srvLocation ServiceSANS
- threat[threat] W32.Blaster.WormBekkoame
- threat[threat] W32.CissiBekkoame
- threat[threat] W32.ExpletBekkoame
- threat[threat] W32.Francette.WormBekkoame
- threat[threat] W32.HLLW.GaobotBekkoame
- threat[threat] W32.HLLW.PolybotBekkoame
- threat[threat] W32.KassbotBekkoame
- threat[threat] W32.Kibuv.WormBekkoame
- threat[threat] W32.LovgateBekkoame
- threat[threat] W32.MaslanBekkoame
- threat[threat] W32.MytobBekkoame
- threat[threat] W32.ReatleBekkoame
- threat[threat] W32.SpybotBekkoame
- threat[threat] W32.WelchiaBekkoame
- threat[threat] W32.YahaBekkoame
- threat[threat] FemotBekkoame
Port: 135/TCP
135/TCP - Known port assignments (22 records found)
- ServiceDetailsSource
- DCE endpoint resolution (Official)WIKI
- epmapDCE endpoint resolutionIANA
- Microsoft EPMAP (End Point Mapper), also known as DCE/RPC Locator service, used to remotely manage services including DHCP server, DNS server and WINS. Also used by DCOM (Unofficial)WIKI
- loc-srvNCS local location brokerSANS
- threat[threat] SecefaBekkoame
- threat[threat] W32.KimanBekkoame
- threat[threat] FemotBekkoame
- threat[threat] W32.Blaster.WormBekkoame
- threat[threat] W32.Francette.WormBekkoame
- threat[threat] W32.ExpletBekkoame
- threat[threat] W32.Kibuv.WormBekkoame
- threat[threat] W32.LovgateBekkoame
- threat[threat] W32.MaslanBekkoame
- threat[threat] W32.MytobBekkoame
- threat[threat] W32.ReatleBekkoame
- threat[threat] W32.SpybotBekkoame
- threat[threat] W32.WelchiaBekkoame
- threat[threat] W32.YahaBekkoame
- threat[threat] W32.CissiBekkoame
- threat[threat] W32.HLLW.GaobotBekkoame
- threat[threat] W32.HLLW.PolybotBekkoame
- threat[threat] W32.KassbotBekkoame
Port: 1223/UDP
1223/UDP - Known port assignments (2 records found)
Port: 1223/TCP
1223/TCP - Known port assignments (2 records found)
Port: 1414/TCP
1414/TCP - Known port assignments (2 records found)
Port: 1883/TCP
1883/TCP - Known port assignments (2 records found)
Port: 1883/UDP
1883/UDP - Known port assignments (2 records found)
Port: 5070/TCP
5070/TCP - Known port assignments (2 records found)
- ServiceDetailsSource
- vtsasVersaTrans Server Agent ServiceIANA
- Binary Floor Control Protocol (BFCP), published as RFC 4582, is a protocol that allows for an additional video channel (known as the content channel) alongside the main video channel in a video-conferencing call that uses SIP. Also used for Session Initiation Protocol (SIP) preferred port for PUBLISH on SIP Trunk to Cisco Unified Presence Server (CUPS) (Official)WIKI
Port: 30464/TCP
30464/TCP - Known port assignments (3 records found)
- ServiceDetailsSource
- UnassignedIANA
- threat[threat] SMTP ETRN overflow A known Netwin ESMTP exploit binds a root shell to TCP port 30464.Bekkoame
- trojan[trojan] Slapper. Backdoor / Worm / IRC trojan / Proxy / Distributed DoS tool. Works on Unix (Linux - SuSe, Mandrake, RedHat, Slackware, Debian, Gentoo), together with Apache Web server. Aliases: Linux.Slapper.Worm, Apache/mod_ssl Worm, PUD, ELF/SlapperSimovits
About TCP/UDP ports
TCP port 135 uses the Transmission Control Protocol. TCP is one of the main protocols in TCP/IP networks. TCP is a connection-oriented protocol, it requires handshaking to set up end-to-end communications. Only when a connection is set up user's data can be sent bi-directionally over the connection.
Attention! TCP guarantees delivery of data packets on port 135 in the same order in which they were sent. Guaranteed communication over TCP port 135 is the main difference between TCP and UDP. UDP port 135 would not have guaranteed communication as TCP.
UDP on port 135 provides an unreliable service and datagrams may arrive duplicated, out of order, or missing without notice. UDP on port 135 thinks that error checking and correction is not necessary or performed in the application, avoiding the overhead of such processing at the network interface level.
UDP (User Datagram Protocol) is a minimal message-oriented Transport Layer protocol (protocol is documented in IETF RFC 768).
Application examples that often use UDP: voice over IP (VoIP), streaming media and real-time multiplayer games. Many web applications use UDP, e.g. the Domain Name System (DNS), the Routing Information Protocol (RIP), the Dynamic Host Configuration Protocol (DHCP), the Simple Network Management Protocol (SNMP).
TCP vs UDP - TCP: reliable, ordered, heavyweight, streaming; UDP - unreliable, not ordered, lightweight, datagrams.
Attention! TCP guarantees delivery of data packets on port 135 in the same order in which they were sent. Guaranteed communication over TCP port 135 is the main difference between TCP and UDP. UDP port 135 would not have guaranteed communication as TCP.
UDP on port 135 provides an unreliable service and datagrams may arrive duplicated, out of order, or missing without notice. UDP on port 135 thinks that error checking and correction is not necessary or performed in the application, avoiding the overhead of such processing at the network interface level.
UDP (User Datagram Protocol) is a minimal message-oriented Transport Layer protocol (protocol is documented in IETF RFC 768).
Application examples that often use UDP: voice over IP (VoIP), streaming media and real-time multiplayer games. Many web applications use UDP, e.g. the Domain Name System (DNS), the Routing Information Protocol (RIP), the Dynamic Host Configuration Protocol (DHCP), the Simple Network Management Protocol (SNMP).
TCP vs UDP - TCP: reliable, ordered, heavyweight, streaming; UDP - unreliable, not ordered, lightweight, datagrams.
Your IP address
3.145.130.31