TCP/UDP Port Finder

Enter port number (e.g. 21), service (e.g. ssh, ftp) or threat (e.g. nimda)
Database updated - March 30, 2016

Search results for "w32"

<< < 5 6 7 8 9 10 11 12 13 > >>
Port: 2281/TCP
2281/TCP - Known port assignments (3 records found)
  • Service
    Details
    Source
  • lnvconsole
    LNVCONSOLE
    IANA
  • threat
    [threat] W32.HLLW.Nautic
    Bekkoame
  • trojan
    [trojan] Nautical. Worm / Network trojan. Aliases: W32.HLLW.Nautic, Backdoor.Nautic, Calinaut, Nautic
    Simovits
Port: 2281/UDP
2281/UDP - Known port assignments (2 records found)
  • Service
    Details
    Source
  • lnvconsole
    LNVCONSOLE
    IANA
  • threat
    [threat] W32.HLLW.Nautic
    Bekkoame
Port: 2283/TCP
2283/TCP - Known port assignments (7 records found)
  • Service
    Details
    Source
  • lnvstatus
    LNVSTATUS
    IANA
  • threat
    [threat] Hvl RAT
    Bekkoame
  • threat
    [threat] Nibu
    Bekkoame
  • threat
    [threat] W32.Dumaru
    Bekkoame
  • hvlrat5
    [trojan] HVL Rat5
    SANS
  • hvlrat
    [trojan] Hvl RAT
    SANS
  • trojan
    [trojan] Hvl RAT. Remote Access. Works on Windows 95,98 and NT. Aliases: Backdoor.HVL-Rat
    Simovits
Port: 2442/TCP
2442/TCP - Known port assignments (3 records found)
  • Service
    Details
    Source
  • netangel
    Netangel
    IANA
  • threat
    [threat] W32.Kelvir
    Bekkoame
  • threat
    [threat] W32.Spybot
    Bekkoame
Port: 2535/TCP
2535/TCP - Known port assignments (3 records found)
  • Service
    Details
    Source
  • madcap
    MADCAP
    IANA
  •  
    MADCAP (Unofficial)
    WIKI
  • threat
    [threat] W32.Beagle
    Bekkoame
Port: 2535/UDP
2535/UDP - Known port assignments (2 records found)
  • Service
    Details
    Source
  • madcap
    MADCAP
    IANA
  • threat
    [threat] W32.Beagle
    Bekkoame
Port: 2556/TCP
2556/TCP - Known port assignments (3 records found)
  • Service
    Details
    Source
  • nicetec-nmsvc
    nicetec-nmsvc
    IANA
  • bagle-backdoor
    Bagle Virus Backdoor
    SANS
  • threat
    [threat] W32.Beagle
    Bekkoame
Port: 2556/UDP
2556/UDP - Known port assignments (2 records found)
  • Service
    Details
    Source
  • nicetec-nmsvc
    nicetec-nmsvc
    IANA
  • threat
    [threat] W32.Beagle
    Bekkoame
Port: 2745/TCP
2745/TCP - Known port assignments (4 records found)
  • Service
    Details
    Source
  • urbisnet
    URBISNET
    IANA
  •  
    KnowShowGo P2P (Official)
    WIKI
  • bagle.c
    Bagle Virus Backdoor
    SANS
  • threat
    [threat] W32.Beagle
    Bekkoame
Port: 2766/TCP
2766/TCP - Known port assignments (6 records found)
  • Service
    Details
    Source
  • compaq-scp
    Compaq SCP
    IANA
  •  
    KnowShowGo P2P (Official)
    WIKI
  • listen
    System V listener port
    SANS
  • nlps
    Solaris Print Services
    SANS
  • 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.Deadhat
    Bekkoame
<< < 5 6 7 8 9 10 11 12 13 > >>

About TCP/UDP ports

TCP port 2281 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 2281 in the same order in which they were sent. Guaranteed communication over TCP port 2281 is the main difference between TCP and UDP. UDP port 2281 would not have guaranteed communication as TCP.
UDP on port 2281 provides an unreliable service and datagrams may arrive duplicated, out of order, or missing without notice. UDP on port 2281 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
Your are from United States18.208.197.243