TCP/UDP Port Finder
Search results for "inst"
Port: 5191/TCP
5191/TCP - Known port assignments (2 records found)
Port: 5192/TCP
5192/TCP - Known port assignments (2 records found)
Port: 5193/TCP
5193/TCP - Known port assignments (2 records found)
Port: 5599/TCP
5599/TCP - Known port assignments (2 records found)
Port: 5599/UDP
5599/UDP - Known port assignments (1 record found)
- ServiceDetailsSource
- esinstallEnterprise Security Remote InstallIANA
Port: 5678/TCP
5678/TCP - Known port assignments (5 records found)
- ServiceDetailsSource
- rracRemote Replication Agent ConnectionIANA
- threat[threat] Port 5678 is the default port for the com.hp.util.rcat Java package (from Hewlett-Packard). This is a simple debugging package.Bekkoame
- threat[threat] A frequent port some picks at random.Bekkoame
- threat[threat] A port for remote execution using the crexd/srexd services.Bekkoame
- threat[threat] Port 5678 was originally specified for the PPTP protocol, but when the standard was ratified, port 1723 was chosen instead.Bekkoame
Port: 5678/UDP
5678/UDP - Known port assignments (7 records found)
- ServiceDetailsSource
- Mikrotik RouterOS Neighbor Discovery Protocol (MNDP) (Unofficial)WIKI
- rracRemote Replication Agent ConnectionIANA
- rracSNATMAP server. The SNATMAP service on port 5678 is used to determine the external Internet address of hosts so that connections between iChat users can properly function behind network address translation (NAT). The SNATMAP service simply communicates to clients the Internet address that connected to it. This service runs on an Apple server, but does not send personal information to Apple. When certain iChat AV features are used, this service will be contacted. Blocking this service may cause issues with iChat AV connections with hosts on networks that use NAT.Apple
- threat[threat] osagent communicationBekkoame
- threat[threat] A port for remote execution using the crexd/srexd services.Bekkoame
- threat[threat] A frequent port some picks at random.Bekkoame
- threat[threat] Port 5678 was originally specified for the PPTP protocol, but when the standard was ratified, port 1723 was chosen instead.Bekkoame
Port: 6005/TCP
6005/TCP - Known port assignments (3 records found)
Port: 6969/TCP
6969/TCP - Known port assignments (30 records found)
- ServiceDetailsSource
- acmsodaacmsodaIANA
- acmsoda (Unofficial)WIKI
- BitTorrent tracker (Unofficial)WIKI
- acmsoda-SANS
- threat[threat] DantonBekkoame
- threat[threat] FloodnetBekkoame
- threat[threat] GateCrasherBekkoame
- threat[threat] IRC 3Bekkoame
- threat[threat] KhaosBekkoame
- threat[threat] Net ControllerBekkoame
- threat[threat] PriorityBekkoame
- threat[threat] RategaBekkoame
- threat[threat] RobiBekkoame
- threat[threat] SpartaBekkoame
- 2000cracks[trojan] 2000 CracksSANS
- trojan[trojan] Vagr Nocker. Remote Access / Steals passwords. Works on Windows. Aliases: Backdoor.Latinus.14, VAGRSimovits
- danton[trojan] DantonSANS
- gatecrasher[trojan] GateCrasherSANS
- irc3[trojan] IRC 3SANS
- netcontroller[trojan] Net ControllerSANS
- priority[trojan] PrioritySANS
- trojan[trojan] 2000 Cracks. Works on Windows 95, 98 and NT.Simovits
- trojan[trojan] BlitzNet. IRC trojan / DoS tool. Works on Unix (Linux).Simovits
- trojan[trojan] Dark IRC. Remote Access / FTP server / IRC trojan / Distributed DoS tool. Works on Windows, together with an IRC software. Aliases: Backdoor.IRC.Dark, Backdoor.Darkirc, Palukka, Backdoor.Palukka, Backdoor.QZ, Win32.DarkIRC, DDoS.Win32.Palukka, Troj/PalukkaSimovits
- trojan[trojan] GateCrasher. Remote Access / Macro trojan. Works on Windows 95, 98 and NT. Aliases: Backdoor.GateCrasher, W97M.Port.TrojanSimovits
- trojan[trojan] Kid Terror. Remote Access / Steals passwords. Works on Windows 95 and 98. Based on GirlFriend's source code. Aliases: Backdoor.KidterrorSimovits
- trojan[trojan] Laphex. Remote Access / Downloading trojan. Works on Windows 95, 98, ME, NT, 2000 and XP. Aliases: Backdoor.Robi, Institon, Backdoor.Institon, Laphex, Backdoor.Laphex, Robi, Institution, Backdoor.InstitutionSimovits
- trojan[trojan] Net Controller. Remote Access / Keylogger / FTP server. Works on Windows 95, 98, ME, NT and XP. Both English and Portoguese versions exists. Aliases: NetcontrollerSimovits
- trojan[trojan] SpArTa. Anti-protection trojan / Remote Access. Works on Windows 95, 98, ME, NT, 2000 and XP. Aliases: Spartadoor, Backdoor.Spartadoor, Backdoor.Sparta, BackDoor.AFCSimovits
- threat[threat] AssasinBekkoame
Port: 7001/TCP
7001/TCP - Known port assignments (10 records found)
- ServiceDetailsSource
- afs3-callbackcallbacks to cache managersIANA
- Avira Server Management Console (Unofficial)WIKI
- Default for BEA WebLogic Server's HTTP server, though often changed during installation (Unofficial)WIKI
- threat[threat] Freak2kBekkoame
- threat[threat] Freak88Bekkoame
- freak2k[trojan] Freak2kSANS
- freak88[trojan] Freak88SANS
- netsnoopergold[trojan] NetSnooper GoldSANS
- 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
About TCP/UDP ports
TCP port 5191 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 5191 in the same order in which they were sent. Guaranteed communication over TCP port 5191 is the main difference between TCP and UDP. UDP port 5191 would not have guaranteed communication as TCP.
UDP on port 5191 provides an unreliable service and datagrams may arrive duplicated, out of order, or missing without notice. UDP on port 5191 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 5191 in the same order in which they were sent. Guaranteed communication over TCP port 5191 is the main difference between TCP and UDP. UDP port 5191 would not have guaranteed communication as TCP.
UDP on port 5191 provides an unreliable service and datagrams may arrive duplicated, out of order, or missing without notice. UDP on port 5191 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.14.149.222