SSL Ports Explained: Examples & How to Choose
- Average speed (km/h)
- km/h
- Result
- Time (min)
- 50 min
- You entered
- Distance (km)
- 10 km
- You entered
SSL ports are network endpoints that use the Secure Sockets Layer (SSL) or its successor Transport Layer Security (TLS) to encrypt traffic between a client and a server. You enter a port number along with the server address (e.g., imap.example.com:993) to establish a secure connection, and the port tells both sides which protocol and encryption method to use. Below we explain the most common SSL port numbers, how they work, and how to pick the right one for your use case.
Formula
The calculator above isn’t about SSL ports—it’s a generic example of how a simple formula can be embedded. For SSL, there is no single formula; instead, the port number is a fixed value defined by the Internet Assigned Numbers Authority (IANA) or by convention. The most common are:
- 443 – HTTPS (HTTP over TLS)
- 993 – IMAPS (IMAP over TLS)
- 995 – POP3S (POP3 over TLS)
- 465 – SMTPS (SMTP over TLS, implicit)
- 636 – LDAPS (LDAP over TLS)
- 989/990 – FTPS (FTP over TLS, data/control)
Each port is a 16-bit number (0–65535) that identifies a specific service on a host. When you connect to a server, you specify the IP address or hostname and the port, like smtp.example.com:465.
Worked Example
Suppose you’re configuring an email client to connect to your provider’s IMAP server. The default port for IMAP over TLS is 993. You would enter:
- Server:
imap.example.com - Port:
993 - Encryption: SSL/TLS (or “explicit TLS�)
The client then establishes a TCP connection to port 993 and immediately starts a TLS handshake before sending any credentials. If you used port 143 (plain IMAP) and then issued a STARTTLS command, the connection would start unencrypted and upgrade later—a different approach.
How SSL Ports Work
When a client connects to an SSL port, it performs a TLS handshake:
- The client sends a ClientHello message with supported cipher suites.
- The server responds with a ServerHello, its certificate, and a key exchange.
- Both sides derive session keys and begin encrypted communication.
This handshake happens on the same TCP connection, which is why the port number matters—it tells the client that the server expects TLS from the start (implicit TLS) rather than upgrading later (STARTTLS).
How to Choose the Right SSL Port
Choosing a port depends on the protocol and whether you want implicit or explicit TLS:
- HTTPS (443) – For web traffic, always use 443. It’s universally supported and often the only port allowed through firewalls.
- Email (465, 993, 995) – Use 465 for SMTP submission with implicit TLS, 993 for IMAP, and 995 for POP3. These are the standard secure ports.
- LDAP (636) – For directory services, use 636 for LDAPS. Alternatively, you can use 389 with STARTTLS, but 636 is simpler.
- FTP (990, 989) – For FTP over TLS, use 990 for the control channel and 989 for data. However, FTPS is often replaced by SFTP (which uses SSH, port 22).
If you’re running a custom service, you can choose any unused port (e.g., 8443 for HTTPS alt) but be aware that non-standard ports may be blocked by firewalls or require client configuration.
Common Problems and Misconceptions
One common misconception is that SSL and TLS are different things—in practice, SSL is the older name, and TLS is the modern protocol. Port numbers haven’t changed, but the encryption handshake uses TLS 1.2 or 1.3 today.
Another issue is confusing implicit TLS with STARTTLS. On port 465, the connection is encrypted from the first byte. On port 587 (SMTP submission), you might use STARTTLS, which begins as plaintext and then upgrades. If you connect to a STARTTLS port without issuing the command, your credentials could be sent in clear text.
Firewalls often block non-standard ports. If you’re having trouble connecting, check that the port is open in both directions. Also, some ISPs block port 25 (SMTP) to reduce spam, but 465 or 587 are usually allowed.
Comparing SSL Ports with Alternatives
For web, HTTPS (443) is the only secure option. For file transfer, you can use FTPS (990/989) or SFTP (22). SFTP uses SSH and is often easier to configure because it only needs one port. For email, IMAPS (993) and POP3S (995) are standard, but some services offer webmail via HTTPS only.
In general, using a dedicated SSL port (implicit TLS) is more secure than STARTTLS because there’s no window where data is sent unencrypted. However, some legacy systems only support STARTTLS, so you may need to use port 143 or 110 with explicit TLS.
Safety and Best Practices
Always use the latest TLS version (1.2 or 1.3) and avoid SSLv3, which is deprecated due to vulnerabilities like POODLE. When configuring a server, disable weak ciphers and enable HSTS for HTTPS. For email, use strong authentication and never allow plaintext authentication on any port.
If you’re a developer, use well-known libraries like OpenSSL or built-in TLS support in your language to handle the handshake. Never implement your own encryption.
Frequently Asked Questions
What is the default SSL port for HTTPS?
Port 443. It’s the standard for HTTPS and is used by virtually all secure websites.
Is port 465 still used for SMTP?
Yes, port 465 is used for SMTP with implicit TLS. Although it was initially deprecated, it was re-registered for SMTPS and is widely supported by email providers.
What’s the difference between SSL and TLS?
SSL is the older protocol, and TLS is its successor. TLS 1.0, 1.1, 1.2, and 1.3 are the current versions. Many people still say “SSL� when they mean TLS.
Can I use any port for SSL?
Technically yes, but you must configure both client and server to use the same port. However, using standard ports (443, 993, etc.) ensures compatibility and avoids firewall issues.
Why does my firewall block port 443?
Some networks restrict outbound traffic. If port 443 is blocked, you may need to use a VPN or a different port, but that’s rare. Check your firewall settings.
What is the port for SFTP?
SFTP (SSH File Transfer Protocol) uses port 22 by default. It’s not an SSL port, but it provides secure file transfer via SSH.
Related
Formula used
in t | Time (min) | min | 50 | 0 in d | Distance (km) | km | 10 | 0 out pace | Average pace (min/km) | min/km | t / d | 2 out speed | Average speed (km/h) | km/h | d / (t / 60) | 2
Each line is one input (in, sel, list) or one result (out: label, unit, formula, decimals). How the calculators work
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.