1. Ports
  2. Port 2722

What Range This Port Belongs To

Port 2722 falls in the registered port range (1024–49151), administered by IANA. 1

The registered range is where legitimate software goes to stake a claim. Port 22 was registered for SSH. Port 443 for HTTPS. Port 3306 for MySQL. Each assignment means "this protocol lives here, and other software should avoid squatting on it."

Port 2722 has no registered tenant. IANA has no official service-to-port mapping for it. It's an empty lot in a neighborhood full of named addresses.

What Actually Uses It

Nothing official. No RFC, no standard, no protocol owns port 2722.

That said, software doesn't always ask permission. Any application can open a listener on any unassigned port without violating a standard — just good manners. Development servers, internal tools, and custom software frequently land on unassigned ports when their developers want something above 1024 (to avoid requiring root privileges) and below the ephemeral range.

Port 2722 has appeared in older security databases flagged as having been used by malware. 2 This is less damning than it sounds. Trojans need a port to phone home on. They pick numbers in the registered range precisely because unassigned ports don't trigger automatic firewall rules. The association says more about how trojans choose ports than about anything specific to 2722.

How to Check What's Listening

If you see traffic on port 2722 and want to know what's responsible:

On Linux or macOS:

sudo ss -tlnp | grep 2722
# or
sudo lsof -i :2722

On Windows:

netstat -ano | findstr :2722

The process ID in the output maps to a specific application. On Linux, lsof will name it directly. On Windows, take the PID to Task Manager or run:

tasklist | findstr <PID>

If something is listening and you don't recognize it, that's worth investigating — not because port 2722 is inherently suspicious, but because unexpected listeners always are.

Why Unassigned Ports Matter

The registered range exists to prevent collision. When MySQL picks 3306, it means every sysadmin, every firewall rule, every cloud security group can say "allow 3306 inbound for database traffic" and know what they're allowing.

Unassigned ports don't have that shared language. When something listens on 2722, there's no shared expectation. That ambiguity is sometimes useful (informal internal services) and sometimes a problem (malware hiding in the noise).

The 48,000+ unassigned slots in the registered range are the Internet's frontier territory — not wild, exactly, but without the infrastructure of named streets.

Hasznos volt ez az oldal?

😔
🤨
😃