CyberKit

Network Ports

TCP and UDP ports that matter for DFIR, each cited with a confidence level.

The TCP and UDP ports worth recognizing in traffic. Open a port for what runs there, why it matters, what to look for and the ATT&CK techniques that use it.

Before you read the table

  • 0 to 1023 are system ports. On Unix, binding one needs privilege, so an unprivileged listener there is worth a look.
  • 1024 to 49151 are registered ports, and nothing stops any program from using one unregistered.
  • 49152 to 65535 are ephemeral. The client's OS picks one per connection, so there is nothing to look up.

63 rows.

Network ports
PortProtocolNameWhat it is
80tcpHTTP (Hypertext Transfer Protocol)HTTP is the application-layer protocol underlying the World Wide Web: a stateless request/response protocol where a client requests a resource by method, path, and headers, and a server returns a status code, headers, and a body. Port 80/tcp is its IANA-registered default, governed by RFC 9110 (HTTP Semantics). Traffic on 80 is plaintext by default, with no confidentiality or integrity protection unless something above the transport adds it.
443tcpHTTPS (HTTP over TLS/SSL)HTTPS wraps HTTP inside a TLS session, so the TCP handshake is followed by a TLS handshake (certificate exchange, cipher negotiation) before any HTTP request or response is exchanged. Port 443/tcp is IANA's registered default and is referenced from RFC 9110 as the default port for the https URI scheme. It now carries the overwhelming majority of web traffic, including HTTP/2 and, via QUIC over UDP on the same port number, HTTP/3.
8080tcpHTTP Alternate (http-alt)Port 8080/tcp carries no protocol of its own: it is registered with IANA simply as http-alt, a designated alternate for port 80, and in practice is used by a wide range of unrelated services: web application servers running without root privileges (which cannot bind to the privileged port 80), reverse proxies, development servers, and device/appliance admin UIs. What is actually spoken on 8080 is ordinary HTTP (or occasionally HTTPS); there is no way to know which without inspecting the traffic.
8443tcpHTTPS Alternate (registered as PCsync HTTPS)Port 8443/tcp's IANA registration is literally pcsync-https, registered to Laplink Software for its PCsync file-synchronization product's HTTPS interface, a use that is essentially obsolete today. In current practice 8443 functions the way 8080 does for HTTP: a widely-adopted, unofficial convention as the alternate/non-privileged port for HTTPS, defaulted to by many Java application servers and by network device or appliance admin consoles.
3128tcpSquid HTTP Proxy (de facto; registered as ndl-aas)Port 3128/tcp is the long-standing default listening port for the Squid caching web proxy, adopted in the 1990s and still Squid's out-of-the-box http_port default today. Its actual IANA registration, however, is for an unrelated service, ndl-aas (an Active API Server port); 3128 became the proxy convention purely through Squid's own defaults and widespread adoption, never a formal IANA proxy assignment.
1080tcpSOCKS ProxySOCKS is a generic circuit-level proxy protocol that relays arbitrary TCP (and, in SOCKS5, UDP) connections on behalf of a client without understanding the application protocol being tunneled, unlike an HTTP proxy, which works only for HTTP(S). Port 1080/tcp is IANA's registered default, and the current version, SOCKS5, is defined in RFC 1928, with RFC 1929 covering username/password authentication.
25tcpSMTP (Simple Mail Transfer Protocol)SMTP is the protocol mail servers use to relay email between each other (MTA-to-MTA) and, historically, from a client to a server. Port 25/tcp is its IANA-registered default, governed by RFC 5321. Modern deployments largely restrict port 25 to server-to-server relay and inbound mail delivery, pushing client mail submission to dedicated ports (465/587) instead.
465tcpSMTPS (Message Submission over implicit TLS)Port 465/tcp carries SMTP wrapped in TLS from the very start of the connection, implicit TLS, with no STARTTLS negotiation, providing the same message-submission function as port 587 but encrypted before any SMTP command is exchanged. Its history is unusually tangled: 465 was informally used for SMTPS since the 1990s but was never officially sanctioned for that purpose, with its formal IANA registrations covering unrelated services (urd on TCP, igmpv3lite on UDP); RFC 8314 in 2018 finally gave the de facto SMTPS usage an official registration, submissions, formalizing 465 as a recommended implicit-TLS submission port alongside 587.
587tcpSMTP Submission (STARTTLS)Port 587/tcp is the IANA-registered message submission port, defined in RFC 6409, specifically for mail clients authenticating and submitting outbound mail to their provider's server, distinct from port 25's server-to-server relay role. Unlike 465, a 587 connection starts in plaintext and upgrades to TLS mid-session via the STARTTLS command, so an observer sees the initial handshake before encryption begins.
110tcpPOP3 (Post Office Protocol v3)POP3 lets a mail client download messages from a server-side mailbox, traditionally removing them from the server after retrieval, a download-and-delete model in contrast to IMAP's server-resident, multi-device synchronization model. Port 110/tcp is its IANA-registered default, defined in RFC 1939. In its unencrypted form, POP3 authenticates with a plaintext USER/PASS exchange by default.
995tcpPOP3S (POP3 over TLS/SSL)Port 995/tcp is POP3 wrapped in implicit TLS from connection start, the encrypted counterpart to port 110. It is IANA-registered as pop3s, with RFC 8314 formalizing implicit TLS as the recommended approach for mail retrieval protocols.
143tcpIMAP (Internet Message Access Protocol)IMAP synchronizes a mail client's view of a mailbox with a server-resident copy, supporting multiple folders and flags with simultaneous access from multiple devices, unlike POP3's simple download model. Port 143/tcp is its IANA-registered default; the current protocol version is IMAP4rev2, defined in RFC 9051, which supersedes the long-standing IMAP4rev1 in RFC 3501. Like POP3, plaintext IMAP negotiates STARTTLS to upgrade to encryption, or can be used entirely unencrypted if the client allows it.
993tcpIMAPS (IMAP over TLS/SSL)Port 993/tcp is IMAP wrapped in implicit TLS from connection start, registered with IANA as imaps and governed by the same IMAP RFCs (3501/9051) plus RFC 8314 for the implicit-TLS convention.
53tcp/udpDNS (Domain Name System)DNS resolves human-readable names to IP addresses, and vice versa, plus many other record types, and is defined across RFC 1034 (concepts) and RFC 1035 (implementation and wire format). It genuinely runs over both UDP and TCP on port 53: UDP handles the vast majority of ordinary queries for low overhead, while TCP is required whenever a response exceeds the practical UDP size limit, and always for zone transfers (AXFR, defined in RFC 5936) between authoritative name servers.
389tcp/udpLDAP (Lightweight Directory Access Protocol)LDAP is the protocol clients use to query and modify a directory service, in a Windows environment, Active Directory's own interface for users, groups, computers, group policy, and schema. Port 389/tcp is its IANA-registered default and is defined by RFC 4511 (part of the RFC 4510 series). It also has a genuine UDP role, connectionless LDAP (CLDAP), which Active Directory domain controllers use to answer lightweight LDAP ping queries from the Windows DC Locator service before a client opens a full TCP LDAP session. Standard LDAP traffic on 389 is unencrypted unless upgraded via STARTTLS.
636tcpLDAPS (LDAP over TLS/SSL)Port 636/tcp is LDAP wrapped in implicit TLS from connection start, the same directory query and modify functionality as 389, but encrypted before any LDAP operation occurs. It predates the standardized StartTLS extension (RFC 4513) and is not itself part of the core LDAP RFC series; it is a widely-deployed de facto convention that Microsoft and other directory vendors continue to support, and which Active Directory hardening guidance increasingly pushes as the default over unsigned plaintext LDAP.
3268tcpGlobal Catalog LDAP (Microsoft Active Directory)Port 3268/tcp is Microsoft's extension of LDAP for Active Directory's Global Catalog: a partial, read-only, forest-wide replica of every domain's directory data, hosted on domain controllers designated as Global Catalog servers. Querying 3268 instead of 389 lets a client search across every domain in the forest in a single query, at the cost of only a subset of each object's attributes being available. It is registered with IANA as msft-gc but is not defined by any IETF RFC; it is Active Directory-specific.
3269tcpGlobal Catalog LDAP over TLS/SSLPort 3269/tcp is the encrypted counterpart to 3268: forest-wide Global Catalog queries wrapped in implicit TLS. It is registered with IANA as msft-gc-ssl and shares the same Microsoft-specific, non-RFC status as 3268.
88tcp/udpKerberosKerberos is the network authentication protocol Active Directory and other Kerberos realms use to issue and validate tickets proving a principal's identity without repeatedly transmitting a password: a client obtains a Ticket-Granting Ticket (TGT) from the Key Distribution Center's Authentication Service, then uses it to request per-service Ticket-Granting Service (TGS) tickets. Port 88 is IANA-registered and defined by RFC 4120 (The Kerberos Network Authentication Service V5), and it genuinely runs over both UDP and TCP: RFC 4120 requires implementations to support both, with UDP preferred for small messages but TCP required whenever a message exceeds the practical UDP datagram size, which is routine in Active Directory once the Privilege Attribute Certificate is included.
464tcp/udpKerberos Change/Set Password (kpasswd)Port 464 carries the Kerberos password-change protocol, allowing a principal to change their own password, or, with sufficient privilege, set another principal's password, without a full administrative directory operation. In an Active Directory environment this is what runs when a domain user changes their password interactively. It is defined by RFC 3244, Microsoft Windows 2000 Kerberos Change Password and Set Password Protocols, and, confirmed via the IANA registry, runs over both TCP and UDP.
137udpNetBIOS Name ServiceNetBIOS Name Service handles registration and resolution of NetBIOS names, the legacy host naming scheme that predates DNS on Windows networks, over UDP broadcast or to a WINS server. It is defined by RFC 1001 (concepts) and RFC 1002 (detailed wire specification) as part of the NetBIOS-over-TCP/IP suite, and while IANA registers the service name on both TCP and UDP, the Name Service function itself operates over UDP in practice, per its RFC 1002 design.
138udpNetBIOS Datagram ServiceNetBIOS Datagram Service provides connectionless datagram delivery between NetBIOS names, including the broadcast mechanisms historically used for browser-service announcements and elections on Windows networks, as part of the same NBT suite defined in RFC 1001/1002. Like the Name Service, IANA registers it on both TCP and UDP, but it operates over UDP in practice.
139tcpNetBIOS Session ServiceNetBIOS Session Service provides the connection-oriented session layer NetBIOS applications use to exchange data. Historically this was how SMB file and print sharing operated, carried inside a NetBIOS session on 139, before Windows 2000 introduced direct-hosted SMB over TCP port 445 without a NetBIOS session wrapper. It is defined by RFC 1001/1002 and, per the IANA registry, formally listed on both TCP and UDP, though the session service itself is inherently connection-oriented and runs over TCP.
20tcpFTP (File Transfer Protocol): DataThe secondary channel an FTP session uses to move actual file bytes, separate from the command channel on port 21. In active mode the FTP server initiates this connection back to the client's specified port using the PORT command; in passive mode (the default in virtually all modern clients), the server instead opens a random high port and the client connects out to it, so raw port-20 traffic is actually the less common case today.
21tcpFTP (File Transfer Protocol): ControlThe command channel of an FTP session: the client authenticates with USER/PASS and issues directory-listing and transfer commands, which the server acknowledges with numeric status replies, per RFC 959. This channel also negotiates the companion data channel (port 20 in active mode, or a server-announced high port in passive mode) that carries the actual file bytes.
22tcpSSH (Secure Shell) / SFTP / SCPAn encrypted remote-login and command-execution protocol (RFC 4251/4253) that also carries file transfer as SFTP and SCP subsystems over the same authenticated, encrypted session, plus arbitrary TCP port forwarding/tunneling. It is the de facto standard for administering Linux/Unix hosts and network appliances, and is increasingly available on Windows via OpenSSH.
23tcpTelnetA plaintext remote-terminal protocol (RFC 854) that predates SSH by roughly two decades. It opens an interactive command-line session on the remote host with no encryption and, in its base form, no integrity protection at all.
445tcpSMB (Server Message Block) / CIFSWindows' (and Samba's) native file, printer, and named-pipe sharing protocol. Port 445 is "direct-hosted" SMB running straight over TCP without the legacy NetBIOS session service (ports 137-139) that older SMB required. Beyond plain file shares, SMB named pipes also carry a range of other Windows RPC-based administrative protocols such as service control, remote registry, and SAM access.
3389tcp/udpRDP (Remote Desktop Protocol)Microsoft's remote graphical desktop protocol (MS-RDPBCGR), historically a pure TCP protocol but, since RDP 8.0, able to negotiate an additional UDP transport (MS-RDPEUDP) for the same session, used to improve responsiveness for graphics, input, and audio when available, with TCP always present as the base/fallback channel. IANA registers ms-wbt-server on both TCP and UDP port 3389, and Microsoft's own documentation lists "TCP and UDP 3389" as the standard RDP port.
5900tcpVNC (Virtual Network Computing) / RFBA cross-platform remote-framebuffer protocol (RFC 6143) implemented by numerous independent products (RealVNC, TightVNC, UltraVNC, TigerVNC) rather than being tied to one vendor or OS. Port 5900 corresponds to display :0; additional displays on the same host stack upward (5901 for :1, and so on).
2049tcp/udpNFS (Network File System)Unix/Linux's native network file-sharing protocol, originally from Sun Microsystems. Older versions (NFSv2/RFC 1094, NFSv3/RFC 1813) could run over either TCP or UDP and relied on the separate rpcbind/portmapper service (port 111) to locate the actual mount/NFS daemon ports; NFSv4 (RFC 7530, and RFC 8881 for minor version 1) consolidated everything onto the single well-known port 2049 and effectively requires TCP.
111tcp/udpRPCbind (Portmapper) / ONC RPCThe ONC RPC (Sun RPC) directory service: it maps an RPC program number (such as the NFS mount/nfsd services) to the actual dynamic port that service is listening on, functionally the Unix/Linux counterpart to the Windows MSRPC endpoint mapper on port 135. Current implementations use the rpcbind protocol (RFC 1833); the older, TCP/UDP-specific predecessor was the Port Mapper protocol.
135tcpMSRPC Endpoint Mapper (DCE/RPC)Windows' RPC locator service: a client connects to port 135 and asks which dynamic high port (typically 49152-65535 on modern Windows) a specific RPC interface (a WMI provider, a DCOM activation request, a remote service-control call) is actually listening on, then opens a second connection to that port to do the real work. DCOM is itself built on top of this same MSRPC transport.
5985tcpWinRM (Windows Remote Management): HTTPMicrosoft's implementation of the WS-Management (WS-Man) standard; it is the transport underneath PowerShell Remoting (Enter-PSSession, Invoke-Command) and WMI-over-WinRM. Port 5985 is the default plaintext-HTTP listener. The SOAP payload itself is typically still protected at the message level by Kerberos/NTLM in a default domain configuration, but the outer HTTP channel is not TLS.
5986tcpWinRM (Windows Remote Management): HTTPSThe same WS-Management/PowerShell Remoting service as port 5985, bound instead to a TLS-wrapped HTTPS listener backed by a certificate. It is the encrypted counterpart, commonly required when remoting across an untrusted network segment or to a non-domain-joined/workgroup host where Kerberos isn't available.
161udpSNMP (Simple Network Management Protocol)The standard protocol for polling and configuring network infrastructure (routers, switches, printers, UPS units, and similar devices) using GET/GETNEXT/GETBULK to read values and SET to write configuration. SNMPv1/v2c authenticate with a plaintext "community string"; SNMPv3 (RFC 3411 and its companion RFCs) adds real user-based authentication and encryption.
162udpSNMP TrapThe reverse-direction channel from SNMP polling: instead of being queried, a managed device pushes an unsolicited notification (link down, temperature threshold, cold/warm start, and similar events) to a management station listening on port 162.
514udpSyslogThe standard log-transport protocol: a device or host sends log messages (originally the loosely structured BSD format, later formalized by RFC 5424) to a central collector. RFC 5426 defines the plain UDP transport, which is connectionless, unauthenticated, and unencrypted by design.
6514tcpSyslog over TLSRFC 5425's TLS transport mapping for syslog: it wraps the same RFC 5424-structured messages in a TLS session, adding the confidentiality, integrity, and (with mutual TLS) sender authentication that plain UDP/514 lacks. IANA separately registers port 6514 for a DTLS-wrapped variant (RFC 6012) as well, though the TCP/TLS mapping is the one actually seen in real-world deployments.
1433tcpMicrosoft SQL ServerThe default port for Microsoft SQL Server's default database engine instance, carrying the Tabular Data Stream (TDS) protocol that clients use to authenticate and run queries. IANA registers the service name ms-sql-s to port 1433 for both TCP and UDP, but in real deployments the database engine itself listens on TCP; the companion UDP service on port 1434 is the separate SQL Server Browser/Resolution service that helps clients locate named instances using dynamic ports, not the query channel itself.
1521tcpOracle Database (Oracle Net Listener)The conventional default port for the Oracle Net Listener, the process that brokers incoming client connections and hands them off to an Oracle Database instance over Oracle's TNS (Transparent Network Substrate) protocol. Notably, IANA's registry does not actually assign 1521 to Oracle. It's registered to 'ncube-lm' (nCube License Manager); Oracle's own officially IANA-registered ports are 2483/2484 (plain/TLS), but 1521 remains the overwhelmingly dominant real-world default carried forward from decades of Oracle deployment convention.
3306tcpMySQL / MariaDBThe IANA-registered default port for the MySQL Client/Server binary protocol, used identically by MariaDB (a MySQL-compatible fork). Clients authenticate and exchange queries/result sets with the server over this single persistent TCP connection; local connections on the same host commonly use a Unix socket instead, bypassing the network port entirely.
5432tcpPostgreSQLThe IANA-registered default port for the PostgreSQL database server's connection listener, carrying PostgreSQL's own frontend/backend wire protocol. The port choice dates back to the original Berkeley POSTGRES project and has stayed the de facto standard through every subsequent PostgreSQL release.
27017tcpMongoDBThe default port for mongod (and mongos router) instances, carrying MongoDB's own binary wire protocol used by drivers and the mongosh shell to issue commands and queries. IANA registers this port to MongoDB Inc. specifically for TCP; the UDP variant is reserved/unused.
6379tcpRedisThe default port for the Redis in-memory key-value store's connection listener, carrying the RESP (REdis Serialization Protocol) wire protocol. IANA registers this port to Redis for TCP only; classic Redis ships with no authentication by default (a requirepass directive must be set explicitly), and older versions had no ACL system at all.
9200tcpElasticsearch (HTTP REST API)The default port for Elasticsearch's HTTP interface, over which clients send REST API calls (indexing, search, cluster management), distinct from port 9300, the transport interface nodes use to talk to each other within a cluster. Notably, IANA's registry does not assign 9200 to Elasticsearch at all. It's officially registered to 'wap-wsp' (WAP connectionless session service), a legacy mobile-carrier protocol; 9200 is purely an Elastic-chosen application default, not an IANA assignment, in the same way 1521 is Oracle's de facto (not official) port.
67udpDHCP Server (BOOTPS)The port a DHCP (Dynamic Host Configuration Protocol) server listens on for client requests, inherited from the older BOOTP protocol it extends (the IANA service name is still 'bootps'). The server uses it to receive DISCOVER/REQUEST broadcasts and hand out IP leases plus configuration options (gateway, DNS, and (for network-boot setups), a TFTP server address).
68udpDHCP Client (BOOTPC)The port a DHCP client listens on to receive OFFER and ACK replies from a DHCP server, the client-side counterpart to server port 67 (again inheriting the BOOTP-era 'bootpc' service name from IANA). Every DHCP-configured host briefly uses this port during lease acquisition and renewal.
69udpTFTP (Trivial File Transfer Protocol)A minimal, connectionless file-transfer protocol with no authentication and no directory listing: a client sends a read or write request and the server streams the file in fixed-size blocks. It's the standard mechanism for PXE network-boot images and for backing up/restoring configuration on network devices (routers, switches, VoIP phones).
123udpNTP (Network Time Protocol)The port NTP servers and clients use to exchange time-synchronization messages, keeping system clocks aligned across a network. NTP is fundamentally UDP-based per its governing RFC; IANA also carries a rarely-used TCP registration for the same service name, but essentially all real-world NTP traffic is UDP.
179tcpBGP (Border Gateway Protocol)The port BGP routers (typically ISP/carrier and large enterprise edge routers) use to establish TCP peering sessions and exchange routing information between autonomous systems. IANA's registry additionally lists UDP and SCTP entries for the 'bgp' service name, but the protocol itself is defined and overwhelmingly deployed over TCP, which BGP relies on for reliable, ordered delivery of routing updates.
500udpIKE / ISAKMP (IPsec Key Exchange)The port used by IKE (Internet Key Exchange, built on the ISAKMP framework) to negotiate and establish the Security Associations that IPsec VPNs use to authenticate peers and derive encryption keys: the control-plane handshake that happens before any encrypted ESP traffic flows. IANA also lists a TCP registration for the same service name, That covers a documented but far less common fallback: RFC 8229/9329 define encapsulating IKE and IPsec entirely inside a single TCP connection when UDP negotiation isn't possible.
4500udpIPsec NAT-Traversal (NAT-T)The port IKE/IPsec peers switch to when a NAT device is detected between them, encapsulating both the IKE negotiation and the resulting ESP-protected traffic inside UDP so it can survive NAT translation (plain ESP has no port number for NAT to rewrite, which otherwise breaks it). IANA lists both a TCP and UDP registration for 'ipsec-nat-t' on 4500, but the mechanism it names (UDP encapsulation to solve the NAT/ESP incompatibility) is inherently UDP-based per RFC 3948/RFC 7296.
1701udpL2TP (Layer 2 Tunneling Protocol)The port L2TP uses to tunnel PPP frames between a client and server, most commonly paired with IPsec for encryption (L2TP/IPsec) since L2TP itself provides no confidentiality. IANA lists both TCP and UDP registrations for 'l2tp' on 1701, but the protocol as deployed (and as most operating systems' built-in VPN clients implement it) runs over UDP.
1723tcpPPTP (Point-to-Point Tunneling Protocol)The port PPTP uses for its control connection, which negotiates and manages the tunnel; the actual tunneled PPP data travels separately over GRE (IP protocol 47), not over 1723 itself, so a firewall blocking only TCP 1723 doesn't fully stop a PPTP tunnel, and an analyst investigating one needs to look at GRE traffic between the same two hosts as well.
5060tcp/udpSIP (Session Initiation Protocol)The signaling port for SIP, the protocol that sets up, modifies, and tears down VoIP calls and other real-time sessions (the actual voice/media then flows separately over RTP on a negotiated port range). IANA registers 5060 to SIP for TCP, UDP, and SCTP alike. It's a genuinely dual/multi-transport service, with UDP historically the most common default for signaling and TCP used especially where SIP-over-TLS (SIPS, typically port 5061) or larger message sizes are involved.
4444tcpMetasploit Framework default handler4444 is the long-standing conventional default LPORT for Metasploit's exploit/multi/handler and for reverse_tcp-family payloads (including Meterpreter), not a port Metasploit invented or was assigned specifically for this purpose (IANA does register TCP/UDP 4444 to a legacy, largely disused service, krb524, the Kerberos v5-to-v4 ticket translator, unrelated to Metasploit), just the value Metasploit and its documentation have used as the out-of-the-box example for years, to the point that SANS Internet Storm Center's own port reference explicitly labels 4444 as the 'Metasploit default listener.' It is trivially changed with a single LPORT option, and penetration testers and red teams routinely do.
31337udpBack Orifice (historical)31337 (read as 'eleet'/'elite' in leetspeak) is the historically documented default UDP port for the original Back Orifice, the remote-administration-tool-turned-Windows-backdoor released by the Cult of the Dead Cow in 1998, one of the most widely publicized early Remote Access Trojans; it communicated over UDP by default (its 2000 successor, BO2K, switched to TCP 54320/UDP 54321). Trend Micro's own trojan-port reference table lists 31337 against Back Orifice by name, and SANS Internet Storm Center covered the port's history and significance in a dedicated Cyber Security Awareness Month write-up.
12345tcpNetBus (historical)12345 (often paired with 12346) is the historically documented default listening port for NetBus, a graphical Windows remote-access trojan written by Carl-Fredrik Neikter and released around 1998: a close contemporary of Back Orifice with similar remote-control capability (file access, registry manipulation, process control). Malaysia's national CERT (MyCERT) and Juniper Networks' threat-signature database both document the 12345/12346 default.
1337tcp"Leet" port (generic backdoor/CTF culture)1337 (leetspeak for 'elite,' the same wordplay behind 31337) is IANA-registered for an unrelated legitimate service (menandmice-dns, the Men & Mice DNS Server Controller protocol) and has no single dominant malware family, but it does have a genuine documented history: SANS Internet Storm Center's own port reference lists both that legitimate menandmice-dns registration and the historical Shadyshell trojan against TCP 1337 (with the original Shadyshell source archived on Packet Storm), and the number's hacker-culture cachet has made it a recurring, informal choice for CTF challenges, bind-shell exercises, and various ad hoc backdoors ever since.
6667tcpIRC (historical botnet C2 channel)6667 is the conventional default port for IRC (Internet Relay Chat) (a legitimate, decades-old chat protocol in its own right) that became, through the 2000s in particular, one of the most common command-and-control channels for botnets. Malware families like Agobot/Phatbot and Kaiten/Tsunami connected outbound to an attacker-run IRC server/channel to receive commands, a pattern SANS Internet Storm Center documented in a dedicated write-up on whether IRC traffic 'is evil,' and which the nmap project still ships a dedicated NSE script (irc-botnet-channels) to help detect.
9001tcpTor ORPort (relay traffic)9001 is the port the Tor Project's own sample relay configuration (torrc.sample.in) and relay-setup documentation use for the ORPort: the port a Tor relay listens on to carry onion-routed traffic between other relays in the network. It's a documented convention rather than a hardcoded requirement; a relay operator can bind ORPort to any port (443 is also commonly recommended precisely because it blends in on restrictive networks), so 9001 specifically is a strong lead, not a guarantee, when triaging Tor-related traffic.
9030tcpTor DirPort (directory service)9030 is the port the Tor Project's own sample relay configuration documents for the optional DirPort, which serves network directory information (the list of known relays and their status) to clients and other relays. Not every relay runs a DirPort (it's an optional role on top of the mandatory ORPort), and like 9001 it's a documented convention rather than an enforced default.

Related

All references