| Port | 30303 |
|---|---|
| Transport | TCP and UDP |
| Service | Ethereum P2P |
| Category | Peer-to-peer |
| Range | registered (1024–49151) |
| Encrypted | Yes, always (TLS or equivalent) |
| Exposure | Designed to face the internet |
Port 30303 Ethereum P2P · TCP and UDP
Ethereum execution-client peer-to-peer port (Geth, Nethermind, Besu): TCP for peer connections and UDP for node discovery.
What runs on port 30303
Ethereum execution-client peer-to-peer port (Geth, Nethermind, Besu): TCP for peer connections and UDP for node discovery. A node needs it reachable to get good peers; the JSON-RPC API (8545) must not be exposed.
Software that uses it: Geth · Nethermind · Besu · Erigon
Should port 30303 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.
- Consensus clients use 9000 (Lighthouse, Nimbus) or 13000 (Prysm) for their own P2P.
Check port 30303
# on the host: is anything listening, and which process? ss -ltnp 'sport = :30303' ss -lunp 'sport = :30303' sudo lsof -i :30303 # from another machine: is it reachable? nc -zv host 30303 nmap -p 30303 host nc -zuv host 30303 sudo nmap -sU -p 30303 host curl -v telnet://host:30303 # 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 30303
# ufw (Ubuntu/Debian)
sudo ufw allow from 10.0.0.0/8 to any port 30303 proto tcp
sudo ufw allow from 10.0.0.0/8 to any port 30303 proto udp
sudo ufw deny 30303/tcp
sudo ufw deny 30303/udp
# nftables
nft add rule inet filter input ip saddr 10.0.0.0/8 meta l4proto { tcp, udp } th dport 30303 accept
nft add rule inet filter input meta l4proto { tcp, udp } th dport 30303 drop
# iptables (legacy)
iptables -A INPUT -p tcp --dport 30303 -s 10.0.0.0/8 -j ACCEPT
iptables -A INPUT -p tcp --dport 30303 -j DROP
iptables -A INPUT -p udp --dport 30303 -s 10.0.0.0/8 -j ACCEPT
iptables -A INPUT -p udp --dport 30303 -j DROP
# firewalld
sudo firewall-cmd --permanent --add-rich-rule='rule family=ipv4 source address=10.0.0.0/8 port port=30303 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 30303" 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 30303 TCP or UDP?
Both. Ethereum P2P uses TCP and UDP on 30303: see the notes above for when each is used.
Is port 30303 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 30303 is open?
On the server, ss -ltnp (or -lunp for UDP) shows whether something listens on 30303 and which process. From another machine, nc -zv host 30303 or nmap -p 30303 host tests reachability. "Open" in a scan means something answered; a firewall usually makes the port filtered (no answer) rather than closed (RST).
Can Ethereum P2P 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.