Port 4604 IRP
Port 4604 is the IANA-assigned irp port for Identity Registration Protocol (TCP).
What is port 4604 used for?
Port 4604 is assigned to irp and uses TCP. The IANA registry describes the service as “Identity Registration Protocol”. 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 irp connects to port 4604. 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 4604 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: [Sixscape_Communications_Pte_Ltd].
Check and block port 4604
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 = :4604'Check on Windows
Get-NetTCPConnection -LocalPort 4604 -State Listen -ErrorAction SilentlyContinueBlock with UFW
sudo ufw deny 4604/tcpBlock with iptables
sudo iptables -A INPUT -p tcp --dport 4604 -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 4604 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 4604 is usually used
Most traffic on port 4604 falls into these scenarios. The demo below is a safe way to confirm the listener before you change anything.
- Application backends and supporting services that use a fixed registered number.
- Containers or local stacks that publish the port on the host.
- Firewall and exposure reviews before the service goes to production.
Probe the port
Confirm something is listening before you debug the client. This checks a TCP handshake on the port.
nc -vz 127.0.0.1 4604
Common problems with port 4604
Connection refused or timed out
Refused usually means the host is reachable but nothing is listening on port 4604. 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 = :4604' or sudo lsof -i :4604. 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 4604 at a glance
| Port number | 4604 |
|---|---|
| Service name | irp |
| Transport protocol | TCP |
| Category | Application services |
| Range | Registered port (1024–10000) |
| Risk level | Standard/Low |
| Registered assignee | [Sixscape_Communications_Pte_Ltd] |
| Registry description | Identity Registration Protocol |
| Source | IANA Service Name and Transport Protocol Port Number Registry |
Frequently asked questions
What is port 4604 used for?
Port 4604 (IRP) uses TCP. Identity Registration Protocol.
How do I check if port 4604 is open?
On Linux run `sudo ss -tlpn 'sport = :4604'`. On Windows run `Get-NetTCPConnection -LocalPort 4604 -State Listen -ErrorAction SilentlyContinue` in PowerShell. If the port is open, the output shows a process listening on port 4604; empty output usually means nothing is bound to it.
How do I block port 4604?
With UFW run `sudo ufw deny 4604/tcp`. With iptables run `sudo iptables -A INPUT -p tcp --dport 4604 -j DROP`. Persist the iptables rules with your distribution's netfilter-persistent or iptables-save tooling so they survive a reboot.
Is port 4604 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 4573 · cardifftec-backA port for communication between a server and client for a custom…
- Port 4605 · sixchatDirect End to End Secure Chat Protocol
- Port 4566 · kwtcKids Watch Time Control Service
- Port 4606 · sixidSecure ID to IP registration and lookup
- Port 4558 · mtcevrunqmanMarathon everRun Quorum Service Manager
- Port 4646 · dots-signalDistributed Denial-of-Service Open Threat Signaling (DOTS) Signal…
Primary data: IANA Service Name and Transport Protocol Port Number Registry.
Last reviewed 2026-10-30 · Methodology · About · Privacy