IP:   Time: -
See more sites from My-Addr
 TCP/UDP tools and library
About TCP/UDP tools
Find port number
Find port number by word
Check all open ports
IP range port scanner
 Ranges of ports in library
TCP ports list range 0-1024
TCP ports list range 1024-7000
TCP ports list range 7000-20000
TCP ports list range 20000-49151
UDP ports list range 0-1024
UDP ports list range 1024-7000
UDP ports list range 7000-20000
UDP ports list range 20000-49151

tcp port 10000,udp port 10000,udp tcp 10000 description,biggest ports library database

On this page you can find tools for search TCP Port Numbers and UDP Port Numbers.
Current service contain the biggest tcp udp port list. Port search going through 4 library (database),
total number of records are about 22000 (in 3 times more that in other service).
  • IANA port numbers assignments library (database) - The Internet Assigned Numbers Authority (IANA) is responsible for maintaining the official assignments of port numbers for specific uses.
  • WIKI port numbers assignments library (database) - Good known wikipedia ports library
  • Gasmy library, Beta Library - good known manualy created port databases.
The closest known TCP ports before 10000 port :9999 ([trojan] The Prayer), 9999 (Lantronix UDS-10/UDS100[43] RS-485 to Ethernet Converter TELNET control), 9999 (Lantronix UDS-10/UDS100 RS-485 to Ethernet Converter Telnet control), 9999 (distinct), 9999 (distinct),
The closest known UDP ports before 10000 port :9999 (QuickTime Streaming Server), 9999 (distinct), 9999 (distinct), 9998 (QuickTime Streaming Server), 9998 (Distinct32),
The closest known TCP ports before 10000 port :10001 (Lantronix UDS-10/UDS100 RS-485 to Ethernet Converter default), 10001 (Lantronix UDS-10/UDS100[44] RS-485 to Ethernet Converter default), 10001 (SCP Configuration), 10001 (SCP Configuration Port), 10002 (EMC-Documentum Content Server Product),
The closest known UDP ports before 10000 port :10001 (SCP Configuration), 10001 (SCP Configuration Port), 10001 (Ubiquiti UniFi access points broadcast to (UDP) to locate the controller(s)), 10002 (EMC-Documentum Content Server Product), 10002 (EMC-Documentum Content Server Product),
In computer networking, the protocols of the Transport Layer of the Internet Protocol Suite, most notably the Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP),
use a numerical identifier for the data structures of the endpoints for host-to-host communications.
Such an endpoint is known as a port and the identifier is the port number.

Network Data Management Protocol
Network Data Management Protocol
Used on VoIP networks for receiving and transmitting voice telephony traffic which includes Google Voice via the OBiTalk ATA devices as well as on the MagicJack and Vonage ATA network device
ndmp Network Data Management Protocol
ndmp Network Data Management Protocol
TCP no data
UDP no data

The Transmission Control Protocol (TCP) is one of the core protocols of the Internet Protocol Suite. TCP is so central that the entire suite is often referred to as "TCP/IP." Whereas IP handles lower-level transmissions from computer to computer as a message makes its way across the Internet, TCP operates at a higher level, concerned only with the two end systems, for example a Web browser and a Web server. In particular, TCP provides reliable, ordered delivery of a stream of bytes from one program on one computer to another program on another computer. Besides the Web, other common applications of TCP include e-mail and file transfer. Among its management tasks, TCP controls message size, the rate at which messages are exchanged, and network traffic congestion.
The User Datagram Protocol (UDP) is one of the core members of the Internet Protocol Suite, the set of network protocols used for the Internet. With UDP, computer applications can send messages, sometimes known as datagrams, to other hosts on an Internet Protocol (IP) network without requiring prior communications to set up special transmission channels or data paths. UDP is sometimes called the Universal Datagram Protocol. The protocol was designed by David P. Reed in 1980 and formally defined in RFC 768.