Registered · Cross-platform

9150 Tor Browser SOCKS

TCP Unofficial
UDP
SCTP
DCCP

What it is

Tor Browser bundled SOCKS proxy.

When / why

Anonymized browsing.

Protocol status detail

TransportStatusMeaning
TCP Unofficial Not assigned by IANA, but standardized, specified, or widely used on this port.
UDP Not applicable for this transport.
SCTP Not applicable for this transport.
DCCP Not applicable for this transport.

Port range

Registered (1024–49151). Assigned by IANA on request; usable without elevated privileges on most systems.

Browse all ports →

Firewall rules for port 9150

Copy-ready inbound rules for the active transports. Replace every <source> placeholder with the specific host, subnet, or CIDR that should reach this port.

ufw

sudo ufw allow proto tcp from <source> to any port 9150

Allow TCP 9150 (Tor Browser SOCKS). Replace <source> with the network/host that should reach it.

firewalld

sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<source>" port port="9150" protocol="tcp" accept'

Allow TCP 9150 (Tor Browser SOCKS) from <source>. Run 'firewall-cmd --reload' afterwards.

nftables

nft add rule inet filter input ip saddr <source> tcp dport 9150 accept

Allow TCP 9150 (Tor Browser SOCKS). Assumes table 'inet filter' with an 'input' chain.

iptables

sudo iptables -A INPUT -p tcp -s <source> --dport 9150 -j ACCEPT

Allow TCP 9150 (Tor Browser SOCKS). Persist with iptables-save/netfilter-persistent.

Azure NSG

az network nsg rule create -g <resource-group> --nsg-name <nsg> -n Allow-torbrowsersocks-9150 --priority 1000 --access Allow --direction Inbound --protocol TCP --source-address-prefixes <source> --destination-port-ranges 9150

Inbound rule for 9150 (Tor Browser SOCKS). Set <source> to a CIDR; lower priority number = higher precedence.

AWS Security Group

aws ec2 authorize-security-group-ingress --group-id <sg-id> --ip-permissions IpProtocol=tcp,FromPort=9150,ToPort=9150,IpRanges="[{CidrIp=<source-cidr>}]"

Inbound TCP 9150 (Tor Browser SOCKS). Replace <source-cidr> (e.g. 10.0.0.0/16).

GCP firewall

gcloud compute firewall-rules create allow-torbrowsersocks-9150 --direction=INGRESS --action=ALLOW --rules=tcp:9150 --source-ranges=<source-cidr> --network=<network>

Ingress rule for 9150 (Tor Browser SOCKS). Scope with --source-ranges and optionally --target-tags.

Windows netsh

netsh advfirewall firewall add rule name="Allow Tor Browser SOCKS 9150/TCP" dir=in action=allow protocol=TCP localport=9150 remoteip=<source>

Inbound TCP 9150 (Tor Browser SOCKS). Set remoteip to a host/subnet; 'any' is discouraged.

Windows PowerShell

New-NetFirewallRule -DisplayName "Allow Tor Browser SOCKS 9150/TCP" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 9150 -RemoteAddress <source>

Inbound TCP 9150 (Tor Browser SOCKS). Replace <source> with a host or subnet.

Rules are generated only for transports marked active for this port. They default to an inbound allow with an explicit source placeholder — never any. Review direction, scope, and rule precedence before applying in production.