bitlvl
EN

Port 563 NNTPS · TCP

NNTPS: NNTP over TLS. What Usenet providers actually use today.

Port563
TransportTCP
ServiceNNTPS — Usenet over TLS
CategoryLegacy services
Rangewell-known (0–1023, needs root to bind on Unix)
EncryptedYes, always (TLS or equivalent)
ExposureDesigned to face the internet

What runs on port 563

NNTPS: NNTP over TLS. What Usenet providers actually use today.

Software that uses it: INN · commercial Usenet providers

Should port 563 be open?

Designed to face the internet. This port exists to be reachable from anywhere, so the usual question is not whether to open it but how the service behind it is configured and patched.

Check port 563

# on the host: is anything listening, and which process?
ss -ltnp 'sport = :563'
sudo lsof -i :563

# from another machine: is it reachable?
nc -zv host 563
nmap -p 563 host
curl -v telnet://host:563      # raw TCP connect test, Ctrl-C to leave

A port that answers from the internet when it should not is the finding; nmap from a machine outside your network (or a VPS) is the honest test, because scans from inside the LAN pass the firewall you are trying to verify.

Allow or block port 563

# ufw (Ubuntu/Debian)
sudo ufw allow from 10.0.0.0/8 to any port 563 proto tcp
sudo ufw deny 563/tcp

# nftables
nft add rule inet filter input ip saddr 10.0.0.0/8 tcp dport 563 accept
nft add rule inet filter input tcp dport 563 drop

# iptables (legacy)
iptables -A INPUT -p tcp --dport 563 -s 10.0.0.0/8 -j ACCEPT
iptables -A INPUT -p tcp --dport 563 -j DROP

# firewalld
sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=10.0.0.0/8 port port=563 protocol=tcp accept'

Replace 10.0.0.0/8 with the networks that need access. Allowing by source address is the rule that matters; "allow 563" with no source is just "open".

Related ports

Part of the port number reference. Ports are 16-bit numbers; see also the subnet calculator and the packet decoder, which shows ports inside TCP and UDP headers.

Questions

Is port 563 TCP or UDP?

TCP. NNTPS is a connection-oriented protocol; there is no UDP service on 563 by default (a scanner reporting UDP 563 open is usually seeing a filtered port).

Is port 563 encrypted?

Yes, always (TLS or equivalent). The port number does not make it safe by itself: certificate validation, authentication and patching still decide.

How do I check whether port 563 is open?

On the server, ss -ltnp (or -lunp for UDP) shows whether something listens on 563 and which process. From another machine, nc -zv host 563 or nmap -p 563 host tests reachability. "Open" in a scan means something answered; a firewall usually makes the port filtered (no answer) rather than closed (RST).

Can NNTPS run on a different port?

Yes; the number is a convention, not a requirement. Changing it reduces log noise from scanners but does not add security, and every client, firewall rule and monitoring check then needs the new number. Keep the default unless you have a concrete reason.