TCP/UDP Port Finder
Search results for "ma"
Port: 31791/UDP
31791/UDP - Known port assignments (4 records found)
- ServiceDetailsSource
- UnassignedIANA
- hack´a´tack[trojan] Hack´a´TackSANS
- hackatack[trojan] Hack¦a¦TackSANS
- trojan[trojan] Hack'a'Tack. Remote Access / Keylogger / Steals passwords / IP Scanner. Works on Windows 95 and 98. With somebugfixes it will work on NT as well. Now there exists two beafed up versions called v.SE and v.TE with many bugfixes included. Version 2000 is shareware! Aliases: HAT, HackTack, Backdoor.HackTack, Backdoor-Q, Fake Server Trojan, Hack Server TrojanSimovits
Port: 31792/TCP
31792/TCP - Known port assignments (5 records found)
- ServiceDetailsSource
- UnassignedIANA
- threat[threat] Hack-a-TackBekkoame
- hackatack[trojan] Hack¦a¦TackSANS
- hack´a´tack[trojan] Hack´a´TackSANS
- trojan[trojan] Hack'a'Tack. Remote Access / Keylogger / Steals passwords / IP Scanner. Works on Windows 95 and 98. With somebugfixes it will work on NT as well. Now there exists two beafed up versions called v.SE and v.TE with many bugfixes included. Version 2000 is shareware! Aliases: HAT, HackTack, Backdoor.HackTack, Backdoor-Q, Fake Server Trojan, Hack Server TrojanSimovits
Port: 32483/TCP
32483/TCP - Known port assignments (1 record found)
- ServiceDetailsSource
- apm-linkAccess Point Manager LinkIANA
Port: 32483/UDP
32483/UDP - Known port assignments (1 record found)
- ServiceDetailsSource
- apm-linkAccess Point Manager LinkIANA
Port: 32771/TCP
32771/TCP - Known port assignments (3 records found)
- ServiceDetailsSource
- filenet-rmiFileNET RMIIANA
- sometimes-rpc5Sometimes an RPC port on my Solaris box (rusersd)SANS
- threat[threat] Ghost Portmapper. Some SunOS machines listen at this port for portmapper. Since firewalls frequently don't filter at high ports, it can allow the attacker access to portmapper even when port 111 is blocked.Bekkoame
Port: 32771/UDP
32771/UDP - Known port assignments (4 records found)
- ServiceDetailsSource
- filenet-rmiFileNet RMIIANA
- filenet-rmiFileNET RMIBekkoame
- sometimes-rpc6Sometimes an RPC port on my Solaris box (rusersd)SANS
- threat[threat] Ghost Portmapper. Some SunOS machines listen at this port for portmapper. Since firewalls frequently don't filter at high ports, it can allow the attacker access to portmapper even when port 111 is blocked.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
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: 32776/TCP
32776/TCP - Known port assignments (3 records found)
Port: 32776/UDP
32776/UDP - Known port assignments (3 records found)
About TCP/UDP ports
TCP port 31791 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 31791 in the same order in which they were sent. Guaranteed communication over TCP port 31791 is the main difference between TCP and UDP. UDP port 31791 would not have guaranteed communication as TCP.
UDP on port 31791 provides an unreliable service and datagrams may arrive duplicated, out of order, or missing without notice. UDP on port 31791 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 31791 in the same order in which they were sent. Guaranteed communication over TCP port 31791 is the main difference between TCP and UDP. UDP port 31791 would not have guaranteed communication as TCP.
UDP on port 31791 provides an unreliable service and datagrams may arrive duplicated, out of order, or missing without notice. UDP on port 31791 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.140.238.141