Port 119NNTP

Network News Transfer Protocol (NNTP) facilitates the distribution, retrieval, and posting of Usenet articles, which function similarly to online forum messages across a distributed network of news servers. Primarily designed for reading and managing discussion groups, NNTP streamlines communication by enabling fast article transfers, centralized indexing, and efficient management of a vast amount of newsgroup content..

transport
tcp

single transport

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
2/10

safe

lookups
9,955

rank 474 of 993 · top 48%

Technical Details

what runs on :119

Overview:

Network News Transfer Protocol (NNTP) operates over TCP port 119 and is the standard protocol used for reading and posting Usenet articles, also known as newsgroup postings. NNTP was standardized in RFC 977 and later updated by RFC 3977, facilitating the transfer and synchronization of articles between clients and servers, as well as between peer servers.

Functionality:

NNTP allows clients to connect to a Usenet server to browse newsgroups, download articles, or post new articles. Clients typically authenticate then issue commands such as GROUP for selecting newsgroups, ARTICLE to fetch posts, or POST to submit content. It supports bulk article transfer between servers, known as peering, through streaming commands, which optimize and automate article distribution across the network.

Protocol Details:

Operating solely over TCP, NNTP establishes persistent connections that enable interactive reading and dynamic retrieval of articles. Sessions use a simple text-based command-response format, akin to SMTP or POP3, which facilitates both automated server processes and manual debugging. While it supports authentication (e.g., via AUTHINFO USER/PASS), traditional NNTP lacks built-in encryption, relying on plaintext communication unless paired with external security layers such as TLS over port 563 (NNTPS).

Security Information

exposure of :119

risk score

2/ 10safe

routine exposure. this port is rarely the way in on its own — keep it patched and logged and move on.

web services averages 3.9 across 112 ports — this one sits 1.9 below.

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

every listening transport is another surface to filter at the edge

security overview

Common Vulnerabilities:

  • Plaintext communication: Since standard NNTP transmits data without encryption, it is susceptible to eavesdropping and interception of credentials or content.
  • Open relay configuration: Misconfigured servers may act as open relays, facilitating spam or unauthorized submissions.
  • Abuse by attackers: Servers can be exploited to distribute malicious content or used as a vector for social engineering through malicious or misleading articles.

Common Mitigations:

  • Encrypted connections: Migrate to NNTP over TLS (often on port 563) or employ STARTTLS extensions to secure communication.
  • Access control: Require strong authentication and restrict posting permissions, limiting exposure to abuse.
  • Server hardening: Disable open relay features, enforce rate limiting, and monitor server logs for suspicious activity.
  • Content filtering: Implement automated scanning of articles for malware or inappropriate content to reduce the impact of social engineering or malware dissemination.

the 8 most looked-up other ports in web services — 112 ports carry that label.

risk mix of the 8 listed

  • safe13%
  • caution88%

0 of 8 encrypted