Port 25/tcp: SMTP (Simple Mail Transfer Protocol)
Category: Email. Range: well-known. Status: iana registered.
What runs here
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.
Why it matters
Port 25 carries mail between domains, so its logs, including the SMTP conversation, envelope from/to, and Received header chain, are foundational for tracing a phishing email's true origin and delivery path. It is also a classic outbound-abuse vector: a compromised host or misconfigured relay sending unauthorized outbound mail on 25 is one of the most common signs of a mail server or open relay being abused, which is why many ISPs and cloud providers block outbound 25 by default.
Where you see it
Legitimately: MTA-to-MTA mail relay and inbound mail delivery to a domain's MX host. Anomalously/maliciously: an open relay or compromised mail server sending unsolicited outbound spam or phishing, a compromised host attempting direct-to-MX SMTP that bypasses an organization's outbound mail gateway, or SMTP used as a simple data-exfiltration channel.
What to look for
| Signal | What it means |
|---|---|
| Received header chain vs. envelope sender | Reconstructing the hop-by-hop Received chain and comparing the SMTP envelope sender to the visible From header is the standard way to spot spoofing or a compromised relay in the path. |
| HELO/EHLO identity vs. source IP | A HELO hostname that does not resolve to, or match, the connecting IP is a common spam and spoofing tell. |
Related ports
ATT&CK techniques
- T1071.003: T1071.003