TCP/UDP Port Finder
Search results for "put"
Port: 41/TCP
41/TCP - Known port assignments (8 records found)
- ServiceDetailsSource
- graphics-SANS
- graphicsGraphicsIANA
- threat[threat] RAT: Deep Throat Puts an FTP service at port 41 (TCP).Bekkoame
- deepthroat[trojan] DeepThroatSANS
- foreplay[trojan] ForeplaySANS
- trojan[trojan] Deep Throat. Remote Access / FTP server / Steals passwords. Works on Windows 95, 98 and NT. There is a Global Master Password backdoor in all the servers: v 2.0 - whothefuckdoyouthinkiamgoddamnit2v 2.1 - whothefuckdoyouthinkiamgoddamnit1v 3.* - whothefuckdoyouthinkiamgoddamnit3 Aliases: Win32.DeepThroat, DTV2, DTV3, BackDoor.J, Backdoor.DeepThroat, W95/Backdoor.TraySimovits
- trojan[trojan] Foreplay. Remote Access / FTP server. Works on Windows. Aliases: F0replay, WiNNUke eXtreame, Reduced ForeplaySimovits
- threat[threat] ForeplayBekkoame
Port: 999/TCP
999/TCP - Known port assignments (9 records found)
- ServiceDetailsSource
- ScimoreDB Database System (Unofficial)WIKI
- ipcserverMac OS X RPC-based services. Used by NetInfo, for example.Apple
- puprouter-IANA
- garcon-Bekkoame
- trojan[trojan] Deep Throat. Remote Access / FTP server / Steals passwords. Works on Windows 95, 98 and NT. There is a Global Master Password backdoor in all the servers: v 2.0 - whothefuckdoyouthinkiamgoddamnit2v 2.1 - whothefuckdoyouthinkiamgoddamnit1v 3.* - whothefuckdoyouthinkiamgoddamnit3 Aliases: Win32.DeepThroat, DTV2, DTV3, BackDoor.J, Backdoor.DeepThroat, W95/Backdoor.TraySimovits
- trojan[trojan] Foreplay. Remote Access / FTP server. Works on Windows. Aliases: F0replay, WiNNUke eXtreame, Reduced ForeplaySimovits
- threat[threat] WinSatanBekkoame
- threat[threat] ForeplayBekkoame
- threat[threat] RAT: Deep Throat Puts a keylogger at port 999 (TCP). This will record all of a user's keystrokes.Bekkoame
Port: 1234/UDP
1234/UDP - Known port assignments (3 records found)
- ServiceDetailsSource
- search-agentInfoseek Search AgentIANA
- VLC media player default port for UDP/RTP stream (Official)WIKI
- threat[threat] The bindshell.c program puts a backdoor root shell on this port by default. This assumes that you've already been compromised by some other exploit and that the hacker uses the default port.Bekkoame
Port: 1234/TCP
1234/TCP - Known port assignments (10 records found)
- ServiceDetailsSource
- search-agentInfoseek Search AgentIANA
- hotline-SANS
- threat[threat] Ultors TrojanBekkoame
- threat[threat] W32.BeagleBekkoame
- threat[threat] The bindshell.c program puts a backdoor root shell on this port by default. This assumes that you've already been compromised by some other exploit and that the hacker uses the default port.Bekkoame
- trojan[trojan] Ultors Trojan. Remote Access. Works on Windows 3.1, 95, 98, ME, NT, 2000 and XP. Uses Telnet as the client. Aliases: Ultors Telnet Trojan, Utlor, Backdoor.UltorSimovits
- subsevenjavaclient[trojan] SubSeven Java clientSANS
- ultorstrojan[trojan] Ultors TrojanSANS
- trojan[trojan] KiLo. Remote Access. Works on Windows.Simovits
- threat[threat] SubSeven Java clientBekkoame
Port: 7747/TCP
7747/TCP - Known port assignments (1 record found)
- ServiceDetailsSource
- prgpPut/Run/Get ProtocolIANA
Port: 7747/UDP
7747/UDP - Known port assignments (2 records found)
Port: 10752/UDP
10752/UDP - Known port assignments (2 records found)
- ServiceDetailsSource
- UnassignedIANA
- threat[threat] Backdoor. One of the many Linux mountd (port 635) exploits installs its backdoor at this port. Origin??? 10751 = 0x2a00, where 0x2a = 42 (proposed by Darren Reed) The bx.c IRC exploit puts a root shell backdoor listening at this port. The ADM named v3 attack puts a shell at this port.Bekkoame
Port: 10752/TCP
10752/TCP - Known port assignments (2 records found)
- ServiceDetailsSource
- UnassignedIANA
- threat[threat] Backdoor. One of the many Linux mountd (port 635) exploits installs its backdoor at this port. Origin??? 10751 = 0x2a00, where 0x2a = 42 (proposed by Darren Reed) The bx.c IRC exploit puts a root shell backdoor listening at this port. The ADM named v3 attack puts a shell at this port.Bekkoame
Port: 32773/TCP
32773/TCP - Known port assignments (3 records found)
- ServiceDetailsSource
- filenet-cmFileNET Component ManagerIANA
- sometimes-rpc9Sometimes an RPC port on my Solaris box (rquotad)SANS
- threat[threat] Sun puts RPC services in this region. Scans against this port might be looking for any RPC service, or maybe the rpc.ttdbserverd or rpc.sadmind service.Bekkoame
Port: 32773/UDP
32773/UDP - Known port assignments (3 records found)
- ServiceDetailsSource
- filenet-cmFileNET Component ManagerIANA
- sometimes-rpc10Sometimes an RPC port on my Solaris box (rquotad)SANS
- threat[threat] Sun puts RPC services in this region. Scans against this port might be looking for any RPC service, or maybe the rpc.ttdbserverd or rpc.sadmind service.Bekkoame
About TCP/UDP ports
TCP port 41 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 41 in the same order in which they were sent. Guaranteed communication over TCP port 41 is the main difference between TCP and UDP. UDP port 41 would not have guaranteed communication as TCP.
UDP on port 41 provides an unreliable service and datagrams may arrive duplicated, out of order, or missing without notice. UDP on port 41 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 41 in the same order in which they were sent. Guaranteed communication over TCP port 41 is the main difference between TCP and UDP. UDP port 41 would not have guaranteed communication as TCP.
UDP on port 41 provides an unreliable service and datagrams may arrive duplicated, out of order, or missing without notice. UDP on port 41 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.21.231.245