bitlvl
EN

Port 88 Kerberos · TCP and UDP

Kerberos: the ticket-based authentication protocol behind Active Directory and MIT/Heimdal realms.

Port88
TransportTCP and UDP
ServiceKerberos — Authentication (Active Directory)
CategoryAuthentication and directories
Rangewell-known (0–1023, needs root to bind on Unix)
EncryptedYes, always (TLS or equivalent)
ExposurePrivate network or VPN only

What runs on port 88

Kerberos: the ticket-based authentication protocol behind Active Directory and MIT/Heimdal realms. Clients talk to the KDC on 88 to obtain tickets (AS and TGS exchanges), then present tickets to services. It needs accurate clocks (a skew of more than five minutes breaks it) and working DNS, including the reverse zone.

Software that uses it: Active Directory domain controllers · MIT Kerberos · Heimdal · FreeIPA · Samba AD

Should port 88 be open?

Private network or VPN only. Nothing good comes from this port being reachable from the internet. Keep it on an internal network, reach it over a VPN or an SSH tunnel, and firewall it from everything that does not need it.

Check port 88

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

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

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

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

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

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

Both. Kerberos uses TCP and UDP on 88: Authentication (Active Directory).

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

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

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