Port 56 XNS-AUTH
Port 56 is the IANA-assigned xns-auth port for XNS Authentication (TCP / UDP).
What is port 56 used for?
Port 56 is assigned to xns-auth and uses TCP / UDP. The IANA registry describes the service as “XNS Authentication”. It sits in the well-known range, which operating systems reserve for core network services, so software expects it at this number by default.
Ports are the transport-layer address a service listens on. A client that wants to reach xns-auth connects to port 56. A TCP connection is refused when nothing is listening, while a UDP request simply goes unanswered. That is why a port conflict appears whenever two processes try to bind the same number.
Use the commands below to confirm whether port 56 is actually in use before you change firewall rules. Blocking the port stops new inbound traffic at the firewall, but it does not stop a local process from listening, and it does not remove the service from the machine.
Browse all Authentication and access ports
Source: IANA Service Name and Transport Protocol Port Number Registry. Registered assignee: [Susie_Armstrong].
Check and block port 56
Copy-ready commands for the protocols assigned to this port. Run the check first, then block only what should not be reachable.
Check on Linux
sudo ss -tlpn 'sport = :56'
sudo ss -ulpn 'sport = :56'Check on Windows
Get-NetTCPConnection -LocalPort 56 -State Listen -ErrorAction SilentlyContinue
Get-NetUDPEndpoint -LocalPort 56 -ErrorAction SilentlyContinueBlock with UFW
sudo ufw deny 56/tcp
sudo ufw deny 56/udpBlock with iptables
sudo iptables -A INPUT -p tcp --dport 56 -j DROP
sudo iptables -A INPUT -p udp --dport 56 -j DROPThese commands are examples for a typical host. Check the listener before you change firewall rules, and persist iptables rules with iptables-save or netfilter-persistent. On Windows, use Windows Defender Firewall or New-NetFirewallRule for persistent blocks. The iptables rules here cover IPv4; mirror them with ip6tables if IPv6 is enabled.
Is port 56 safe to expose?
This port is not on our curated list of services with a widely exploited profile. Exposure is only safe when the listening service is intended, patched and protected by a firewall. Keep the listening service patched and remove it if unused. A default-deny firewall policy with explicit allow rules is still the safest baseline.
Where port 56 is usually used
Most traffic on port 56 falls into these scenarios. The demo below is a safe way to confirm the listener before you change anything.
- Network devices authenticating users through a central service.
- Wi-Fi, VPN and remote-access gateways enforcing access policy.
- Accounting and session logs used for audits.
Probe the auth service
Authentication protocols are sensitive to shared secrets and source addresses, so test from an authorised client.
nc -vz 127.0.0.1 56Common problems with port 56
Connection refused or timed out
Refused usually means the host is reachable but nothing is listening on port 56. A timeout more often means a firewall drop, a wrong host or a service bound to a different interface.
Port already in use
Find the process holding the port with sudo ss -tlpn 'sport = :56' or sudo lsof -i :56. Stop that process or configure it to bind another port; killing it without identifying it can take down a production service.
Firewall rule did not survive a reboot
UFW and Windows Firewall keep rules across restarts. Raw iptables rules do not: save them with iptables-save or the netfilter-persistent package, and re-apply after upgrades that reset the ruleset.
The port is blocked but still reachable
A firewall rule filters inbound traffic; it does not close the listener. Confirm with the check command above and bind the service to 127.0.0.1 when only local clients need it.
Port 56 at a glance
| Port number | 56 |
|---|---|
| Service name | xns-auth |
| Transport protocol | TCP / UDP |
| Category | Authentication and access |
| Range | Well-known port (0–1023) |
| Risk level | Standard/Low |
| Registered assignee | [Susie_Armstrong] |
| Registry description | XNS Authentication |
| Source | IANA Service Name and Transport Protocol Port Number Registry |
Frequently asked questions
What is port 56 used for?
Port 56 (XNS-AUTH) uses TCP / UDP. XNS Authentication.
How do I check if port 56 is open?
On Linux run `sudo ss -tlpn 'sport = :56'` and `sudo ss -ulpn 'sport = :56'`. On Windows run `Get-NetTCPConnection -LocalPort 56 -State Listen -ErrorAction SilentlyContinue` and `Get-NetUDPEndpoint -LocalPort 56 -ErrorAction SilentlyContinue` in PowerShell. If the port is open, the output shows a process listening on port 56; empty output usually means nothing is bound to it.
How do I block port 56?
With UFW run `sudo ufw deny 56/tcp` and `sudo ufw deny 56/udp`. With iptables run `sudo iptables -A INPUT -p tcp --dport 56 -j DROP` and `sudo iptables -A INPUT -p udp --dport 56 -j DROP`. Persist the iptables rules with your distribution's netfilter-persistent or iptables-save tooling so they survive a reboot.
Is port 56 safe to expose?
This port is not on our curated list of services with a widely exploited profile. Exposure is only safe when the listening service is intended, patched and protected by a firewall. Nevertheless, keep the listening service patched and remove it if unused. A default-deny firewall policy with explicit allow rules is still the safest baseline.
Related ports
Primary data: IANA Service Name and Transport Protocol Port Number Registry.
Last reviewed 2026-10-30 · Methodology · About · Privacy