Port 7574 COHERENCE-DISC
Port 7574 has a different IANA assignment for each transport protocol: TCP coherence; UDP coherence-disc.
What is port 7574 used for?
Port 7574 carries a different IANA service on each transport protocol: TCP coherence; UDP coherence-disc. 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. The same port is also registered under coherence.
Each transport reaches a different service on this number, so match the protocol to the service you are diagnosing. A TCP check says nothing about a UDP listener on the same port, and the reverse is also true. Both transports still bind to the same number, which is why two processes can collide even when they use different protocols.
Use the commands below to confirm whether port 7574 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: [Oracle_5].
Check and block port 7574
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 = :7574'
sudo ss -ulpn 'sport = :7574'Check on Windows
Get-NetTCPConnection -LocalPort 7574 -State Listen -ErrorAction SilentlyContinue
Get-NetUDPEndpoint -LocalPort 7574 -ErrorAction SilentlyContinueBlock with UFW
sudo ufw deny 7574/tcp
sudo ufw deny 7574/udpBlock with iptables
sudo iptables -A INPUT -p tcp --dport 7574 -j DROP
sudo iptables -A INPUT -p udp --dport 7574 -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 7574 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 7574 is usually used
Most traffic on port 7574 falls into these scenarios. The demo below is a safe way to confirm the listener before you change anything.
- Application servers opening pooled connections to the database on port 7574.
- Migrations, backups and reporting jobs run from a trusted bastion host.
- Local Docker or test environments that publish the database on the host.
Open a test connection
Probe the TCP listener before you debug credentials or driver settings.
nc -vz 127.0.0.1 7574
Common problems with port 7574
Connection refused or timed out
Refused usually means the host is reachable but nothing is listening on port 7574. 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 = :7574' or sudo lsof -i :7574. 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 7574 at a glance
| Port number | 7574 |
|---|---|
| Service name | coherence-disc |
| Aliases | coherence |
| Transport protocol | TCP / UDP |
| Assignments by protocol |
|
| Category | Databases |
| Range | Registered port (1024–10000) |
| Risk level | Standard/Low |
| Registered assignee | [Oracle_5] |
| Registry description | Oracle Coherence Cluster discovery service |
| Source | IANA Service Name and Transport Protocol Port Number Registry |
Frequently asked questions
What is port 7574 used for?
Port 7574 (COHERENCE-DISC). The IANA registry assigns a different service on each transport protocol: TCP coherence; UDP coherence-disc.
How do I check if port 7574 is open?
On Linux run `sudo ss -tlpn 'sport = :7574'` and `sudo ss -ulpn 'sport = :7574'`. On Windows run `Get-NetTCPConnection -LocalPort 7574 -State Listen -ErrorAction SilentlyContinue` and `Get-NetUDPEndpoint -LocalPort 7574 -ErrorAction SilentlyContinue` in PowerShell. If the port is open, the output shows a process listening on port 7574; empty output usually means nothing is bound to it.
How do I block port 7574?
With UFW run `sudo ufw deny 7574/tcp` and `sudo ufw deny 7574/udp`. With iptables run `sudo iptables -A INPUT -p tcp --dport 7574 -j DROP` and `sudo iptables -A INPUT -p udp --dport 7574 -j DROP`. Persist the iptables rules with your distribution's netfilter-persistent or iptables-save tooling so they survive a reboot.
Is port 7574 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 7569 · dell-eql-asmDell EqualLogic Host Group Management
- Port 7575 · wtmi-panelMain access port for WTMI Panel
- Port 7443 · oracleas-httpsOracle Application Server HTTPS
- Port 7981 · sossd-collectSpotlight on SQL Server Desktop Collect
- Port 6789 · radgGSS-API for the Oracle Remote Administration Daemon
- Port 7982 · sossd-discSpotlight on SQL Server Desktop Agent Discovery
Primary data: IANA Service Name and Transport Protocol Port Number Registry.
Last reviewed 2026-10-30 · Methodology · About · Privacy