CyberKit

Network ports

Port 465/tcp: SMTPS (Message Submission over implicit TLS)

Category: Email. Range: well-known. Status: iana registered.

What runs here

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.

Why it matters

Recognizing 465 tells an analyst this is authenticated client mail submission, not server-to-server relay, so the relevant identity is the authenticating account rather than a domain's MX infrastructure. Because TLS is established immediately, any 465 connection that is not cleanly encrypted from the first bytes is itself anomalous. Threat actors that obtain mailbox credentials frequently use 465/587 directly, rather than a webmail UI, for large-scale automated sending in phishing-from-a-real-account or BEC campaigns.

Where you see it

Legitimately: mail clients submitting outbound mail with implicit TLS. Anomalously/maliciously: automated mass-mail sending from a compromised mailbox credential (BEC, phishing from a real account), or credential-stuffing/brute-force attempts against a mail submission endpoint.

What to look for

Indicators
SignalWhat it means
Authentication attempts and failuresRepeated AUTH failures against a submission endpoint in a short window is classic password-spraying or credential-stuffing behavior targeting mailboxes.

Related ports

  • 25/tcp: SMTP (Simple Mail Transfer Protocol)
  • 587/tcp: SMTP Submission (STARTTLS)
  • 995/tcp: POP3S (POP3 over TLS/SSL)
  • 993/tcp: IMAPS (IMAP over TLS/SSL)

ATT&CK techniques

Sources