bitlvl
EN

Port 7 echo · TCP and UDP

The echo service sends back whatever it receives. It was a debugging aid for early TCP/IP stacks and is a classic amplification and loop vector (echo pointed at chargen), which is why every modern system ships with it disabled.

Port7
TransportTCP and UDP
Serviceecho
CategoryLegacy services
Rangewell-known (0–1023, needs root to bind on Unix)
EncryptedNot applicable
ExposureDisable it

What runs on port 7

The echo service sends back whatever it receives. It was a debugging aid for early TCP/IP stacks and is a classic amplification and loop vector (echo pointed at chargen), which is why every modern system ships with it disabled.

Software that uses it: inetd/xinetd "simple services" · Windows Simple TCP/IP Services

Should port 7 be open?

Disable it. This is a legacy or insecure protocol. The recommendation is not to firewall it but to turn the service off and use the modern replacement.

Check port 7

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

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

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

# nftables
nft add rule inet filter input ip saddr 10.0.0.0/8 meta l4proto { tcp, udp } th dport 7 accept
nft add rule inet filter input meta l4proto { tcp, udp } th dport 7 drop

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

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

Both. echo uses TCP and UDP on 7: see the notes above for when each is used.

Is port 7 encrypted?

Not applicable. The protocol carries no application data worth encrypting, or encryption is handled at another layer.

How do I check whether port 7 is open?

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

Can echo 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.