Service:
Protocol:
TCPPort:
465Used for:
Secure SMTP for encrypted email submissionWhy It’s Open
Port 465 is used for SMTP over SSL/TLS (SMTPS), providing encrypted email submission from mail clients to mail servers. Originally designated for SMTP with SSL, it was briefly deprecated in favor of STARTTLS on port 587 but remains widely used for legacy systems and specific email security requirements.
Mail servers expose this port to allow secure email submission, particularly for legacy email clients that don’t support modern STARTTLS implementations on port 587.
Common Risks
- SSL/TLS Vulnerabilities
Outdated encryption protocols may be exploitable - Certificate Issues
Invalid or expired certificates compromise security - Spam Relay
Misconfigured servers can be used for spam distribution - Credential Theft
Despite encryption, weak authentication can be exploited - Version Exposure
Server banners may reveal software versions
Want to save time on reporting?
Let PentestPad generate, track, and export your reports - automatically.

Enumeration & Testing
Check if it’s open:
nmap -sT -p 465Test SSL/TLS:
openssl s_client -connect :465Check certificate:
sslscan :465What to Look For
| Checkpoint | What it means |
|---|---|
| Weak SSL/TLS versions | Vulnerable to known cryptographic attacks |
| Self-signed certificates | Potential for man-in-the-middle attacks |
| Open relay configuration | Server may be abused for spam |
| Authentication not required | Missing access controls |
Mitigation
- Modern TLS Only
Disable older SSL/TLS versions - Strong Certificates
Use valid, properly signed certificates - Authentication Required
Implement strong SMTP authentication - Rate Limiting
Prevent abuse through connection and sending limits - Regular Updates
Keep SMTP software and security patches current - Real World Example
In 2021, attackers exploited misconfigured SMTPS servers using outdated TLS 1.0, allowing them to intercept encrypted email traffic and harvest credentials from multiple organizations.
TL;DR
- Port 465 = SMTPS (Secure SMTP)
- Legacy encrypted email submission
- Requires current TLS versions
- Need strong authentication
Known CVEs and Exploits
- CVE-2021-28937 – TLS renegotiation vulnerability in mail servers
- CVE-2020-13925 – Authentication bypass in SMTP implementations
- CVE-2019-16508 – Buffer overflow in SMTPS handling
- Multiple tools exist for SMTPS security testing.