Port 5321 BSFSVR-ZN-SSL
Port 5321 is the IANA-assigned bsfsvr-zn-ssl port for Webservices-based Zn interface of BSF over SSL (TCP).
What is port 5321 used for?
Port 5321 is assigned to bsfsvr-zn-ssl and uses TCP. The IANA registry describes the service as “Webservices-based Zn interface of BSF over SSL”. It sits in the registered range, the block used by databases, application servers and developer tooling. Port conflicts here are common when several local services start at once.
Ports are the transport-layer address a service listens on. A client that wants to reach bsfsvr-zn-ssl connects to port 5321. If nothing is listening, the connection is refused. That is why a port conflict appears whenever two processes try to bind the same number.
Use the commands below to confirm whether port 5321 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.
Source: IANA Service Name and Transport Protocol Port Number Registry. Registered assignee: [Bert_Paul].
Check and block port 5321
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 = :5321'Check on Windows
Get-NetTCPConnection -LocalPort 5321 -State Listen -ErrorAction SilentlyContinueBlock with UFW
sudo ufw deny 5321/tcpBlock with iptables
sudo iptables -A INPUT -p tcp --dport 5321 -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 5321 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 5321 is usually used
Most traffic on port 5321 falls into these scenarios. The demo below is a safe way to confirm the listener before you change anything.
- Serving a website, API or reverse-proxy traffic that clients reach on port 5321.
- Load-balancer and uptime checks probing the port before routing requests.
- Local development, where a browser or curl calls the service on localhost:5321.
Send a test request
Start a local web server, then ask the port for response headers. Replace 127.0.0.1 with the host you are testing.
curl -I http://127.0.0.1:5321Common problems with port 5321
Connection refused or timed out
Refused usually means the host is reachable but nothing is listening on port 5321. 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 = :5321' or sudo lsof -i :5321. 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 5321 at a glance
| Port number | 5321 |
|---|---|
| Service name | bsfsvr-zn-ssl |
| Transport protocol | TCP |
| Category | Web and HTTP |
| Range | Registered port (1024–10000) |
| Risk level | Standard/Low |
| Registered assignee | [Bert_Paul] |
| Registry description | Webservices-based Zn interface of BSF over SSL |
| Source | IANA Service Name and Transport Protocol Port Number Registry |
Frequently asked questions
What is port 5321 used for?
Port 5321 (BSFSVR-ZN-SSL) uses TCP. Webservices-based Zn interface of BSF over SSL.
How do I check if port 5321 is open?
On Linux run `sudo ss -tlpn 'sport = :5321'`. On Windows run `Get-NetTCPConnection -LocalPort 5321 -State Listen -ErrorAction SilentlyContinue` in PowerShell. If the port is open, the output shows a process listening on port 5321; empty output usually means nothing is bound to it.
How do I block port 5321?
With UFW run `sudo ufw deny 5321/tcp`. With iptables run `sudo iptables -A INPUT -p tcp --dport 5321 -j DROP`. Persist the iptables rules with your distribution's netfilter-persistent or iptables-save tooling so they survive a reboot.
Is port 5321 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
- Port 5320 · bsfserver-znWebservices-based Zn interface of BSF
- Port 5349 · stunsSession Traversal Utilities for NAT (STUN) port
- Port 5798 · enlabel-dplProprietary Website deployment service
- Port 5248 · caacwsCA Access Control Web Service
- Port 5841 · shiprush-d-chZ-firm ShipRush interface for web access and bidirectional data
- Port 5015 · fmwpFileMaker, Inc. - Web publishing
Primary data: IANA Service Name and Transport Protocol Port Number Registry.
Last reviewed 2026-10-30 · Methodology · About · Privacy