Online admissions open for the SEO, PHP web development and networking & cybersecurity courses. Enquire for the next batch.

Common Network Ports Cheat Sheet

Cheat sheet · 65 entries Updated By the SkillNewton team

This cheat sheet lists the port numbers you meet most often in networking exams, firewall rules and server troubleshooting, grouped by what the service does. Each row shows the port and transport protocol, then the service. Numbers follow the IANA registry and widely documented software defaults. Remember that a default is only a convention: services can run on other ports, so confirm with ss -tulpn or the service configuration.

How to use this cheat sheet

  1. Learn the core ports first. Start with 22, 25, 53, 80, 443, 3389 and the email ports. They appear in almost every exam and firewall rule set.
  2. Note the transport protocol. A rule for 53/TCP does not cover 53/UDP. Check which protocol a service uses before opening a port.
  3. Check what is really listening. Run ss -tulpn on Linux or netstat -ano on Windows to see the ports open on your own machine.
  4. Open only what you need. Use the list to build firewall rules that allow required services and block the rest, especially database and remote-access ports.

Web

80/TCPHTTP – unencrypted web traffic. Usually only redirects to HTTPS today.
443/TCPHTTPS – HTTP over TLS (HTTP/1.1 and HTTP/2).
443/UDPHTTP/3 – HTTP over QUIC.
8080/TCPHTTP alternate – common for development servers, proxies and application servers.
8443/TCPWidely used alternative HTTPS port for admin panels and application servers (a convention, not the IANA name).
3128/TCPSquid HTTP proxy – default listening port.

Email

25/TCPSMTP – mail transfer between servers. Many ISPs and cloud providers block outbound 25 from ordinary hosts.
587/TCPSMTP submission – mail clients sending mail, upgraded to TLS with STARTTLS and authenticated.
465/TCPSMTPS submission – mail clients sending over implicit TLS (RFC 8314).
110/TCPPOP3 – download mail from a mailbox (unencrypted).
995/TCPPOP3S – POP3 over TLS.
143/TCPIMAP – access and sync mail kept on the server (unencrypted or STARTTLS).
993/TCPIMAPS – IMAP over TLS.

File transfer and remote access

20/TCPFTP data – used for transfers in active mode.
21/TCPFTP control – commands and login, sent in clear text.
22/TCPSSH – encrypted remote shell; also carries SFTP and SCP.
23/TCPTelnet – unencrypted remote shell. Replace with SSH.
69/UDPTFTP – simple file transfer with no login; used for network boot and device configs.
445/TCPSMB – Windows file and printer sharing. Never expose to the internet.
137–139NetBIOS – name service (137/UDP), datagram (138/UDP) and session service (139/TCP), used by older SMB.
2049/TCPNFS – Network File System shares (UDP also possible on older versions).
3389/TCPRDP – Windows Remote Desktop (also uses 3389/UDP). Put it behind a VPN or gateway.
5900/TCPVNC – remote desktop (first display; 5901 for the second, and so on).
873/TCPrsync daemon – used when rsync runs as a service rather than over SSH.

Name and directory services

53/UDPDNS – standard queries and responses.
53/TCPDNS – zone transfers and large responses.
853/TCPDNS over TLS (DoT) – encrypted DNS queries.
67/UDPDHCP server (BOOTP server) – receives client requests.
68/UDPDHCP client (BOOTP client) – receives offers and acknowledgements.
546/UDP and 547/UDPDHCPv6 – client (546) and server (547).
5353/UDPmDNS – multicast DNS for local name discovery (.local names, printers, casting).
88/TCP and UDPKerberos – authentication in Active Directory and other realms.
389/TCPLDAP – directory queries (also 389/UDP for some lookups).
636/TCPLDAPS – LDAP over TLS.
3268/TCPGlobal Catalog – forest-wide LDAP searches in Active Directory (3269/TCP over TLS).

Network management, time and VPN

123/UDPNTP – time synchronisation.
161/UDPSNMP – manager polls an agent on a device.
162/UDPSNMP trap – device sends alerts to the manager.
514/UDPSyslog – traditional log forwarding (unencrypted, no delivery guarantee).
6514/TCPSyslog over TLS.
1812/UDPRADIUS authentication (1813/UDP for accounting).
49/TCPTACACS+ – device administration authentication, authorisation and accounting.
179/TCPBGP – routing information exchange between routers.
500/UDPIKE / ISAKMP – sets up IPsec VPN tunnels.
4500/UDPIPsec NAT traversal – IKE and ESP traffic wrapped in UDP when NAT is in the path.
1194/UDPOpenVPN – default port (TCP can also be used).
51820/UDPWireGuard – commonly documented default listening port (configurable).

Databases and caches

3306/TCPMySQL and MariaDB.
5432/TCPPostgreSQL.
1433/TCPMicrosoft SQL Server default instance.
1521/TCPOracle Database listener.
27017/TCPMongoDB.
6379/TCPRedis.
11211/TCPMemcached.
9200/TCPElasticsearch and OpenSearch HTTP API (9300/TCP for node-to-node traffic).
# Databases should listen only where needed. Check on Linux:
sudo ss -tulpn | grep -E ':(3306|5432|6379|27017)'
# 127.0.0.1:3306  -> local only (good for a single server)
# 0.0.0.0:3306    -> all interfaces: restrict with a firewall

Other common services

5060/UDP and TCPSIP – VoIP call signalling.
5061/TCPSIP over TLS.
3478/UDPSTUN and TURN – NAT traversal for voice and video calls.
631/TCPIPP – Internet Printing Protocol (CUPS on Linux).
9100/TCPRaw printing (often called JetDirect or AppSocket).
1883/TCPMQTT – lightweight IoT messaging.
8883/TCPMQTT over TLS.
5985/TCPWinRM over HTTP – PowerShell remoting (5986/TCP over HTTPS).
520/UDPRIP – Routing Information Protocol (RIPng for IPv6 uses 521/UDP).
6443/TCPKubernetes API server – common default.

Frequently asked questions

What are well-known, registered and dynamic ports?

IANA divides the 65,536 port numbers into well-known ports (0 to 1023), registered ports (1024 to 49151) and dynamic or private ports (49152 to 65535). Clients usually pick a temporary source port from the dynamic range.

Which port does ping use?

None. Ping uses ICMP echo request and echo reply messages, and ICMP has types and codes rather than ports. Firewalls allow or block it by ICMP type.

Does changing the SSH port from 22 make a server secure?

It reduces automated login noise in logs but is not a security control on its own. Use key-based authentication, disable password and root logins and restrict access with a firewall.

Why does DNS use both UDP and TCP?

Most queries use UDP because it is fast. TCP is used for zone transfers, for responses too large for UDP, and by encrypted DNS over TLS on port 853.

Want to Learn This Properly?

The Networking & Cybersecurity: Foundation & Practical Implementation (Online) turns resources like this into practised skills, with projects on real websites.

WhatsApp Call Us Now

Free counselling

Send an Enquiry

Tell us which course you are interested in. We reply by email or phone with the next batch and how to enrol.

We reply by email or phone within working hours. No spam.