whatportis.com
suggest an edit →

Port 24Private Mail

Port 24 is traditionally assigned for private mail systems, serving as a dedicated communication channel distinct from standard email protocols. This port is seldom used in modern network infrastructures but may still be encountered in legacy or proprietary messaging environments. Its primary function involves facilitating the transfer and exchange of email-like messages within closed or controlled networks..

inEmailNetwork Services
transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
4/10

caution

lookups
11,707

rank 341 of 993 · top 34%

Technical Details

what runs on :24

Port 24 was historically reserved to support private mail systems, offering organizations the ability to separate internal messaging services from those traversing the Internet. Unlike SMTP (port 25) — the dominant protocol for email transfer — port 24 could be utilized by customized or proprietary mail applications that needed an isolated communication pathway. These setups allowed organizations to maintain an extra level of control and customization over internal communication processes.

The use of port 24 enabled the implementation of specialized mail handling features, including internal routing, custom message processing workflows, and integration with enterprise software suites tailored to unique business requirements. Because it was not standardized like SMTP or IMAP, implementations varied widely and were often tightly coupled with organizational infrastructure.

Over time, the prevalence of private mail protocols on port 24 diminished, with most systems consolidating onto standardized, more secure protocols. However, in niche scenarios or legacy networks, port 24 may still be in use, primarily for backward compatibility or supporting proprietary systems that have not transitioned to newer technologies.

Security Information

exposure of :24

risk score

4/ 10caution

worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.

email averages 3.9 across 42 ports — this one sits 0.1 above.

in transit

cleartext

credentials and payloads are readable by anyone on path

assignment

official

registered with iana for this service — scanners fingerprint it by number

reachable over

tcp · udp

udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite

security overview

Common Vulnerabilities:

  • Because private mail systems often lack standardized security features, services running on port 24 might be susceptible to plaintext credential interception, unauthorized access, or impersonation attacks.
  • Legacy implementations typically do not support modern encryption or authentication methods, increasing the risk of data leaks and man-in-the-middle attacks.
  • Port 24 may be targeted by attackers scanning for misconfigured or forgotten services, which could provide a foothold into internal networks.

Common Mitigations:

  • Disable port 24 if no private mail systems are actively used, reducing the network attack surface.
  • Implement robust access controls and network segmentation to limit exposure if the port must remain open.
  • Employ encryption or tunnel communication through secure protocols like SSH or VPN to protect message content.
  • Regularly audit legacy services utilizing this port and prioritize migration toward secure, standardized email protocols.
  • Monitor network activity for unusual traffic patterns on port 24 that may indicate reconnaissance or exploitation attempts.

Related Ports

all 42 in email →

the 8 most looked-up other ports in email — 42 ports carry that label.

portservicerisk
:143IMAPcaution
:995POP3Scaution
:109POP2caution
:2096cPanel SSL Webmailsafe
:110POP3caution
:993IMAPScaution
:1352Lotus Notes RPCcaution
:7025Zimbra LMTPcaution

risk mix of the 8 listed

  • safe13%
  • caution88%

3 of 8 encrypted