Port 8200 (HashiCorp Vault)

Vault API and UI. 8201 is used for cluster traffic.

Registered (user) port, 1024-49151 TCP Network infrastructure Expose only to trusted sources

What port 8200 is used for

Vault API and UI. 8201 is used for cluster traffic.

Security: should port 8200 be open?

Expose only to trusted sources. Vault holds your secrets; restrict network access to the clients that need it, use TLS, and never run a dev-mode server (in-memory, root token printed) outside a laptop.

IANA assignment

Service nameProtoDescriptionAssigneeReference

trivnet1 TCP TRIVNET Saar Wilf -

trivnet1 UDP TRIVNET Saar Wilf -

Check what is listening on port 8200

Linux: is anything listening on TCP 8200?

sudo ss -tlnp 'sport = :8200'

Linux / macOS: which process owns the port

sudo lsof -nP -i :8200

Older Linux / BSD (net-tools)

sudo netstat -tlnp | grep ':8200 '

Windows (Command Prompt)

netstat -ano | findstr :8200

Windows (PowerShell)

Get-NetTCPConnection -LocalPort 8200 -State Listen | Select LocalAddress,OwningProcess

Test it from outside

From another machine

nc -vz -w 5 HOST 8200

From Windows

Test-NetConnection HOST -Port 8200

Allow only trusted sources on port 8200 in the firewall

Replace 203.0.113.10 with the address or network you trust. With ufw, make sure the default incoming policy is deny.

ufw (one trusted source)

sudo ufw allow from 203.0.113.10 to any port 8200 proto tcp

iptables

sudo iptables -A INPUT -p tcp --dport 8200 -s 203.0.113.10 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport 8200 -j DROP

nftables

sudo nft add rule inet filter input ip saddr 203.0.113.10 tcp dport 8200 accept
sudo nft add rule inet filter input tcp dport 8200 drop

Windows Firewall

New-NetFirewallRule -DisplayName 'TCP 8200 trusted' -Direction Inbound -Protocol TCP -LocalPort 8200 -RemoteAddress 203.0.113.10 -Action Allow

All port numbers · Open port checker
Assignment data: IANA port number registry (public domain), retrieved 2026-11-10.