TCP/UDP Port Finder
Search results for "linux"
Port: 33568/TCP
33568/TCP - Known port assignments (5 records found)
- ServiceDetailsSource
- UnassignedIANA
- lion[trojan] LionSANS
- t0rnrootkit[trojan] T0rn RootkitSANS
- trojan[trojan] li0n. Worm / Steals passwords / Rootkit dropper / Hacking tool / Distributed DoS tool. Works on Unix (Linux), together with BIND 8.2. Aliases: The Lion worm, Linux/Lion, 1i0n, LionSimovits
- trojan[trojan] T0rn Rootkit. Rootkit. Works on Unix (Linux). Aliases: Torn RootkitSimovits
Port: 47017/TCP
47017/TCP - Known port assignments (4 records found)
Port: 54321/TCP
54321/TCP - Known port assignments (9 records found)
- ServiceDetailsSource
- Xsan. Xsan Filesystem AccessApple
- Dynamic and/or Private PortsIANA
- threat[threat] Back Orifice 2000Bekkoame
- threat[threat] School BusBekkoame
- schoolbus[trojan] School BusSANS
- trojan[trojan] Back Orifice 2000. Remote Access. Works on Windows 95, 98 and NT. XOR, TripleDES, AES and five other encryption algorithms. Aliases: BackOrifice2K.InstSimovits
- trojan[trojan] School Bus. Remote Access / Steals passwords. Works on Windows 95, 98 and ME. Aliases: Backdoor.SchoolBus.A, SchoolB.C, ScBusSimovits
- trojan[trojan] yoyo. Rootkit / Remote Access. Works on Unix (Linux).Simovits
- backorifice2000[trojan] Back Orifice 2000SANS
Port: 60001/TCP
60001/TCP - Known port assignments (5 records found)
Port: 60008/TCP
60008/TCP - Known port assignments (6 records found)
- ServiceDetailsSource
- Dynamic and/or Private PortsIANA
- Xsan. Xsan Filesystem AccessApple
- lion[trojan] LionSANS
- t0rnrootkit[trojan] T0rn RootkitSANS
- trojan[trojan] li0n. Worm / Steals passwords / Rootkit dropper / Hacking tool / Distributed DoS tool. Works on Unix (Linux), together with BIND 8.2. Aliases: The Lion worm, Linux/Lion, 1i0n, LionSimovits
- trojan[trojan] T0rn Rootkit. Rootkit. Works on Unix (Linux). Aliases: Torn RootkitSimovits
Port: 65000/TCP
65000/TCP - Known port assignments (13 records found)
- ServiceDetailsSource
- Xsan. Xsan Filesystem AccessApple
- Dynamic and/or Private PortsIANA
- threat[threat] RoxratBekkoame
- threat[threat] Sockets des TroieBekkoame
- threat[threat] StacheldrahtBekkoame
- devil[trojan] DevilSANS
- socketsdestroie[trojan] Sockets des TroieSANS
- stacheldrahtagent[trojan] Stacheldraht agent - handlerSANS
- stacheldraht[trojan] StacheldrahtSANS
- trojan[trojan] Devil. Remote Access. Works on Windows 95, 98 and NT. Aliases: Backdoor.Devil, Trojan.Win32.FloodSimovits
- trojan[trojan] Sockets des Troie. Remote Access / ICQ trojan / Virus. Works on Windows 95 and 98, together with ICQ. Features as telnet and finger. Aliases: Sockets23, Lame, BACKDOOR.KAMIKAZE, IRC_TROJAN, TROJ_BACKDOOR, W32/Cheval.gen , Backdoor.Sockets23, Control Du Sockets, W32.HLLP.DeTroie, DeTroie.drpSimovits
- trojan[trojan] Stacheldraht. Distributed DoS tool / IRC trojan. Works on Unix (Sun and Linux).Simovits
- threat[threat] DevilBekkoame
Port: 65289/TCP
65289/TCP - Known port assignments (3 records found)
About TCP/UDP ports
TCP port 33568 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 33568 in the same order in which they were sent. Guaranteed communication over TCP port 33568 is the main difference between TCP and UDP. UDP port 33568 would not have guaranteed communication as TCP.
UDP on port 33568 provides an unreliable service and datagrams may arrive duplicated, out of order, or missing without notice. UDP on port 33568 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 33568 in the same order in which they were sent. Guaranteed communication over TCP port 33568 is the main difference between TCP and UDP. UDP port 33568 would not have guaranteed communication as TCP.
UDP on port 33568 provides an unreliable service and datagrams may arrive duplicated, out of order, or missing without notice. UDP on port 33568 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
18.117.9.138