bitlvl
EN

Port 9050 Tor SOCKS · TCP

Tor's SOCKS proxy: applications that should go through Tor are pointed at localhost:9050 (Tor Browser uses 9150).

Port9050
TransportTCP
ServiceTor SOCKS
CategoryProxies
Rangeregistered (1024–49151)
EncryptedYes, always (TLS or equivalent)
ExposureLoopback or the host's own network only

What runs on port 9050

Tor's SOCKS proxy: applications that should go through Tor are pointed at localhost:9050 (Tor Browser uses 9150). The control port on 9051 lets a program change circuits and must be password-protected. Anything beyond localhost is wrong; a reachable Tor SOCKS port is a free anonymous proxy for others.

Software that uses it: Tor · torsocks, proxychains · Privoxy (chained on 8118)

Should port 9050 be open?

Loopback or the host's own network only. The service should listen on 127.0.0.1 (or a Unix socket) and be reached by a reverse proxy or by the application on the same host. If it answers on a public address, that is a misconfiguration.

Check port 9050

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

# from another machine: is it reachable?
nc -zv host 9050
nmap -p 9050 host
curl -v telnet://host:9050      # 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 9050

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

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

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

# firewalld
sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=10.0.0.0/8 port port=9050 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 9050" 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 9050 TCP or UDP?

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

Is port 9050 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 9050 is open?

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

Can Tor SOCKS 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.