List of TCP and UDP Port Numbers

Summary:

Based on the provided information, here is a summary of the main points related to TCP and UDP port numbers retrieved from Wikipedia's page: 1. **Information Source**: The content in question appears to be an extract or excerpt from Wikipedia's "List of TCP and UDP port numbers" article. This list includes various port numbers categorized by their usage, such as well-known ports (0–1023), registered ports (1024–49151), and dynamic/private ports (49152–65535). 2. **Potential Issues**: The page acknowledges that the information might be outdated since it was last updated in 2000. Additionally, there are unsourced statements within the article which may compromise its reliability. 3. **Improvement Suggestions**: According to the content: - There are external links on the page that need cleanup to enhance Wikipedia's quality standards. - The navigation tools for users like creating accounts, logging in, editing pages, and searching could be improved. 4. **Multilingual Content**: The article is available in various language versions, allowing for translation and contributions from editors around the world. This feature promotes inclusivity and diversity in the content creation process. 5. **Port Numbers Categorized by Usage**: The list provided includes: - Well-known ports (0–1023): These are registered with IANA and have standardized services associated with them. - Registered ports (1024–49151): These are also assigned by IANA but do not necessarily have a specific standard service. - Dynamic/private ports (49152–65535): These are used for private networks and can be dynamically allocated as needed. In summary, the Wikipedia article serves as a resource for understanding TCP and UDP port numbers, their categorization, and their usage in networking protocols. However, it acknowledges certain limitations including outdated information and unsourced statements. The page also provides an opportunity for multilingual content and user contributions to improve its quality and relevance over time.

Details:

The article on Wikipedia provides information about port numbers used by protocols in the Transport Layer of the Internet Protocol Suite, which is responsible for establishing host-to-host communications. It mentions that initially, these port numbers were used by NCP and only two ports were needed due to half duplex transmission. As TCP (Transmission Control Protocol) and UDP (User Datagram Protocol) became adopted, only one port was required per communication channel, leading to the dropping of even numbered ports. The article explains that well-known ports are those with numbers from 0 to 1023, used by system processes providing widely used network services. On Unix-like operating systems, a superuser privilege is needed for a process to bind a network socket to a well-known port number. The official usage of these ports is registered with IANA (Internet Assigned Numbers Authority), though unofficial uses also occur in practice. The table provides an overview of various internet protocols, their status (official or unofficial), and the type of service they offer. Here's a summary based on the provided data:

• **0**: UDP, Reserved - No official use specified.

• **1**: TCP, UDP, TCP Port Service Multiplexer (TCPMUX) - Official for multiplexing multiple network services over a single connection.

• **2**: TCP, UDP, CompressNET - Management Utility and Compression Process are both official uses of this protocol.

• **3**: TCP, UDP, CompressNET - Official for compression processes.

• **4**: TCP, UDP, Unassigned - No specific use mentioned.

• **5**: TCP, UDP, Remote Job Entry (systat service) - Official for remote job entry services.

• **7**: TCP, UDP, Echo Protocol - Official for the echo protocol used in debugging and testing network connections.

• **8**: TCP, UDP, Unassigned - No specific use mentioned.

• **9**: TCP, UDP, Discard Protocol - Official for discarding received data without any response.

• **9**: UDP, Wake-on-LAN - Unofficial use for waking up computers via LAN.

• **10**: TCP, UDP, Unassigned - No specific use mentioned.

• **11**: TCP, UDP, Active Users (systat service) - Official for monitoring active users on a network.

• **12**: TCP, UDP, Unassigned - No specific use mentioned.

• **13**: TCP, UDP, Daytime Protocol (RFC 867) - Official for providing the current date and time over the network.

• **14**: TCP, UDP, Unassigned - No specific use mentioned.

• **15**: TCP, UDP, Previously netstat service - Unofficial use related to network status querying.

• **16**: TCP, UDP, Unassigned - No specific use mentioned.

• **17**: TCP, UDP, Quote of the Day - Official for displaying a daily quote over the network.

• **18**: TCP, UDP, Message Send Protocol - Official for sending messages across networks.

• **19**: TCP, UDP, Character Generator Protocol (CHARGEN) - Official for generating character streams to test line modes and echoing received characters back.

• **20**: TCP, UDP, FTP data transfer - Official use related to file transfer protocol.

• **21**: TCP, FTP control (command) - Official for controlling the FTP session via commands.

• **22**: TCP, UDP, Secure Shell (SSH) - Official for secure logins and various other network services including file transfers and port forwarding.

• **23**: TCP, UDP, Telnet protocol—unencrypted text communications - Official for unencrypted remote terminal connections.

• **24**: TCP, UDP, Priv-mail: any private mail system - Official use related to private mail transfer.

• **25**: TCP, Simple Mail Transfer Protocol (SMTP)—used for routing email between mail servers.

• **26**: TCP, UDP, Unassigned - No specific use mentioned.

• **27**: TCP, UDP, NSW User System FE - Official use related to a user system frontend.

• **29**: TCP, UDP, MSG ICP - Official use related to inter-network communication protocol.

• **33**: TCP, UDP, Display Support Protocol - Official for supporting graphical display applications.

• **35**: TCP, UDP, Any private printer server protocol - Official for handling various types of printer servers.

• **37**: TCP, UDP, TIME protocol - Official for synchronizing timekeeping across networks.

• **39**: TCP, UDP, Resource Location Protocol (RLP) - Used to determine the location of higher level services from hosts on a network.

• **40**: TCP, UDP, Unassigned - No specific use mentioned.

• **42**: TCP, UDP, ARPA Host Name Server Protocol and Windows Internet Name Service - Official for name service resolution.

• **43**: TCP, WHOIS protocol - Official for querying databases about registered users of domains on the internet.

• **47**: TCP, UDP, NI FTP - Official use related to network information services in FTP.

• **49**: TCP, UDP, TACACS Login Host protocol - Official for authentication and authorization services.

• **50**: TCP, UDP, Remote Mail Checking Protocol - Official for checking remote mail servers.

• **51**: TCP, UDP, IMP Logical Address Maintenance - Official use related to maintaining logical addresses in the IMP network.

• **52**: TCP, UDP - No specific use mentioned.

This table outlines a range of protocols used across various networking scenarios, from basic data transfer and name service resolution to more specialized services like secure communications and printer management. The provided text lists various network protocols and their associated TCP or UDP ports, along with some additional details about each protocol. Here is a summary of the information presented:

• **XNS (Xerox Network Systems) Time Protocol** - Official; uses port 53 for both TCP and UDP.

• **XNS (Xerox Network Systems) Clearinghouse** - Official; uses port 55 for both TCP and UDP.

• **ISI Graphics Language (ISI-GL)** - Official; uses port 56 for both TCP and UDP.

• **XNS (Xerox Network Systems) Authentication** - Official; uses port 56 for both TCP and UDP.

• **Route Access Protocol (RAP)** - Unofficial; uses port 57 for TCP.

• **Mail Transfer Protocol (SMTP) RFC 780** - Official; uses port 25 for TCP, but the default is often changed to avoid conflicts.

• **Bootstrap Protocol (BOOTP) Server and Client** - Official; uses ports 68 and 69 for UDP.

• **Trivial File Transfer Protocol (TFTP)** - Official; uses port 70 for both TCP and UDP.

• **Gopher protocol** - Official; uses port 71 for TCP.

• **NETRJS protocol** - Official; uses ports 72 to 74 for TCP.

• **Finger protocol** - Official; uses port 79 for TCP.

• **Hypertext Transfer Protocol (HTTP)** - Official; uses port 80 for both TCP and UDP, but often re-mapped to avoid conflicts.

• **Torpark (Onion routing)** - Unofficial; uses ports 81 and 82 for TCP and UDP respectively.

• **Kerberos** - Official; uses ports 88, 90, and 90 for both TCP and UDP.

• **dnsix (DoD Network Security for Information Exchange) Securit Attribute Token Map** - Official; uses port 90 for both TCP and UDP.

• **PointCast (dotcom)** - Unofficial; uses port 99 for TCP.

• **CyberGate RAT protocol** - Unofficial; uses port 100 for TCP.

• **NIC host name** - Official; uses port 101 for both TCP and UDP.

• **ISO-TSAP (Transport Service Access Point) Class 0 protocol** - Official; used by Digital Equipment Corporation DECnet over TCP/IP, also on ports 102 for TCP and UDP.

• **ACR/NEMA Digital Imaging and Communications in Medicine (DICOM)** - Official; uses port 104 for both TCP and UDP.

• **CCSO Nameserver Protocol (Qi/Ph)** - Official; uses port 105 for both TCP and UDP.

• **Remote TELNET Service protocol** - Official; uses port 107 for both TCP and UDP.

• **SNA Gateway Access Server** - Official; uses port 108 for both TCP and UDP.

• **Post Office Protocol (POP2)** - Official; uses port 109 for TCP.

• **Post Office Protocol (POP3)** - Official; uses port 110 for TCP.

These protocols are used in various networking applications, from time synchronization to file transfer and communication services over the internet. This text lists various network protocols and their corresponding port numbers. Here's a summary of the content:

• **TCP/UDP Ports 111, 113, 115, 117, 118, 123, 126, 135, 137, 138, 139, 143, 152, 153, 156, 158, 161, 162, 170, 175, 177, 179, 194, 199, 201, 209** are associated with different network protocols and services such as:

• **TCP/UDP 111**: TCP (ONC RPC), UDP (Sun RPC) - used for remote procedure call.

• **TCP 113**: Ident (Authentication Service/Identification Protocol) - Used by IRC servers to identify users.

• **TCP 115**: SFTP (Simple File Transfer Protocol) - A network protocol providing file transfer over secure channels.

• **TCP 117**: UUCP (Unix-to-Unix Copy) Path Service - Enables communication between Unix systems via the network.

• **TCP/UDP 118**: SQL (Structured Query Language) Services - Supports database management and querying through the network.

• **UDP 123**: NTP (Network Time Protocol) - Used for time synchronization across networks.

• **TCP/UDP 126**: Formerly Unisys Unitary Login, now NXEdit, used by Unisys Programmer's Workbench for Clearpath MCP software development.

• **TCP/UDP 135**: DCE endpoint resolution (DCOM) and Microsoft EPMAP (End Point Mapper), used for remote service management including DHCP, DNS, and WINS servers.

• **TCP/UDP 137-139**: NetBIOS services - NetBIOS Name Service, NetBIOS Datagram Service, and NetBIOS Session Service providing inter-application communication over a network.

• **TCP 143**: IMAP (Internet Message Access Protocol) - Manages email messages on servers.

• **TCP/UDP 152, 153**: BGP (Border Gateway Protocol), SGMP (Simple Gateway Monitoring Protocol).

• **TCP/UDP 156, 158**: DMSP (Distributed Mail Service Protocol), SQL Service.

• **UDP 161**: SNMP (Simple Network Management Protocol) for network management.

• **TCP/UDP 162**: SNMPTRAP (SNMP Trap) - Extends the functionality of SNMP to report events and changes in network status.

• **TCP 170**: Print-srv, Network PostScript - Supports network printing using PostScript language.

• **TCP 175**: VMNET (IBM z/VM, z/OS & z/VSE - Network Job Entry(NJE)).

• **TCP/UDP 177**: XDMCP (X Display Manager Control Protocol) for managing graphical user interfaces over a network.

• **TCP 179**: BGP (Border Gateway Protocol).

• **TCP/UDP 194, 199**: IRC (Internet Relay Chat), SNMP Unix Multiplexer (SMUX).

• **TCP/UDP 201**: AppleTalk Routing Maintenance.

• **TCP/UDP 209**: QMail (Quick Mail Transfer Protocol) - A protocol used for email transmission over the network.

These ports and protocols facilitate various networking functions including file transfer, remote procedure calls, time synchronization, network management, and communication between applications on different systems. This text provides a list of various protocols and their corresponding port numbers, along with the transport layer protocol (TCP or UDP) used to transmit them. The items are categorized by their specific function or protocol type, such as network management, messaging, directory access, or power supply. Some examples include Internetwork Packet Exchange (IPX), Precision Time Protocol for event messages and general messages, Lightweight Directory Access Protocol (LDAP), Microsoft-DS Active Directory, and SecureCast1 for communication with NAI's SecureCast servers. The list also includes official protocol assignments marked by their status as 'Official'. This summary lists various network protocols and their corresponding port numbers. The list includes both official (standard ports) and unofficial (non-standard ports) designations for different services and applications. Some examples are TCP, UDP, Modbus protocol, Rexec, Shell, Syslog, UUCP, RPC, AFP over TCP, Real Time Streaming Protocol, etc. Each entry provides the name of the service or protocol, its official/unofficial status, and the port numbers it uses (either in TCP or UDP). The provided text lists a variety of TCP and UDP ports, along with their protocols and some descriptions. Here's the summary:

• **7**: TCP - e-mail message submission via SMTP (Simple Mail Transfer Protocol).

• **591**: TCP - FileMaker 6.0 and later Web Sharing using HTTP Alternate protocol.

• **593**: TCP, UDP - HTTP RPC Ep Map and Remote procedure call over Hypertext Transfer Protocol often used by Distributed Component Object Model services and Microsoft Exchange Server.

• **604**: TCP - TUNNEL profile for BEEP peers to form an application layer tunnel.

• **623**: TCP, UDP - ASF Remote Management and Control Protocol (ASF-RMCP).

• **631**: TCP, UDP - Internet Printing Protocol (IPP) and Common Unix Printing System (CUPS).

• **635**: TCP, UDP - RLZ DBase.

• **636**: TCP, UDP - Lightweight Directory Access Protocol over TLS/SSL (LDAPS).

• **639**: TCP, UDP - MSDP, Multicast Source Discovery Protocol.

• **641**: TCP, UDP - SupportSoft Nexus Remote Command for remote control traffic.

• **646**: TCP, UDP - LDP, Label Distribution Protocol used in MPLS networks.

• **647**: TCP - DHCP Failover protocol.

• **648**: TCP, UDP - RRP (Registry Registrar Protocol).

• **651**: TCP, UDP - IEEE-MMS.

• **653**: TCP, UDP - Media Management System (MMS) Media Management Protocol (MMP).

• **657**: TCP - IBM RMC (Remote monitoring and Control) protocol used by System p5 AIX Integrated Virtualization Manager (IVM) and Hardware Management Console to connect managed logical partitions (LPAR).

• **660**: TCP - Mac OS X Server administration.

• **666**: TCP, UDP - Doom (first online first-person shooter), airserv-ng (used by aircrack-ng for remote controlling wireless devices).

• **674**: TCP - ACAP (Application Configuration Access Protocol).

• **688**: TCP, UDP - REALM-RUSD (ApplianceWare Server Appliance Management Protocol).

• **691**: TCP - MS Exchange Routing.

This text lists various network protocols and their communication methods, categorized by the protocol type (TCP or UDP), along with a brief description of each. The list includes:

• TCP/UDP: Linux-HA High Availability Heartbeat for cluster management.

• TCP: IEEE-MMS-SSL (IEEE Media Management System over SSL) for secure media management.

• UDP: OLSR (Optimized Link State Routing) for routing in mobile ad hoc networks.

• TCP: EPP (Extensible Provisioning Protocol), used for communication between domain name registries and registrars, as per RFC 5734.

• TCP: LMP (Link Management Protocol) for managing traffic engineering links between nodes, supporting the Internet standard.

• TCP: IRIS over BEEP for providing an Internet Registry Information Service.

• TCP: Secure Internet Live Conferencing (SILC).

• TCP: Cisco Tag Distribution Protocol, which is being replaced by the MPLS Label Distribution Protocol.

• TCP: Topology Broadcast based on Reverse-Path Forwarding routing protocol (TBRPF), standardized in RFC 3684.

• TCP/UDP: Kerberos administration and authentication protocols including kerberos-iv, Kerberos master, kpasswd server, and slave propagation.

• UDP: mdbe daemon for managing network devices.

• Microsoft Net.TCP Port Sharing Service.

• Certificate Management Protocol.

• Adobe Flash support (unconfirmed if official).

• DHCP Failover protocol.

• Group Domain Of Interpretation (GDOI) protocol.

• iSCSI standard defined in RFC 3720.

• OWAMP control protocol as per RFC 4656.

The list provides an overview of various networking protocols used across different applications, some official and some unofficial, with TCP and UDP as the primary modes of data transfer. This summary lists various network protocols and their corresponding port numbers in the TCP and UDP protocol families. Some examples include TWAMP control (RFC 5357) on port 862, rsync file synchronization protocol on port 873, CDDBP for CD DataBase on port 888, Brocade SMI-S RPC over TCP on port 897 and UDP on port 898, Samba Web Administration Tool (SWAT) on port 901, VMware Virtual Infrastructure Client on port 902, VMRC Remote Console on port 903, NAS Netnews Administration System on port 991, TELNET protocol over TLS/SSL on port 992, and POP3S on port 995. The list also includes other services such as Microsoft Windows SBS SharePoint (port 987), FTPS Protocol over TLS/SSL (ports 989, 990), and Opsware agent (cogbot) on port 1002. This document provides an incomplete list of notable ports along with their TCP and UDP statuses. The range of port numbers from 1024 to 49151 are registered ports assigned by IANA for specific services upon application. On most systems, these registered ports can be used by ordinary users. The provided table includes details about various ports such as their assigned protocol (TCP or UDP), the service they support, and their status (official or unofficial). Some examples include NFS (port 1025), DCOM (port 1026), Kerberos KPOP (port 1109), Tripwire (port 1169), Indigo Home Automation (port 1176), AcceleNet Intelligent Transfer Protocol (port 1182), OpenVPN (port 1194), and the cajo project (port 1198). It is recommended to refer to the Service Name and Transport Protocol Port Number Registry of IANA for a complete list of assigned ports. This text lists various port numbers and protocols used by different software applications. Here's a summary of each entry: 1. **Steam Friends Applet** - Uses UDP, unofficial (port 1200). 2. **Kazaa** - Uses TCP, unofficial (port 1214). 3. **Uvora Online** - Uses TCP, unofficial (port 1217). 4. **QuickTime Streaming Server** - Administration uses TCP and UDP, official (port 1223). 5. **TGP (TrulyGlobal Protocol)** - Official (port 1232), protocol includes both TCP and UDP. 6. **Nexum, Inc. First-Defense Remote Systems Monitoring Service** - Uses UDP, official (port 1234). 7. **VLC media player for UDP/RTP stream** - Unofficial default port (port 1236). 8. **Symantec BindView Control UNIX Management Server Connections** - Default ports are TCP and UDP, unofficial (ports 1241). 9. **Nessus Security Scanner** - Official but uses both TCP and UDP (ports 1270-1271). 10. **Microsoft System Center Operations Manager (SCOM) Agent** - Uses both TCP and UDP, official (port 1293). 11. **IPSec (Internet Protocol Security)** - Official, uses TCP (port 1301). 12. **Palmer Performance OBDNet** - Unofficial, uses TCP (port 1309). 13. **Altera Quartus jtagd** - Unofficial, uses TCP (port 1311). 14. **Dell OpenManage HTTPS** - Official, uses TCP (port 1313). 15. **Xbiim (Canvii server)** - Unofficial, uses TCP (port 1314). 16. **Festival Speech Synthesis System** - Unofficial, uses TCP (port 1319). 17. **AMX ICSP Management Server Connections** - Official but different ports for TCP and UDP (ports 1319-1320). 18. **Men and Mice DNS** - Official, uses both TCP and TCP (ports 1337). 19. **WASTE Encrypted File Sharing Program** - Unofficial, uses both TCP and UDP (ports 1341). 20. **Qubes Manufacturing Execution System** - Official but unspecified protocol usage (port 1344). 21. **Internet Content Adaptation Protocol** - Official, uses TCP (port 1352). 22. **IBM Lotus Notes / Domino RPC Protocol** - Official, uses both TCP and UDP (ports 1387-1388). These entries represent a range of applications from official corporate systems to unofficial or unsupported software components used in specific contexts. This text lists various ports used by different software and services, including Microsoft SQL Server (official port 1434 and unofficial ports 1521), Solarwinds Kiwi Log Server (port 1494), Citrix XenApp (independent computing architecture thin client protocol, port 1500), NetGuard GuardianPro firewall for NT4 (remote management 1501/authentication client 1503), Windows Live Messenger (whiteboard and application sharing, ports 1512/UDP), Microsoft Windows Internet Name Service (WINS, ports 1513/TCP/UDP), Garena Gaming Client (port 1521), nCube License Manager (port 1521), Oracle database (default listener port 1521, alternative for future releases unofficial port 1527), Apache Derby Network Server (default port 1533), IBM Sametime IM-Virtual Places Chat (port 1534/UDP), Eclipse Target Communication Framework agent discovery (ports 1547/TCP/UDP), Laplink (ports 1550/TCP/UDP), 3M Image Storage license manager (port 1550), Gadu-Gadu direct client-to-client (port 1581/UDP), MIL STD 2045-47001 VMF (port 1583), Pervasive PSQL (port 1589), Cisco VQP (VLAN Query Protocol, port 1590), GE Smallworld Datastore Server (SWMFS/Smallworld Master Filesystem, port 1627), iSketch (ports 1645/TCP/UDP), RADIUS authentication protocol for Cisco and Juniper Networks (port 1646/TCP/UDP), and Novell GroupWise clients in client/server access mode (port 1688). Here's a summary of the provided text, focusing on service names and their associated protocol types:

• **Microsoft Key Management Service for KMS Windows Activation** - UDP 1700

• **Cisco RADIUS Change of Authorization for TrustSec** - UDP 1701

• **Layer 2 Forwarding Protocol (L2F) & Layer 2 Tunneling Protocol (L2TP)** - UDP 1707, TCP 1707

• **Windward Studios** - Both protocols are unspecified but mentioned in context of service 1707.

• **America's Army** - A massively multiplayer online game - UDP 1716

• **H.323 Registration and alternate communication** - TCP 1719, UDP 1719

• **Call signalling for H.323** - TCP 1720, UDP 1720

• **Microsoft Point-to-Point Tunneling Protocol (PPTP)** - UDP 1725

• **Valve Steam Client** - Both protocols are unspecified but mentioned in context of service 1755.

• **Microsoft Media Services (MMS, ms-streaming)** - UDP 1761, TCP 1761

• **Novell Zenworks Remote Control utility** - TCP 1762 to 1768, UDP unspecified but likely UDP as well based on pattern.

• **Federal Emergency Management Information System** - Both protocols are unspecified but mentioned in context of service 1792.

• **Moby** - Both protocols are unspecified but mentioned in context of service 1801.

• **Microsoft Message Queuing** - TCP 1812, UDP 1812

• **RADIUS authentication protocol** - TCP 1813, UDP 1813

• **RADIUS accounting protocol** - TCP 1863, UDP 1863

• **Microsoft Notification Protocol (MSNP), used by Microsoft Messenger service and Instant Messaging clients** - TCP unspecified but likely TCP.

• **MQ Telemetry Transport (MQTT)** - Both protocols are unspecified but mentioned in context of service 1883.

• **Leonardo over IP** - Pro2col Ltd, UDP 1900

• **Microsoft SSDP for UPnP device discovery** - UDP 1920

• **IBM Tivoli monitoring console** - TCP 1935

• **Flash Real Time Messaging Protocol (RTMP)** - Both protocols are unspecified but mentioned in context of service 1947.

• **SentinelSRM (hasplm), Aladdin HASP License Manager** - UDP 1967

• **Cisco IOS IP Service Level Agreements (IP SLAs) Control Protocol** - TCP unspecified but likely TCP.

The text provides a list of various protocols and services along with their associated years, names, and some details about their status or usage. Here's a summarized version:

• **1972**: TCP - No specific service named; only the protocol is mentioned.

• **1975-1977**: UDP - Cisco TCO (Technical Coordination Office) documentation.

• **1984**: Various services including Big Brother, Xymon (formerly Hobbit), and related systems for network monitoring.

• **1985**: UDP - Cisco HSRP (Hot Standby Router Protocol).

• **1994**: TCP, UDP - Cisco STUN-SDLC (Serial Tunneling – Synchronous Data Link Control) protocol.

• **1997**: TCP - Chizmo Networks Transfer Tool .

• **1998**: TCP, UDP - Cisco XOT service (Xymon over TCP).

• **2000**: TCP, UDP - Cisco SCCP (Skinny Client Control Protocol).

• **2001**: UDP - CAPTAN Test Stand System.

• **2002**: TCP - Secure Access Control Server (ACS) for Windows .

• **2008**: TCP - Stylex Secured server.

• **2010**: TCP - Artemis: Spaceship Bridge Simulator default port.

• **2014**: TCP - Remoticus.

• **2030**: Oracle services for Microsoft Transaction Server.

• **2031**: TCP, UDP - mobrien-chat (http://chat.mobrien.com:2031).

• **2041**: TCP - Mail.Ru Agent communication protocol .

• **2049**: TCP, UDP - Network File System and shilp.

• **2053**: TCP - knetd, Kerberos de-multiplexor.

• **2056**: UDP - Civilization 4 multiplayer.

• **2074**: TCP, UDP - Vertel VMF SA (i.e., App.. SpeakFreely).

• **2080**: TCP, UDP - Autodesk NLM (FLEXlm).

• **2082**: TCP - Infowave Mobility Server and CPanel.

• **2083**: TCP - Secure Radius Service (radsec) and CPanel with SSL.

• **2086**: TCP - GNUnet and WebHost Manager.

• **2087**: TCP - WebHost Manager with SSL.

• **2095**: TCP - CPanel default web mail.

• **2096**: TCP - CPanel default SSL web mail.

• **2102**: TCP, UDP - zephyr-srv and related services for Project Athena.

• **2103**: TCP, UDP - zephyr-clt and zephyr-hm connections.

• **2104**: TCP, UDP - IBM MiniPay and eklogin, Kerberos encrypted remote login (rlogin).

Note: The status of some entries is marked as "Unofficial" or not specified clearly in the text provided. The project Athena includes a range of services and applications, each with its specific port numbers. These include TCP and UDP connections used by various departments like MIS (Management Information Systems) and the FTP proxy service. Some notable entries are Zephyr Notification Service (2102), APC Agent (2160 & 2161), EForward-document transport system (2181), Apple Push Notification service (2195 & 2196), Tuxanci game server (2200), NOAAPORT Broadcast Network (2210), and CoMotion Master/Backup (2262). Other services include ArmA multiplayer for gaming, direct administration of servers by DirectAdmin, and updates from ESET antivirus. This text lists various port numbers and their usage, detailing whether they are official or unofficial, the protocol (TCP or UDP), and the software context in which they are typically used. Some examples include:

• **2370 TCP** is the default port for BMC Software Control-M/Server, set up to allow Control-M/Enterprise Manager connections during installation.

• **2381 TCP** is unofficial and is the default port for HP Insight Manager Web server.

• **2401 TCP** is official and used by the version control system CVS.

• **2420 UDP** is unofficial and corresponds to Westell Remote Access.

• **2424 TCP** is official and pertains to OrientDB, a database listening for Binary client connections.

• **2427 UDP** is official and linked to Cisco MGCP.

• **2447 TCP/UDP** refers to the OpenView Network Node Manager (NNM) daemon.

• **2480 TCP** and **2484 TCP/UDP** are related to Oracle databases, with the former listening for HTTP client connections and the latter for SSL client connections.

• **2500 TCP** is used by THEÒSMESSENGER for client communications.

• **2518 TCP/UDP** pertains to Willy, potentially a software name or reference unclear from this context.

• **2525 TCP** is the default port for SMTP (Simple Mail Transfer Protocol), an alternate usage.

• **2535 TCP** is unofficial and associated with MADCAP - Multicast Address Dynamic Client Allocation Protocol.

• **2546 TCP** pertains to EVault data protection services.

• **2593 TCP/UDP** is used by RunUO—a server for the game Ultima Online.

• **2598 TCP** and **2599 TCP** are unofficial ports, with 2598 replacing port 1494 in ICA (Citrix) sessions when Session Reliability is enabled.

• **2610 TCP** is for tracking mobile device monitoring via TrackiT.

• **2636 TCP** pertains to Solve Service.

• **2638 TCP** is associated with the SQL Anywhere database server.

This text provides a list of various port numbers and the protocols (TCP, UDP) they use, along with some information about what services or applications are associated with these ports. Some entries include the name of the service or application, whether it is official or unofficial, and sometimes additional details such as being per a specific standard or protocol like CORBA or GridFTP. Here's a summary:

• 2641 to 2967: These port numbers are used for various services including TCP (Transmission Control Protocol) and UDP (User Datagram Protocol). Some examples include HDL Server from CNRI, XBT Tracker, Citel / MCK IVPIP, NetIQ Monitor Console, GPS daemon (gpsd), WAP-push Multimedia Messaging Service (MMS), Symantec AntiVirus Corporate Edition, and others. The status is either official or unofficial depending on the service.

• 2710: This port number has both TCP and UDP entries for XBT Tracker and experimental UDP tracker extension, as well as for Knuddels.de which is unofficial.

• 2809 to 2827: These ports are related to CORBA (Common Object Request Broker Architecture) specifications, with some being official and others unofficial depending on the service or application. For example, corbaloc:iiop URL, IBM WebSphere Application Server (WAS), GridFTP specification, I2P Basic Open Bridge API, Norman Proprietary Event Protocol NPEP, and Megaco text/binary H.248 are mentioned.

• 3000 to 3017: These ports are used for various proprietary or open source software services including Miralix License server, Cloud9 Integrated Development Environment server, Distributed Interactive Simulation (DIS), Ruby on Rails development default, and other unspecified services which also have an unofficial status.

In summary, the text lists a range of port numbers with their associated protocols along with information about what service or application is using them, whether they are official according to specific standards or considered unofficial based on the context provided in the text. The text provides a summary of various ports and their associated protocols, services, and applications. Here is a breakdown of the information presented:

• **TCP and UDP Ports**: The document lists several TCP and UDP ports along with their corresponding service or application. Some examples include Galaxy Server (Gateway Ticketing Systems) on port 3052, SAP-Router for SAP R/3 on port 3300, and Debate Gopher backend database system on port 3305.

• **Service Descriptions**: Each entry includes a description of the service or application running on the specified port. For example, "Galaxy Server (Gateway Ticketing Systems)" is mentioned as an official service using port 3052.

• **Source Information**: The source of this information is not explicitly stated, but it is referred to as "Unofficial" in some cases, indicating that the data might not be verified or confirmed by a trusted authority.

• **Protocol Usage**: Some ports are specified as using either TCP (Transmission Control Protocol) or UDP (User Datagram Protocol). For instance, port 3290 is used for Apple Remote Desktop reporting and specified as official, while port 3299 uses SAP-Router and is labeled unofficial.

In summary, this document provides a list of network ports with their associated protocols and services, including some details about the applications or protocols running on these ports. The reliability of the information provided may vary, with "Unofficial" entries possibly not verified through official channels. This is a list of port numbers and their protocols (TCP or UDP) used for various services and applications. Here's the summary:

• 3389: Used by Microsoft Terminal Server, now known as Remote Desktop Protocol (RDP), which allows remote access to Windows-based terminals.

• 3396: Used by Novell NDPS Printer Agent.

• 3412: Used by xmlBlaster for data delivery and management in distributed systems.

• 3455: Used by RSVP Reservation Protocol, which manages the allocation of network resources like bandwidth.

• 3423: Used by xTrm Communication Protocol, possibly for real-time communication or file transfer.

• 3424: SSL version of the above protocol.

• 3478: Used by STUN and TURN protocols for NAT (Network Address Translation) traversal, crucial for establishing peer-to-peer connections over networks with multiple routers.

• 3483: Used by Slim Devices for their discovery protocol, possibly used in home networking to discover devices like printers or media servers.

• 3493: Used by Network UPS Tools (NUT), which manage uninterruptible power supplies and other power management tasks.

• 3516: Used by Smartcard Port, potentially for secure communication with smart card readers.

• 3527: Used by Microsoft Message Queuing, a technology facilitating message-oriented middleware in distributed applications.

• 3535: SMTP alternate port, used by Simple Mail Transfer Protocol (SMTP) for email transmission.

• 3537: Used by ni-visa-remote, possibly for remote access or control of Visa card services.

• 3544: Teredo tunneling is a method to enable IP traffic to pass through NATs and firewalls using UDP port 3544.

• 3562: SDBProxy is used for middleware between applications and databases, supporting simple data management tasks over TCP.

• 3605: ComCam IO Port is associated with specific I/O devices or communication interfaces.

• 3606: Splitlock Server operates on port 3606, possibly handling secure or encrypted communications.

• 3632: Used by a distributed compiler for efficient code compilation across multiple machines.

• 3689: Digital Audio Access Protocol (DAAP) is used by Apple's iTunes and AirPort Express for audio streaming and management.

• 3690: Subversion (SVN) is a version control system used in software development, supporting file sharing between team members.

• 3702: WS-Discovery is part of the Windows Vista Web Services Dynamic Discovery protocol, facilitating automatic discovery of network services.

• 3724: Used by some Blizzard games and Club Penguin, possibly for game server communication or specific gaming features.

• 3784: Ventrilo VoIP program uses port 3784 (UDP) for voice communications over the internet.

• 3785: Another UDP port used by the same VoIP program, Ventrilo.

• 3799: RADIUS protocol is used for network access and authorization management.

• 3800: Used by HGG programs, which are unclear from this list; additional context might be needed to identify these programs fully.

• 3825, 3826, and 3835: These ports are used by RedSeal Networks for client/server connections, potentially handling secure network interactions.

• 388: This port number is listed but not associated with any specific service or protocol; it might be reserved, unused, or incorrectly documented.

The text provides a list of port numbers and their associated protocols, services, or software. Here's a summary of each entry:

• **0**: TCP/UDP - Reserved for future use (not used by any standard protocol).

• **3868**: TCP - IGRS (Internet Gateway Remote Services), an unofficial protocol.

• **3872**: TCP - Oracle Management Remote Agent, an unofficial service.

• **3899**: TCP - Remote Administrator, an unofficial service.

• **3900**: TCP/UDP - UDT OS (Universal Data Transport Operating System) used by IBM UniData, an unofficial protocol.

• **3945**: TCP/UDP - EMCADS service provided by Giritech for G/On, an official service.

• **3978**: TCP/UDP - OpenTTD game (masterserver and content service), an unofficial service.

• **3979**: TCP/UDP - OpenTTD game, an unofficial service.

• **3999**: TCP/UDP - Norman distributed scanning service, an official service.

• **4000**: TCP/UDP - Diablo II game, an unofficial service.

• **4001**: TCP - Microsoft Ants game, an unofficial service.

• **4007**: TCP - PrintBuzzer printer monitoring socket server, an unofficial service.

• **4018**: TCP/UDP - Protocol information and warnings, an official service.

• **4035**: TCP - IBM Rational Developer for System z Remote System Explorer Daemon, an unofficial service.

• **4045**: TCP/UDP - Solaris lockd NFS lock daemon/manager, an unofficial service.

• **4069**: UDP - Minger Email Address Verification Protocol, an official service.

• **4089**: TCP/UDP - OpenCORE Remote Control Service, an official service.

• **4093**: TCP/UDP - PxPlus Client server interface provided by ProvideX, an official service.

• **4096**: TCP/UDP - Ascom Timeplex BRE (Bridge Relay Element), an official service.

• **4100**: TCP - WatchGuard authentication applet default, an unofficial service.

• **4105**: TCP/UDP - Xgrid, an official service.

• **4111**: TCP - Smartcard-TLS, an official service.

• **4125**: TCP - Microsoft Remote Web Workplace administration, an unofficial service.

• **4172**: TCP/UDP - Teradici PCoIP, an official service.

• **4190**: TCP - ManageSieve email filtering protocol, an official service.

• **4201**: TCP/UDP - TinyMUD and various derivatives, an unofficial service.

• **4226**: TCP/UDP - Aleph One (game), an unofficial service.

• **4224**: TCP - Cisco Audio Session Tunneling, an unofficial service.

• **4242**: TCP/UDP - Reverse Battle Tetris and Orthanc DICOM port, both unofficial services.

• **4303**: TCP - Simple Railroad Command Protocol (SRCP), an official service.

• **4321**: TCP - Referral Whois (RWhois) Protocol, an official service.

• **4433-4436**: TCP - Axence nVision, an unofficial service.

This text lists various port numbers and their uses in different network communications, including TCP (Transmission Control Protocol) and UDP (User Datagram Protocol). Some examples are for official protocols like IPsec NAT Traversal (RFC 3947), OPC UA TCP Protocol for OPC Unified Architecture, and others. The ports range from 4444 to 4894, serving a variety of purposes such as proxy connections, specific software services (like Microsoft Silverlight, Google Desktop Search, and optional web interfaces for eMule), gaming servers (e.g., Armagetron Advanced, Inter-Asterisk Exchange), sound server (PulseAudio), and enterprise management tools (Computer Associates Desktop and Server Management, Gearman job server). The usage is not always official, with some ports marked as unofficial or used by specific software versions only. The text lists a variety of port numbers and their associated protocols (TCP, UDP) as well as the context or service they are typically used for. Here's a summary of each entry:

• **cial 4899**: No specific information available about what uses this port.

• **4949 TCP**: Munin Resource Monitoring Tool.

• **4950 TCP, UDP**: Cylon Controls UC32 Communications Port.

• **4982 TCP**: Solar Data Log (JK client app for PV solar inverters).

• **4993 TCP, UDP**: Home FTP Server web Interface Default Port.

• **5000 TCP, UDP**: Various uses including VTun VPN software, UPnP Windows network device interoperability, FlightGear multiplayer (UDP), SOLICARD ARX, Drobo Dashboard, FileMaker, RTP media data and RTCP control protocol.

• **5001 TCP, UDP**: Slingbox, Iperf for measuring bandwidth performance, Synology Inc. Management Console, Audio Station with secured options.

• **5002 TCP, UDP**: SOLICARD ARX, Drobo Dashboard.

• **5003 TCP, UDP**: FileMaker.

• **5004 TCP, DCCP**: RTP media data (RFC 3551, RFC 4571).

• **5005 TCP, DCCP**: RTCP control protocol (RFC 3551, RFC 4571).

• **5010 TCP, UDP**: Registered to TelePath for IBM WebSphere MQ Workflow.

• **5029 TCP**: Sonic Robo Blast 2: Multiplayer.

• **5031 TCP, UDP**: AVM CAPI-over-TCP (ISDN over Ethernet tunneling).

• **5037 TCP**: Android ADB server.

• **5050 TCP**: Yahoo! Messenger.

• **5051 TCP**: ita-agent for Symantec Intruder Alert.

The provided list includes various port numbers associated with different protocols and services. Here's a summary of each entry:

• **SIP Ports**: 5060 (TCP), 5061 (TCP over TLS, TCP), and 5070 (UDP). These are related to the Session Initiation Protocol (SIP) for VoIP communications.

• **BFCP (Binary Floor Control Protocol)**: Port 5071 is used with RFC 4582, supporting a content channel in video conferencing alongside SIP.

• **Qpur Communication and File Protocols**: Ports 5082, 5083, and 5084 are associated with Qpur protocols for unspecified purposes.

• **EPCglobal LLRP (Low Level Reader Protocol)**: Ports 5085 (TCP over TLS), 5093 (UDP), and 5099 (TCP). These are used in RFID technology.

• **Tivoli Framework NetCOOL/Impact**: Port 5104 uses HTTP for a service, likely related to management or monitoring of systems.

• **A-Talk Communications**: Ports 5106 and 5107 are used for A-Talk client connections (local and remote server).

• **VPOP3 Mail Server Webmail**: Ports 5108 and 5109, which might be related to accessing webmail services via POP3.

• **ProRat Server**: Port 5121 is used for ProRat servers, possibly related to remote control or support tools.

• **TorgaNET (Micronational Darknet)**: Ports 5124 and 5125 are used in the network of a specific micronation's intelligence operations.

• **ATMP (Ascend Tunnel Management Protocol)**: Port 5150 is associated with this protocol, possibly managing VPN or tunneling connections.

• **Cerberus RAT (Remote Administration Tool)**: Port 5151 is used in malware instances of Cerberus for remote control.

• **ESRI SDE Instance and Remote Start**: Ports 5151 (TCP) and 5154 (UDP), likely related to ESRI spatial database environment management.

• **BZFlag Game Server**: Port 5154 is used by the BZFlag game server, supporting multiplayer gaming over network connections.

These ports are crucial in identifying the specific services running on a given system and can be configured for security or optimization purposes within networks. This text lists various protocols and their associated port numbers, along with whether they are official or unofficial, and the transport layer protocol being used (either TCP or UDP). The items listed include XMPP client/server connections over SSL, HP Virtual Room Service, Google Cloud Messaging, CAPWAP control and data, STUN for NAT traversal, TURN for NAT traversal, Multicast DNS, LLMNR for local network name resolution, Web Services for Devices API, OmniCast content delivery system, mftp file sharing protocol, and Stratacache. Some examples are:

• Extensible Messaging and Presence Protocol (XMPP) client connection over SSL uses ports 5298 (TCP) and 5228 (TCP).

• HP Virtual Room Service is official with ports 5228 (TCP).

• Google Cloud Messaging uses port 5246 (UDP).

• CAPWAP control and data are official with ports 5247 (UDP) and 5269 (TCP).

• STUN for NAT traversal uses port 5349 (TCP).

• TURN for NAT traversal also uses port 5349 (TCP).

• Multicast DNS operates on port 5355 (UDP).

• LLMNR for local network name resolution is official with ports 5357 (TCP) and 5355 (UDP).

• Web Services for Devices API is unofficial with ports 5358 (TCP) and 5394 (UDP).

• OmniCast content delivery system uses port 5405 (TCP).

• mftp file sharing protocol operates on ports 5402 (TCP) and 5402 (UDP).

This summary provides a list of port numbers used by various software applications, along with their protocol (TCP or UDP), source, and official/unofficial designation. The ports listed include: 1. lelogic Synergy - Not specified (Continuus CM Message Router 5413 TCP/UDP) 2. Wonderware SuiteLink service - Official (5421 TCP/UDP) 3. NetSupport Manager - Official (5432 TCP/UDP) 4. PostgreSQL database system - Official (5433 TCP) 5. Bouwsoft file/webserver - Unofficial (5445 UDP) 6. Cisco Unified Video Advantage - Unofficial (5450 TCP) 7. OSIsoft PI Server Client Access, Asset Framework Client Access, and Notifications Client Access - Unofficial (all on 5458 TCP) 8. VMware VAMI - Unofficial (5495 TCP) 9. IBM Cognos TM1 Admin server - Unofficial (5498 TCP) 10. Hotline tracker server connection/discovery - Unofficial (both ports 5499 UDP and 5499 TCP) 11. VNC remote desktop protocol for incoming listening viewer - Unofficial (5500 TCP, used with Hotline control and file transfer connections) 12. Setiqueue Proxy server client for SETI@Home project - Unofficial (5517 TCP) 13. Hewlett-Packard Data Protector - Unofficial (5550 TCP/UDP) 14. Oracle WebCenter Content Inbound Refinery - Intradoc Socket port, formerly known as Oracle Universal Content Management (5555 TCP/UDP) 15. Freeciv versions up to 2.0, Hewlett-Packard Data Protector, McAfee EndPoint Encryption Database Server, SAP, Default for Microsoft Dynamics CRM 4.0 - Unofficial (all on 5555 TCP/UDP) 16. Oracle WebLogic Server Node Manager - Official (5591 TCP) 17. pcANYWHEREdata and status - Official (both ports 5631 TCP and 5632 UDP, version 7.52 and later of Symantec pcAnywhere) 18. IBM Lotus Sametime p2p file transfer - Unofficial (5656 TCP) These port numbers are used for different purposes in various software applications, ranging from data communication between devices to remote desktop access and server communications. This is a list of port numbers and the protocols they are associated with, along with some additional information about each service. Here's a summary:

• **66 TCP**: NRPE (Nagios) - An unofficial protocol used for remote monitoring.

• **5667 TCP**: NSCA (Nagios) - Another unofficial protocol used for the same purpose.

• **5672 TCP**: AMQP <86> - Official, a standard messaging protocol.

• **5678 UDP**: Mikrotik RouterOS Neighbor Discovery Protocol (MNDP) - Unofficial, possibly for network discovery.

• **5683 UDP**: CoAP <5683> - Official, used for constrained applications on the internet.

• **5721 TCP/UDP**: Kaseya - An unofficial software or service related to remote support and management.

• **5741 TCP/UDP**: IDA Discover Port 1 & 2 - Official, possibly for network discovery in some system or application.

• **5800 TCP**: VNC (Virtual Network Computing) over HTTP - Unofficial, typically used for remote desktop connections.

• **5814 TCP/UDP**: HP Support Automation (HP OpenView Self-Healing Services) - Unofficial, possibly related to technical support tools.

• **5850 TCP**: COMIT SE (PCR) <87> - Unofficial, a protocol used in some specific network setups or applications.

• **5852 TCP**: Adeona client: communications to OpenDHT - Unofficial, possibly for decentralized communication.

• **5900 TCP/UDP**: Remote Frame Buffer protocol (RFB), Virtual Network Computing (VNC) remote desktop protocol - Official and unofficial uses for accessing remote graphical user interfaces.

• **5912 TCP**: Default for Tidal Enterprise Scheduler agent-Socket used for communication between Master-to-Agent, though can be changed - Unofficial, possibly related to scheduling or automation services.

• **5938 TCP/UDP**: TeamViewer remote desktop protocol - Unofficial, likely used for remote support and access.

• **5984 TCP/UDP**: CouchDB database server - Official, a NoSQL database service.

• **5985 TCP**: Windows PowerShell Default psSession Port - Official, standard port for PowerShell sessions over the network.

• **5986 TCP**: Same as 5985, another instance of the same official port used by Windows PowerShell.

• **5999 TCP**: CVSup file update tool - Official, typically used in software distribution and version control systems.

• **6000 TCP/UDP**: X11 (used between an X client and server over the network) - Official, standard ports for graphical user interface access across networks.

• **6050 TCP/UDP**: Arcserve backup or Nortel software - Unofficial, possibly related to data protection or telecommunications equipment.

• **6072 TCP**: iOperator Protocol Signal Port - Unofficial, specific to a protocol used in some network operations or management systems.

• **6086 TCP**: PDTP (FTP like file server) - Official, as part of the protocol suite for transferring files over networks.

The text lists several port numbers and their usage across different software applications. Here is the summarized data: 1. **Ventrilo** - A P2P network uses ports 6100 (TCP) for authentication, which must be allowed outbound for version 3 of Ventrilo. 2. **Backup Exec Agent Browser** has an unofficial port number of 6100 (TCP). 3. **Ventrilo** also uses an unofficial port number of 6112 (UDP and TCP) which is used by "dtspcd" for remote command execution and application launching. 4. **Blizzard's Battle.net**, **ArenaNet**, and **Relic** gaming services use an unofficial port number of 6112 (TCP). 5. **Club Penguin** uses ports 6113 (TCP) and unofficial usage is noted for some Blizzard games as well. 6. **DameWare Remote Control** operates on port 6129 (TCP). 7. **ARINC 840 EFB Application Control Interface** has a port number of 6159 (TCP). 8. **Oracle WebCenter Content Portable** series uses various unofficial ports:

• Content Server with Native UI on 6200 (TCP) and Admin on 6201 (TCP).

• Content Server Web UI on 6225 (TCP), JavaDB on 6227 (TCP).

• Intradoc Sockets are used for Capture on 6240 (TCP) and Inbound Refinery on 6255 (TCP), both with unofficial usage.

9. **WinMX** uses port 6257 (UDP). 10. **Planet M.U.L.E.** operates on an unofficial port number of 6260 (both TCP and UDP). 11. **Sybase Advantage Database Server** has an unofficial port number of 6324 (TCP). 12. **Hall Research Device discovery and configuration** uses port 6343 (UDP). 13. **SFlow, sFlow traffic monitoring** operates on port 6346 (UDP). 14. **gnutella-svc**, **gnutella-rtr**, and various P2P networks like FrostWire, Limewire, Shareaza use ports 6347 (TCP) and 6350 (TCP), along with UDP counterparts. These port numbers are significant for network configuration, especially in a corporate environment where firewalls or routers need to be configured to allow specific traffic through the necessary ports. This text lists various port numbers and their protocols, along with a brief description or service associated with each. Here's a summary of the information provided:

• **EMC CLARiiON**: Access Protocol - Official (port 6389, TCP)

• **PgBouncer**: A connection pooler for PostgreSQL - Official (port 6444, TCP)

• **Sun Grid Engine**: Qmaster Service (port 6445, TCP), Execution Service (port 6445, UDP)

• **Elipse**: RPC Protocol (REC) - Official (port 6514, TCP)

• **Gobby**: Software based on libobby and libinfinity protocols (ports 6522, 6523, TCP/UDP)

• **SANE**: SANE network scanner daemon - Official (port 6560-6561, TCP)

• **Speech-Dispatcher**: Daemon - Official (port 6571, TCP)

• **Windows Live FolderShare**: Client - Unofficial (port 6601, TCP)

• **McAfee Network Agent**: Unofficial (port 6646, UDP)

• **Internet Relay Chat** (IRC): Default ports are 6660-6664 (TCP), 6665-6669 (TCP), and SSL versions (ports 6697, 6699, TCP)

• **WinMX**: Unofficial (port 6699, TCP)

• **BitTorrent**: Most often used ports are 6881-6887 (TCP/UDP), with a specific mention of MUSE using port 6888 (TCP/UDP)

These entries provide details about various network services and applications that use specific ports for communication, including protocols like TCP and UDP. The text provides a list of port numbers and their associated protocols, services, and usage notes. Here's a summary:

• **889–6890**: These ports are part of the unofficial full range used most often for BitTorrent and related services.

• **6891–6900**: Also for BitTorrent and other unspecified services, mostly unofficial.

• **6901**: Used for Windows Live Messenger's file transfer (TCP) and voice (UDP), also unofficial.

• **6902–6968**: More BitTorrent related ports, still unofficial.

• **6969**: Specific for acmsoda and used as a BitTorrent tracker, also unofficial.

• **6970–6999**: Continuation of the BitTorrent range, mostly unofficial.

• **7000**: Default port for Vuze's built-in HTTPS Bittorrent Tracker, unofficial.

• **7001**: For BEA WebLogic Server's HTTP and HTTPS servers, often changed during installation, unofficial.

• **7002, 7005**: Ports for BMC Software Control-M/Server and Agent configurations, also unofficial.

• **7010**: Used for Cisco AON AMC (AON Management Console), unofficial.

• **7022, 7023**: For database mirroring endpoints and unspecified communication, mostly unofficial.

• **7025**: Zimbra LMTP (local mail delivery) server port, unofficial.

• **7047**: Zimbra conversion server, unofficial.

• **7080**: Sepialine Argos Communications port, unofficial.

• **7133**: Enemy Territory: Quake Wars game server, unofficial.

• **7144, 7145**: Peercast network services, mostly unofficial.

• **7171**: Tibia gaming service, unofficial.

• **7306, 7307**: Zimbra mysql mailbox and logger ports, mostly unofficial.

• **7312**: Sibelius License Server port, unspecified as official or unofficial.

These ports are used for various network services such as file sharing (BitTorrent), instant messaging (Windows Live Messenger), email (Zimbra), gaming (Enemy Territory: Quake Wars), and others, often with unofficial status unless specified otherwise. The text lists various port numbers and protocols used in different applications and services, including operating systems, games, utilities, and network management tools. Some examples are:

• Folding@home v7.3.6 has a Web control interface on TCP 7396 (Unofficial)

• I2P uses UDP 7655 for the SAM Bridge Socket API and TCP ports 7656-7660 for an anonymizing overlay network (Unofficial)

• P2P DC (RedHub) is on UDP 7700 (Unofficial)

• Killing Floor, San Andreas Multiplayer, Bad Trip MUD use UDP 7707 and 7708 (Unofficial)

• Unreal Tournament series defaults to TCP ports 7777-7788 and UDP port 7777 (Unofficial)

• GFI EventsManager 7 & 8 is official for TCP ports 7787-7788.

This is a list of TCP and UDP ports along with their purposes. Many of these are unofficial uses, while others have official designations. Here's the summary:

• 7915: Used as a default port for YSFlight server (Unofficial)

• 7935: Fixed port used for Adobe Flash Debug Player to communicate with debugger tools (Adobe Flash IDE, Flex Builder or fdb) (Unofficial)

• 7937-9936: TCP and UDP ports used by EMC 2 Legato Networker or Sun Solstice Backup (Official)

• 8000: Used for iRDMI (Intel Remote Desktop Management Interface), can be found on port 8000 both as TCP and UDP, sometimes erroneously used instead of port 8080 (Official)

• 8001: Commonly used for internet radio streams using SHOUTcast (Unofficial)

• 8002: Used by Cisco Systems Unified Call Manager Intercluster (Unofficial)

• 8008: HTTP, alternate port often used for IBM HTTP Server administration (Official and unofficial)

• 8009: ajp13 - Apache JServ Protocol AJP Connector (Unofficial)

• 8010: XMPP file transfers (Unofficial)

• 8011-8013: HTTP/TCP ports used by Symon Communications Event and Query Engine (Unofficial)

• 8014: HTTP/TCP ports used by Symon Communications Event and Query Engine (Unofficial)

• 8020: Used by 360Works SuperContainer (Unofficial)

• 8042: Default port for Orthanc GUI (Unofficial)

• 8069: OpenERP default HTTP port for web interface and xmlrpc calls (Unofficial)

• 8070: Legacy netrpc protocol for OpenERP (Unofficial)

• 8074: Gadu-Gadu communication port (Unofficial)

• 8075: Killing Floor game server port (Unofficial)

• 8078: Default port for most Endless Online-based servers (Unofficial)

• 8080: Commonly used for HTTP, can also be a web proxy or caching server (Official and unofficial)

The text discusses various ports used by different software and services, primarily as unofficial or non-standard usage. Here's a summary of the key points: 1. **Web Server Ports**:

• **Apache Tomcat** is associated with port 8080 for both TCP (official) and UDP (Unofficial).

• **FilePhile** uses port 8080 for TCP, while Vermont Systems / RecTrac (WebTrac), Parallels Plesk Control Panel, and VibeStreamer use port 8080 for TCP.

• **CouchBase** has a web administration interface on port 8091 for TCP (Unofficial) and an API on port 8092 for TCP (Unofficial).

2. **Other Services**:

• **VibrateStreamer**, **ePolicy Orchestrator (ePO)**, **Hosting Accelerator**, **Check Point Cluster Control Protocol**, and **Bloomberg Application** all use port 8086/TCP for unspecified services.

• **JOSM** uses port 8111 for remote control over TCP, while **Pacifica Coin** uses port 8116 for UDP communication.

• **Privoxy** is an official service using port 8123 for a web proxy (TCP).

• **GoToMyPC** utilizes port 8200 for unspecified services, and **VMware Server Management User Interface** uses both TCP (8222) and UDP (8243/8280) but is considered insecure.

These ports are not standard and are used by various applications in non-conventional ways, often bypassing the typical port usage for their respective protocols. The provided text lists various port numbers and their usage for different applications, mostly related to network protocols and server management tools. Some of the key points include: 1. **Teeworlds Server** uses UDP port 8303. 2. **MultiBit**, **Bitcoin JSON-RPC server**, and **Bitmessage** use TCP ports 8331, 8332/8333 (for Bitcoin), and 8444 respectively. 3. **VMware Server Management User Interface** uses TCP port 8333. 4. **MapleStory Login Server** and various game servers use ports 8500, 8585 to 8589 for UDP and TCP connections. 5. **Wavestore CCTV protocol** is associated with ports 8601 (TCP) and 8602 (UDP). 6. **Ultra Fractal** uses TCP port 8691 for distributed calculations across network computers. 7. **TeamSpeak** utilizes UDP ports 8701/8767 and alternate ports 8702/8768, while the **EPOS Speech Synthesis System** uses TCP port 8787. 8. **MapleStory CashShop Game Server** operates on TCP ports 8787 and 8788. 9. **Nessus web interface** is associated with port 8834. 10. **Opera Unite server** uses UDP port 8880, with both TCP and UDP versions sharing this port number. 11. **WebSphere Application Server** uses default SOAP connector ports including 8880 for its services. These are all unofficial or non-standard port numbers used by various software applications to communicate over the network, often bypassing standard well-known ports which range from 1 to 1024 and typically assigned to common services like HTTP (port 80), HTTPS (port 443), FTP (ports 20/21), SSH (port 22), etc. This text provides a list of TCP and UDP ports used by various software applications, servers, and protocols. Some entries are marked as unofficial or have "

" indicating that the information might be unverified or incomplete. Here is a summary of the key points from each entry:

• **TCP Ports:**

• **8881**: Used by Atlasz Informatics Research Ltd for their "Secure Application Server."

• **8882**: Also used by Atlasz Informatics Research Ltd's "Secure Application Server," though it is marked as unofficial.

• **8883**: Uses TCP and UDP, with Secure MQ Telemetry Transport (MQTT over SSL) being the service.

• **8886**: Used by PPM3 (Padtec Management Protocol version 3), which is unofficial.

• **8887**: Hosted by HyperVM using HTTP protocol, though it's also marked as unofficial.

• **8888**: Hosts multiple services including Freenet with HTTP and Sun Answerbook via dwhttpd server (deprecated).

• **8889** and **8889** are both used by MAMP servers, which is unofficial.

• **8937**: Transaction Warehouse Data Service (TWDS) is hosted on this port, also official.

• **8983**: Default for Apache Solr.

• **8998**: Used by I2P Monotone Repository, which is unofficial.

• **9000** to **9002**, **9009**: Host various services including Play! Framework web server, Hadoop NameNode, ETL Service Manager, and Pichat Server.

• **9009**: Newforma Server comms, which is unofficial.

• **UDP Ports:**

• **9000** to **9002**: Used by various services including SqueezeCenter web server & streaming, UdpCast, and Play! Framework web server.

• **9009**: Pichat Server used by Pee, also unofficial.

• **Other:**

• There are references to software like Win Media Streamer, SOAP connector, QFlex (IBM WebSphere MQ monitoring), and Buffalo LinkSystem Web access, all marked as unofficial unless otherwise specified.

This list provides an overview of the ports used for different applications and servers, useful for network configuration and management purposes. This text lists various ports and their associated software, categorized by whether the information is official or unofficial. Some examples include:

• **r to peer chat software**: Official (9010), Official (9025), Official (9030), Unofficial (9043), Unofficial (9050), Unofficial (9051), Unofficial (9060)

• **Web services**: Official (9080, both TCP and UDP), Official (9080, TCP), Unofficial (9090, various software including Webwasher, Secure Web, McAfee Web Gateway, Openfire, SqueezeCenter, Cherokee, Transmission, WebSphere Application Server)

• **Instant messengers**: Official (9110), Unofficial (9119)

• **Collaboration software**: Official (9080, TCP), Official (9080, UDP)

• **Remote administration tools**: Official (9100, 9101, 9102, 9103, 9105, 9106, 9107), Unofficial (9199)

• **Business Intelligence and Performance Management**: Unofficial (9300)

• **Distributed file systems**: Official (9309), Official (9418)

• **BitTorrent clients**: Unofficial (9100, Transmission Web Interface)

The ports are specified as TCP or UDP, and include software names such as Tor, WebSphere Application Server, Openfire, SqueezeCenter, Cherokee, Git, MooseFS, and more. Some of these entries also specify if they are unofficial or official, based on the source providing the information. This text lists several port numbers and their associated services. The ports are categorized as official or unofficial based on their source. Official ports are specified by IANA (Internet Assigned Numbers Authority), while unofficial ports may be used by specific software or protocols without official recognition. Here is the summarized list of port numbers, services, and types:

• **9421 TCP** - MooseFS distributed file system—master server to clients

• **9422 TCP** - MooseFS distributed file system—chunk servers to clients

• **9443 TCP** - VMware HTTPS port for vCenter Server web management interface

• **9535 UDP/TCP** - mngsuite, LANDesk Management Suite Remote Control

• **9536 TCP/UDP** - laes-bf, IP Fabrics Surveillance buffering function

• **9600 UDP** - Omron FINS PLC communication

• **9675 TCP/UDP** - Spiceworks Desktop, IT Helpdesk Software

• **9695 UDP** - CCNx

• **9800 TCP/UDP** - WebDAV, WebCT e-learning portal

• **9875 TCP** - Club Penguin Disney online game for kids

• **9898 TCP/UDP** - MonkeyCom (citation needed)

• **9898 UDP** - MonkeyCom (citation needed)

• **9898 TCP** - Tripwire —File Integrity Monitoring Software

• **9987 UDP** - TeamSpeak 3 server default voice port

• **9996 TCP/UDP** - Ryan's App Trading Software, "The Palace" Virtual Reality Chat software

• **9997 TCP** - Splunk port for communication between forwarders and indexers

• **9998 TCP/UDP** - "The Palace" Virtual Reality Chat software

• **9999 TCP** - Hydranode —edonkey2000 TELNET control, Lantronix UDS-10/UDS100 RS-485 to Ethernet Converter TELNET control, Urchin Web Analytics

• **10000 TCP** - Webmin —Web-based administration tool for Unix-like systems, BackupExec, Ericsson Account Manager (avim)

• **10001 TCP** - Lantronix UDS-10/UDS100 RS-485 to Ethernet Converter default

• **10008 TCP/UDP** - Octopus Multiplexer, primary port for the CROMP protocol

This document lists various port numbers used by different software applications, operating systems, or protocols. Here's a summary of the entries provided:

• **Cross Fire**: A multiplayer online First Person Shooter, which is not officially documented but might use TCP (port 10009) and UDP (not specified).

• **Rexd daemon**: An unofficial service using Open Object Rexx (ooRexx), running on port 10010 with TCP.

• **rexd daemon**: Another unofficial service, this time related to AIX, NeXT, HPUX systems, also on port 10017 but not specifying the protocol used (likely TCP).

• **Zimbra smtp —to amavis and back**: An unofficial setup involving Zimbra SMTP MTA communicating with Amavisd via ports 10024 (TCP) and 10025 (TCP), possibly for email security or filtering.

• **Zabbix**: A network monitoring tool, available on agents (port 10050, TCP/UDP) and trapper (port 10051, TCP/UDP).

• **NMEA 0183 Navigational Data**: Uses port 10110 for transmission of NMEA 0183 sentences over either TCP or UDP.

• **NetIQ Endpoint, Qcheck, and VoIP Assessor**: Services provided by NetIQ, available on ports 10113 (TCP/UDP), 10114 (TCP/UDP), and 10115 (TCP/UDP) respectively.

• **Intuit Quickbooks client**: An unofficial connection using port 10200 (TCP), possibly for financial software communication.

• **f-protd and fpscand**: Virus scanning daemons from FRISK Software International, available on multiple ports (from 10200 to 10204) for Unix platforms.

• **VoiceIP-ACS UMP default device provisioning endpoint**: A service used in VoiceIP systems, accessible via TCP at port 10301 and SSL-encrypted at 10302.

• **Farming Simulator 2011 Default Server**: Uses UDP on port 10823.

• **Jungle Disk Monitor service**: Opens port 10891 with TCP, possibly for monitoring or data transfer from Jungle Disk services.

• **metasys (Johnson Controls Metasys java AC control environment)**: An unofficial protocol using port 11112, likely for controlling air conditioning systems through a Java interface.

• **ACR/NEMA Digital Imaging and Communications in Medicine (DICOM)**: Official standard on port 11155 with TCP.

These entries are mostly unverified or undocumented connections that might be used by specific software applications or require further investigation to confirm their exact usage. This text lists various server ports and protocols used by different services, applications, or games. The list includes:

• **DP**: Unofficial port number 11211, possibly related to a specific service or protocol (TCP/UDP).

• **Tunneling Protocol** (TCP): Unofficial port numbers for various servers including Savage:Battle for Newerth, Blood Quest Online, and more.

• **IPStor**: Server management communication using unofficial port number 12010 (TCP).

• **ElevateDB**: Default database port at 123 (unofficial), possibly related to a database service.

• **Axence nVision**: Ports 12012 and 12012 (both TCP) with unspecified numbers, likely used for a specific software or service.

• **Audition Online Dance Battle, Korea Server**: Multiple ports are listed including 12012 (TCP/UDP), 12031 (TCP), and 12035 (UDP).

• **GELF Protocol**: Unofficial port number 12201 (UDP).

• **Light Weight Access Point Protocol (LWAPP)**: Ports 12222 (UDP for control, RFC 5412) and 12223 (UDP for data, RFC 5412).

• **NetBus** and other remote administration tools: Mentioned with port numbers such as 12489 (TCP), 12975 (TCP/UDP for Hamachi VPN), and others.

• **BMC Software Control-M/Enterprise Manager**: Uses TCP ports 13195-13196, potentially for communication related to software management.

• **Cross Fire** is a multiplayer online First Person Shooter using unspecified TCP/UDP port numbers (unofficial).

The list also includes official and unofficial designations based on the context provided, which may include whether they are used by specific applications or protocols, their security characteristics (TCP vs UDP), and their status as per the text's author. The provided text lists various port numbers and their associated services, along with the company names they are affiliated with or the protocol types. Here is a summary of the information presented:

• **TCP/UDP Ports:**

• **13721** to **16300**: These ports are used by Symantec products including NetBackup (various versions), Network Utility—vnetd, VOPIED protocol, and Database—nbdb. They also include unofficial services like bprd, bpdbm, nomdb, and various others for different applications such as Kaspersky Network Agent, XPilot, Oracle WebCenter Content family of products, and shroudBNC.

• **14567** and **15567**: These ports are used by Battlefield Vietnam and mods, and Jeex.EU Artesia (direct client-to-db.service), respectively.

• **15000** to **15345**: This range includes unofficial services such as psyBNC, Wesnoth, hydap, Hypack, and others for XPilot, Oracle WebCenter Content family of products, and shroudBNC.

• **16080** and **16200** to **16250**: These ports are used by Mac OS X Server (Web service), various components of the Oracle WebCenter Content suite such as Imaging, Content Server, Inbound Refinery, Records Management, and others.

• **14900**: This port is associated with K3 SYSPRO and K3 Framework WCF Backbone, which are mentioned to be unofficial.

• **Protocol Types:**

• Most of the services listed use TCP or UDP protocols, except for some unofficial ones that do not specify a protocol explicitly but are noted as such in their descriptions (e.g., "Unofficial" indicates these services are unverified or not standardized).

These port numbers and services could be relevant to network configurations, security settings, firewall rules, or other networking considerations depending on the context in which they are used. This text lists various port numbers associated with different services and applications, including online backup systems, content management platforms, gaming servers, and a sound server. The ports are categorized as either unofficial or official, based on their designation. Some examples include:

• 16384 UDP for Iron Mountain Digital online backup.

• 16400 TCP for Oracle WebCenter Content (formerly known as Oracle Document Capture).

• 16567 UDP and TCP for Battlefield 2 and mods, as well as for Dropbox's LanSync Protocol (db-lsp).

• 18010 TCP for Super Dancer Online Extreme (SDO-X)—CiB Net Station Malaysia Server.

• 18104 TCP for RAD PDF Service.

• 18180 TCP for DART Reporting server.

• Multiple ports from 18200 to 18606 UDP and TCP for Audition Online Dance Battle, AsiaSoft Thailand/SEA Servers, and KAIZEN Brazil Server, with status and version checks or FAM database queries.

• 18300 to 18306 UDP and TCP for Audition Online Dance Battle, AsiaSoft SEA Server.

• 18333 TCP for Bitcoin testnet.

• 19000 and 19132 UDP and TCP for various Audition Online Dance Battles and Gkrellm server instances.

• 19150 UDP and TCP for Minecraft Pocket Edition LAN Server, indicating a mix of official and unofficial designations based on the context provided.

The provided text lists various network ports and their associated services, protocols, and software. Here's a summarized version of the data:

• **DminSecure Communication Agent** (Unofficial): Uses TCP and UDP.

• **KeyAuditor & KeyServer, Sassafras Software Inc.**: Tools like K2 - KeyShadow for managing software assets uses both TCP and UDP ports.

• **Google Talk**: Provides voice and video connections using TCP and UDP with specific port numbers <128>.

• **Belkin Network USB Hub** (Unofficial): Uses unspecified protocols but listed on UDP and TCP, possibly related to network management or device communication.

• **Ensim Control Panel** (Unofficial), **4D database SQL Communication**, **4D database Client Server Communication**, **4D database DB4D Communication** (all unofficial) are tools for managing software assets, using various TCP ports.

• **SCADA systems**: The DNP protocol is used between RTU's and IED's, with official versions at ports 20000 and a secure version (19999).

• **Usermin** (Unofficial): A web-based user tool accessed via TCP port 20000.

• Various games like **Killing Floor** and software tools such as **Precise TPM Listener Agent**, **Symantec i3 Web GUI server**, and **AMLFilter, Inc.** services have unofficial TCP or UDP ports in the range of 20xxx to 21xx,x.

These entries suggest a mix of official and unofficial uses for various network protocols, with some specific software tools listed that communicate over network ports using different transport layers (TCP/UDP). The text lists various port numbers and protocols used by different software, hardware components, or services. These include TCP/IP ports for communication protocols like Skype (default protocol), Teamware Office suite (standard client connection, client notifier, message transfer, MIME Connector, and Agent server connections), Xfire, collectd, BINKP, Tonido Directory Server, and various games such as Duke Nukem 3D, Minecraft, EVE Online, Quake, and War of No Return. Additionally, there are unofficial ports for camera systems (FLIR Systems Camera Resource Protocol) and software protection systems (CodeMeter, WIBU-SYSTEMS AG). Some ports like the one used by NetBeans IDE or the default port for collectd are not officially assigned but are used in specific applications. This summary lists a range of port numbers used by various software and services, including master servers, license servers, dedicated server ports, and other network communications. The ports are categorized by the software or service they support, such as QuakeWorld, Source engine, Mojiangka, MongoDB, Bitfighter, Starsiege: Tribes, Red Eclipse, Killing Floor, Jedi Knight: Jedi Academy, and Pokémon Netbat. Some of these ports use both TCP (Transmission Control Protocol) and UDP (User Datagram Protocol), while others are specific to certain software or game types. This summary provides a list of various port numbers and their associated protocols, along with brief descriptions. The ports range from unofficial to official, covering different types of software and services such as BitTorrent (30301), TCP (30564), Lantronix Discovery for serial-to-ethernet devices (30718), Back Orifice (remote administration tool) (31314), electric imp node<>server communication with TLS (31337), Crestron protocol (40123), and SafetyNET p Industrial Ethernet protocol (40000). Some ports are used for specific applications like game servers (e.g., WarZ on 34000, 34001), media streaming or games (e.g., TetriNET on 31457, 31458), and software-defined networking (SDN) related protocols (e.g., LM-MON on 32123). The text provides a list of port numbers and their usage in various network services, protocols, and applications. It includes standard ports for well-known services such as TCP (Transmission Control Protocol) and UDP (User Datagram Protocol). Some examples are the Crestron Control Port (41795), Murealm Client (

), TheòsMessenger (ports 43034, 43047, and 43594), RuneScape (ports 43595 and 44405), Mu Online Connect Server (44444), LightClaw.TeamServer (45824), and a server for the DAI family of client-server products (47001). Additionally, it mentions that ports above 49152 are used for custom or temporary purposes, including automatic allocation of ephemeral ports. The text also references RFCs and other standards documents to provide context on port usage in computer networking. The original content appears to be a list of references and links related to various internet protocols, standards, and technology documents. Here's a summary of the main points mentioned: 1. **HTTP and UDP**: The question "Does HTTP use UDP?" is not directly addressed in the provided text, but it mentions several RFCs which could relate to network protocols used for different purposes such as mail systems, file transfer (BFTP), registry information services (IRIS), and message submission for mail. 2. **Standards and Protocols**: The text lists various Internet-related standards and drafts including:

• **RFC 983**: This is not a known RFC but might be a typo or misprint, as it does not correspond to any documented IETF Request For Comments (RFCs).

• **RFC 1413**: Identifies the Identification Protocol.

• **RFC 1068**: Describes the Background File Transfer Program (BFTP).

• **RFC 1056**: PCMAIL: A Distributed Mail System for Personal Computers.

• **RFC 1504**: Appletalk Update-Based Routing Protocol.

• **RFC 1340**: Assigned Numbers.

• **RFC 4409**: Message Submission for Mail.

• **RFC 3620**: The TUNNEL Profile.

• **RFC 3632**: VeriSign Registry Registrar Protocol (RRP) Version 2.0.0.

• **IEEE Standards**: Media Management System (MMS) and Session Security, Authentication, Initialization Protocol (SSAIP).

• **Cisco IOS Software Releases**: New Features related to MPLS Label Distribution Protocol (LDP), Link Management Protocol (LMP), and other protocol updates.

3. **Patents and Protocols**: The document mentions a United States Patent 7286529, which is for "Discovery and tag space identifiers in a tag distribution protocol (TDP)". This suggests that there might be patenting activities related to specific protocols or standards within the internet framework. 4. **Updates and Archives**: There are references to updates on RFCs like DHCP Failover Protocol, which seems to have expired since it's mentioned as an Internet Draft dated September 2003. Some documents reference archives from previous years, indicating updates or changes in protocols over time. 5. **Technology Products**: The text also includes mentions of Cisco products with specific versions (like Cisco IOS Software Release 11.1CT and Releases 12.0 S), which might be referring to software releases that support new features related to the mentioned protocols and standards. 6. **References on RFCs**: Many references seem to point towards the importance of standardized internet protocols as outlined in various Request for Comments (RFCs) documents, which are maintained by the Internet Engineering Task Force (IETF). In summary, these points highlight a broad range of technological and protocol standards that form the backbone of modern internet communications. They include both established protocols like HTTP/HTTPS and DNS, as well as emerging or less commonly known standards used in specific applications or within certain organizations for internal network management and communication. This is a collection of various entries, each with a brief description or context related to specific topics such as network protocols, software configurations, and technical specifications for ports used in different systems and applications. Here's the summarized content: 1. **Certificate Management Protocol (CMP)**: A protocol related to managing certificates, possibly used in securing communications between devices. 2. **Setting up a socket policy file server**: This seems to be about configuring a server to handle socket policies for communication with other servers or clients. 3. **Port 903**: Described as necessary for configuring an external firewall to allow traffic related to ESX and VirtualCenter, which might involve managing virtual environments. 4. **RFCs (Request For Comments)**: Various RFC documents are mentioned:

• RFC 4707: A standard for something or another.

• RFC 6751: Another standard document possibly related to network protocols.

• RFC 5389 and RFC 5766: Standards for Session Traversal Utilities in NAT (STUN) and Traversal Using Relays around NAT (TURN), respectively, which are crucial for traversing firewalls and NATs in networking.

• RFC 5928: A resolution mechanism within the TURN framework.

5. **Firewall, Proxy, Router and Port Configuration for Blizzard Games**: Specific port configurations required by Blizzard Entertainment's gaming platforms. 6. **Brief descriptions of registered TCP and UDP ports**: General information about commonly used ports in network communications. 7. **Remote Procedure Call (RPC)**: A protocol that allows a computing system to use the facilities of another system, as if local, without having direct access to that other system’s processes or memory. 8. **Tuxánci game**: A multiplatform game inspired by Bulanci, distributed under the GNU General Public License. 9. **Philips - Contact en Ondersteuning**: Support information for Philips products, likely related to troubleshooting and technical support services. 10. **Service Name and Transport Protocol Port Number Registry**: A registry maintained by IANA that lists registered service names and their associated TCP or UDP port numbers. 11. **Getting Started with Rails**: Information on starting a web application development using the Ruby on Rails framework. 12. **devpi 0.9.2 documentation - Quickstart devpi-server**: Documentation for setting up a Python-based package repository server named devpi, used in software distribution and version management. 13. **CruiseControl.rb – Getting Started**: Instructions on how to get started with CruiseControl.rb, which is an open source continuous integration toolkit written in Ruby. 14. **Minger Email Address Verification Protocol (IETF Draft)**: A draft standard for verifying email addresses through a specific protocol. 15. **Referral Whois (RWhois) Protocol (RFC 2167)**: Information about a protocol used for querying whois data in a referral mechanism. These entries are primarily technical and relate to configuring software, setting up servers, and understanding network protocols and port usages. The text provides a variety of information related to different topics, including technical manuals, software details, and protocol specifications. Here's a summary of the main points: 1. **eMule Ports**: There is no specific content mentioned for "eMule Ports" in the provided text snippet. 2. **FlightGear Howto: Multiplayer** - This seems to be related to a manual or guide on how to set up multiplayer mode in FlightGear, but details are not provided. 3. **ARX Passersystem, Användarmanual**: No summary can be made as there is no content available about this topic. 4. **How can I troubleshoot my DroboShare?** - This refers to a support page on the DroboShare website, but without access to the full article, it's not possible to summarize its content accurately. 5. **Nmap Indication**: Graham Hill responded to a question about "telepathstart" and "telepathattack" listening on ports 5010 and 5011 of a Linux box, but no specific details or solutions are provided in the text snippet. 6. **Multiplayer - SRB2 Wiki**: This is a link to an old wiki page about multiplayer settings in the game SRB2, possibly providing information on how to configure it for use with others online. 7. **Symantec Intruder Alert product support** and **IBM Tivoli Netcool/Impact**: These are references to specific products from Symantec and IBM, but no details about what they do or how to troubleshoot them is provided in the snippet. 8. **RFCs (Request for Comments)**: The text mentions several RFCs which are technical standards for various internet protocols:

• RFC 2107: Ascend Tunnel Management Protocol

• RFC 3920: Extensible Messaging and Presence Protocol (XMPP)

• RFC 5415: Control And Provisioning of Wireless Access Points (CAPWAP)

• Various updates or versions like RFC 6120, which might be more recent documentation on the same topic.

9. **Various Protocols**: The text also mentions several protocols and their specifications without providing details about them. These include Binary Floor Control Protocol, VNC ports usage for TCP/IP connections, and others not specified in detail here. 10. **Software Manuals and Mini-Manuals**: Some links provide brief information or references to manuals:

• "Kega Fusion Mini-Manual" provides different versions from two sources, indicating multiple ways of accessing this manual's content.

• "Stratacache" is a generic mention without details.

• "Use IT Group - Bouwsoft - Groensoft" and "Port Numbers" are also mentioned generically without detailed contents.

11. **AMQP URI Specification**: Describes the specification for AMQP (Advanced Message Queuing Protocol) URIs used by RabbitMQ, a message broker software.

• The link provided is to RabbitMQ's official site, where you can find more details about how to use this specification in their platform.

In summary, these are references or mentions of various technical documents and protocols without detailed content summaries available within the text snippet itself. This text appears to be a list of references or citations, each with a brief description or title related to various topics such as software products, technical documentation, and support forums. Here is a summary of each entry: 1. "Enter-PSSession" - A command in PowerShell used for remote session management, possibly from Microsoft TechNet. 2. CVSup.org - An open-source version control system similar to CVS or SVN. 3. RFC 5424 - A request for comments document that defines the protocol for structured logging of observations of network events. 4. prd Technologies Ltd Billing & Rating Solutions - Description unclear, possibly related to billing and rating software solutions. 5. "SANE Unix man page" - Documentation on using SANE (a scanning application program interface) in a Unix environment from the SANE project website. 6. Datalogger Support Software - Generic term for support software used with dataloggers, not specified further. 7. Application-Oriented Networking – Cisco Systems - Description of networking concepts by Cisco Systems. 8. WebClientAuthenticatedSessionIDs - Possibly related to authentication sessions in web applications as mentioned in the FahClient forum. 9. Smartlaunch 4.1 Cyber Cafe Management Software Product Overview - An overview of a software used for managing cyber cafes, possibly from its official website or documentation. 10. "How to create a YSF Server, step by step guide" - A guide on setting up a YSF (Yet Another Soundboard Format) server, detailed in the YSFlight Headquarters forum. 11. Flex 3 – Adobe Flex 3 Help - Documentation from Adobe regarding their Flex 3 framework for building Rich Internet Applications. 12. Intel DMI (Desktop Management Interface) - Information on the Desktop Management Interface provided by Intel. 13. Freemake Video Downloader - A software tool to download videos from various online platforms, detailed in its official documentation or support pages. 14. "SuperContainer - 360Works Product Support Wiki" - Technical support information for a container management software named SuperContainer, maintained by 360Works. 15. Coral Content Distribution Network Wiki - FAQ section of the wiki, likely providing answers to common questions about the content distribution network. 16. VMware Communities: Change MUI ports? - Discussion on changing MUI (Microsoft User Interface) ports in VMware environments. 17. Apache Synapse - A description or documentation page for the Apache Synapse project, possibly from its official site or a community wiki. 18. Bitcoin Forum: Command Line and JSON-RPC - Section of the Bitcoin forum discussing command line operations and JSON-RPC interactions related to Bitcoin transactions. 19. "FAQ - Bitcoin" - A frequently asked questions page about Bitcoin cryptocurrency, hosted on the en.bitcoin.it website. 20. Wavestore Resources & Support - Technical support resources for a storage solution or product from Wavestore. 21. Apache Solr Tutorial - An educational guide on setting up and using Apache Solr, an enterprise search platform. 22. Play2 Documentation - Documentation for the Play Framework 2 (Play2), likely hosted by its official website or community wiki. 23. ETL Electronics - General reference to a company or product line specializing in electronics, possibly not detailed further. 24. "PS3™ | Using remote play (via the Internet)" and "Transferring data using Wi-Fi | PlayStation®Vita User's Guide" - Guides on how to use remote play functionality and transfer data via Wi-Fi for PS3 and PlayStation Vita devices, respectively, from their official support sites. 25. Tripwire Enterprise 8 - Documentation or information about the eighth version of Tripwire Enterprise, a security management tool. 26. Lantronix Discontinued Products / No Longer Supported - List of discontinued products from Lantronix with brief descriptions, likely from their official website or support portal. 27. Manual pages - F-PROT Antivirus Support - Unix - Technical documentation for using F-PROT antivirus on Unix systems, possibly from its developer's website or community wiki. 28. "network broadcast from bluestacks - Beacon-v1" - Discussion related to network broadcasting in Bluestacks emulator, found on the Getsatisfaction support forum. 29. Starting and Configuring the ElevateDB Server - Guide for setting up and configuring the ElevateDB server, likely hosted by its official website or community wiki. This content appears to be a collection of various references related to different topics, primarily focusing on server-related configurations and protocols. Here is a summary of the main points from the provided text: 1. **Server and Networking**: The text mentions several references to networking concepts, including "Networking introduction - collectd Wiki" which discusses a protocol used by Collectd for monitoring usage. There are also links to specific server setups like "Cube 2: Sauerbraten - Configuration" and "Server Setup - redeclipse", indicating discussions about configuring gaming servers or similar software. 2. **Port Configurations**: Several references discuss default port configurations, such as Mac OS X Server using ports 80 and 16080 for web services, which is relevant for network configuration and security settings. 3. **Protocols and Software Support**: The text includes discussions on specific protocols like APRS (Automatic Packet Reporting System) used in the 'APRS Wiki', and mentions WISCEBridge Debug Protocol. It also refers to configuring software features like allowing an internal XMPP client or server to connect to a Talk service, possibly related to communication protocols. 4. **Software Requirements**: "Immunet Protect 2.0 Requirements & Compatible Security Package List" outlines the system requirements for a security software product, and "Manually Configure Ports In Your Firewall - FAQ - Immunet Forum" provides guidance on firewall settings for that software. 5. **Software Lists and Registries**: The text includes references to specific software lists like Dhanalak #1 Multi-Branch Chain Accounting Inventory Management Software from Dhanalakshmi.org, indicating discussions about enterprise or specialized software applications. There's also a mention of FORUM on Flatcast.com which could be related to community forums. 6. **Technical Documentation and Standards**: The text includes references to MSDN (Microsoft Developer Network) for technical information on obtaining data from the local computer, and links to IANA (Internet Assigned Numbers Authority) procedures for managing service name and transport protocol port number registry, which are standards bodies related to internet protocols. 7. **External Links**: The text provides direct links to external resources where more detailed information or official lists can be found, such as the "Service Name and Transport Protocol Port Number Registry" managed by IANA. Overall, this content seems to be documentation or reference material intended for network administrators, system engineers, or technical support personnel who are responsible for configuring and maintaining servers, firewalls, and software configurations in a corporate or enterprise environment. The article discusses a list of TCP and UDP port numbers retrieved from Wikipedia's page on this topic. It mentions that the information is potentially dated as it was last updated in 2000, but the content includes articles with unsourced statements which might not be reliable. The page also contains external links that require cleanup to improve Wikipedia's quality standards and navigation tools for users like creating accounts, logging in, editing pages, searching, etc. Additionally, there are various language versions of the article available for translation and editing by contributors around the world.

Disclaimer:

The content in this post is for informational and educational purposes only. It may reference technologies, configurations, or products that are outdated or no longer supported. If there are any comments or feedback, kindly leave a message and will be responded.