TCP/UDP Port Finder
Search results for "par"
Port: 1864/TCP
1864/TCP - Known port assignments (1 record found)
- ServiceDetailsSource
- paradym-31portParadym 31 PortIANA
Port: 1864/UDP
1864/UDP - Known port assignments (1 record found)
- ServiceDetailsSource
- paradym-31portParadym 31 PortIANA
Port: 2766/TCP
2766/TCP - Known port assignments (6 records found)
- ServiceDetailsSource
- compaq-scpCompaq SCPIANA
- KnowShowGo P2P (Official)WIKI
- listenSystem V listener portSANS
- nlpsSolaris Print ServicesSANS
- threat[threat] used by Solaris listen/nlps_server. It was part of System V R3 and Solaris. In much the same way that scanning for tcpmux will fingerprint SGI machines, scanning for this port will fingerprint SVR3 (Solaris 2.0) machines.Bekkoame
- threat[threat] W32.HLLW.DeadhatBekkoame
Port: 3089/TCP
3089/TCP - Known port assignments (1 record found)
- ServiceDetailsSource
- ptk-alinkParaTek Agent LinkingIANA
Port: 3089/UDP
3089/UDP - Known port assignments (1 record found)
- ServiceDetailsSource
- ptk-alinkParaTek Agent LinkingIANA
Port: 3129/TCP
3129/TCP - Known port assignments (6 records found)
- ServiceDetailsSource
- netport-idNetPort Discovery PortIANA
- threat[threat] Masters ParadiseBekkoame
- threat[threat] Novarg(Mydoom)Bekkoame
- threat[threat] W32.HLLW.DeadhatBekkoame
- mastersparadise[trojan] Masters ParadiseSANS
- trojan[trojan] Masters Paradise. Remote Access. Works on Windows 95, 98 and NT. Aliases: Masters Paradise 98, Paradise Agent, Paradise trojan, Backdoor.MasterPSimovits
Port: 3366/TCP
3366/TCP - Known port assignments (1 record found)
- ServiceDetailsSource
- creativepartnrCreative PartnerIANA
Port: 3366/UDP
3366/UDP - Known port assignments (1 record found)
- ServiceDetailsSource
- creativepartnrCreative PartnerIANA
Port: 4025/TCP
4025/TCP - Known port assignments (1 record found)
- ServiceDetailsSource
- partimagePartition Image PortIANA
Port: 4025/UDP
4025/UDP - Known port assignments (1 record found)
- ServiceDetailsSource
- partimagePartition Image PortIANA
About TCP/UDP ports
TCP port 1864 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 1864 in the same order in which they were sent. Guaranteed communication over TCP port 1864 is the main difference between TCP and UDP. UDP port 1864 would not have guaranteed communication as TCP.
UDP on port 1864 provides an unreliable service and datagrams may arrive duplicated, out of order, or missing without notice. UDP on port 1864 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 1864 in the same order in which they were sent. Guaranteed communication over TCP port 1864 is the main difference between TCP and UDP. UDP port 1864 would not have guaranteed communication as TCP.
UDP on port 1864 provides an unreliable service and datagrams may arrive duplicated, out of order, or missing without notice. UDP on port 1864 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.227.161.132