TCP/UDP Port Finder
Search results for "root"
Port: 29292/TCP
29292/TCP - Known port assignments (4 records found)
- ServiceDetailsSource
- TMO Integration Service Communications Port, Used by Transaction Manager SaaS (HighJump Software) (Unofficial)WIKI
- UnassignedIANA
- backgate[trojan] BackGateSANS
- trojan[trojan] BackGate Kit. Remote Access / Rootkit / Steals passwords / Downloading trojan / FTP proxy / HTTP proxy / Telnet proxy / SOCKs proxy / Winsock proxy / FTP server. Works on Windows NT, together with MS Internet Information Server (IIS). Aliases: Backdoor.NTHack, NT Hack, Unicode RootkitSimovits
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
Port: 31337/TCP
31337/TCP - Known port assignments (50 records found)
- ServiceDetailsSource
- UnassignedIANA
- eliteSometimes interesting stuff can be found here hereSANS
- threat[threat] Back OrificeBekkoame
- threat[threat] Back Orifice 1.20 patchesBekkoame
- threat[threat] Back Orifice russianBekkoame
- threat[threat] Baron NightBekkoame
- threat[threat] BeeoneBekkoame
- threat[threat] BO clientBekkoame
- threat[threat] BO FacilBekkoame
- threat[threat] BO spyBekkoame
- threat[threat] BO2Bekkoame
- threat[threat] cron / crontabBekkoame
- threat[threat] EmcommanderBekkoame
- threat[threat] Freak2kBekkoame
- threat[threat] Freak88Bekkoame
- threat[threat] icmp_pipe.cBekkoame
- threat[threat] SockdminiBekkoame
- threat[threat] W32.HLLW.GoolBekkoame
- admworm[trojan] ADM wormSANS
- backfire[trojan] Back FireSANS
- backorifice1.20patches[trojan] Back Orifice 1.20 patchesSANS
- backorifice(lm)[trojan] Back Orifice (Lm)SANS
- backorificerussian[trojan] Back Orifice russianSANS
- baronnight[trojan] Baron NightSANS
- beeone[trojan] BeeoneSANS
- bindshell[trojan] bindshellSANS
- bo2[trojan] BO2SANS
- boclient[trojan] BO clientSANS
- bofacil[trojan] BO FacilSANS
- bospy[trojan] BO spySANS
- cron/crontab[trojan] cron / crontabSANS
- deepbo[trojan] Deep BOSANS
- freak2k[trojan] Freak2kSANS
- freak88[trojan] Freak88SANS
- gummo[trojan] GummoSANS
- icmp_pipe.c[trojan] icmp_pipe.cSANS
- linuxrootkitiv[trojan] Linux Rootkit IVSANS
- trojan[trojan] ADM worm. Worm / Rootkit / Backdoor. Works on Unix (Linux). Affects Linux RedHat 4.0 to 5.2. Aliases: ADM Inet w0rm, Linux.ADM.WormSimovits
- trojan[trojan] Back Fire. Remote Access. Works on Windows 95 and 98.Simovits
- trojan[trojan] Back Orifice (Lm). Remote Access. Works on Windows 95 and 98.Simovits
- trojan[trojan] Back Orifice russian. Remote Access. Works on Windows 95 and 98.Simovits
- trojan[trojan] BlitzNet. IRC trojan / DoS tool. Works on Unix (Linux).Simovits
- trojan[trojan] BO client. Works on Windows 95 and 98. BO client is using the ordinary BO server.Simovits
- trojan[trojan] BO Facil. Works on Windows 95 and 98. Aliases: Back Orifice FacilSimovits
- trojan[trojan] BO2. Remote Access. Works on Windows 95 and 98. Bo2 is a Back Orifice client application.Simovits
- trojan[trojan] Freak88. Distributed DoS tool. Works on Windows 95, 98 and NT. Aliases: Freak 2000Simovits
- trojan[trojan] Freak2k. Distributed DoS tool. Works on Windows 95, 98 and NT. Aliases: Freak 2000Simovits
- Back Orifice - remote administration tool (often Trojan horse) (Unofficial)WIKI
- trojan[trojan] NoBackO. Remote Access / Sniffer. Works on Windows.Simovits
- threat[threat] Back FireBekkoame
Port: 33567/TCP
33567/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: 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: 45092/TCP
45092/TCP - Known port assignments (2 records found)
- ServiceDetailsSource
- UnassignedIANA
- trojan[trojan] BackGate Kit. Remote Access / Rootkit / Steals passwords / Downloading trojan / FTP proxy / HTTP proxy / Telnet proxy / SOCKs proxy / Winsock proxy / FTP server. Works on Windows NT, together with MS Internet Information Server (IIS). Aliases: Backdoor.NTHack, NT Hack, Unicode RootkitSimovits
Port: 45559/TCP
45559/TCP - Known port assignments (2 records found)
Port: 47017/TCP
47017/TCP - Known port assignments (4 records found)
Port: 47017/UDP
47017/UDP - Known port assignments (2 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
About TCP/UDP ports
TCP port 29292 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 29292 in the same order in which they were sent. Guaranteed communication over TCP port 29292 is the main difference between TCP and UDP. UDP port 29292 would not have guaranteed communication as TCP.
UDP on port 29292 provides an unreliable service and datagrams may arrive duplicated, out of order, or missing without notice. UDP on port 29292 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 29292 in the same order in which they were sent. Guaranteed communication over TCP port 29292 is the main difference between TCP and UDP. UDP port 29292 would not have guaranteed communication as TCP.
UDP on port 29292 provides an unreliable service and datagrams may arrive duplicated, out of order, or missing without notice. UDP on port 29292 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.17.187.116