High port (10001–65535) Standard/Low risk

Port 38422 XN-CONTROL

Quick answer

Port 38422 is the IANA-assigned xn-control port for Xn Control Plane (3GPP) (SCTP).

TransportSCTP
RiskStandard/Low
Typical useInfrastructure and administration

What is port 38422 used for?

Port 38422 is assigned to xn-control and uses SCTP. The IANA registry describes the service as “Xn Control Plane (3GPP)”. It sits above the registered range, where most numbers are transient client ports. A fixed high port is worth documenting precisely because tooling often assumes the default.

Ports are the transport-layer address a service listens on. This entry has no TCP assignment; SCTP clients establish their own association and fail in protocol-specific ways. That is why a port conflict appears whenever two processes try to bind the same number.

Use the commands below to confirm whether port 38422 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 Infrastructure and administration ports

Source: IANA Service Name and Transport Protocol Port Number Registry. Registered assignee: [Luis_Lopes].

Check and block port 38422

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 -Slpn 'sport = :38422'

Check on Windows

# No built-in Windows cmdlet for SCTP endpoints; use the vendor's diagnostic tool.

Block with UFW

# UFW does not manage SCTP rules; use iptables or nftables.

Block with iptables

sudo iptables -A INPUT -p sctp --dport 38422 -j DROP

These 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. UFW and the built-in Windows cmdlets cover TCP and UDP only; this port also lists SCTP, so use nftables, iptables or the vendor's diagnostic tool for those protocols. SCTP and DCCP handling also depends on kernel support, including their diagnostic modules, so a missing result may mean the module is not loaded rather than that nothing is listening.

Is port 38422 safe to expose?

Standard/Low

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 38422 is usually used

Most traffic on port 38422 falls into these scenarios. The demo below is a safe way to confirm the listener before you change anything.

Demo

Confirm the SCTP listener

This port is not registered for TCP, so an nc TCP probe cannot confirm it. Run this on the host that runs the service; empty output means nothing is bound to port 38422.

sudo ss -Slpn 'sport = :38422'

Common problems with port 38422

No reply from the service

Because UDP has no handshake, a missing reply can mean the service is idle, the packet was dropped, or the client sent it to the wrong interface. Check the listener locally before blaming the network.

Port already in use

Find the process holding the port with sudo ss -ulpn 'sport = :38422' or sudo lsof -i :38422. 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 38422 at a glance

Port number38422
Service namexn-control
Transport protocolSCTP
CategoryInfrastructure and administration
RangeHigh port (10001–65535)
Risk levelStandard/Low
Registered assignee[Luis_Lopes]
Registry descriptionXn Control Plane (3GPP)
SourceIANA Service Name and Transport Protocol Port Number Registry

Frequently asked questions

What is port 38422 used for?

Port 38422 (XN-CONTROL) uses SCTP. Xn Control Plane (3GPP).

How do I check if port 38422 is open?

On Linux run `sudo ss -Slpn 'sport = :38422'`. On Windows run `# No built-in Windows cmdlet for SCTP endpoints; use the vendor's diagnostic tool.` in PowerShell. If the port is open, the output shows a process listening on port 38422; empty output usually means nothing is bound to it. UFW and the built-in Windows cmdlets cover TCP and UDP only; SCTP needs nftables, iptables or the vendor's diagnostic tool.

How do I block port 38422?

With iptables run `sudo iptables -A INPUT -p sctp --dport 38422 -j DROP`. Persist the iptables rules with your distribution's netfilter-persistent or iptables-save tooling so they survive a reboot. UFW covers TCP and UDP only; use iptables or nftables for SCTP.

Is port 38422 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.

See all Infrastructure and administration ports

Primary data: IANA Service Name and Transport Protocol Port Number Registry.

Last reviewed 2026-10-30 · Methodology · About · Privacy