What Range This Port Belongs To
Port 3155 is a registered port — part of the range from 1024 to 49151 that IANA manages on behalf of software vendors and protocol designers. Unlike the well-known ports below 1024 (where HTTP lives at 80, SSH at 22, DNS at 53), registered ports don't require elevated privileges to open. Any user-level process can bind to them.
The registered range exists so that software can claim a consistent, recognizable port. If your application always shows up at port 3155, users and network admins know what to expect. The alternative — picking a random high port — creates chaos for firewalls and support tickets.
The IANA Registration: "jpegmpeg"
IANA's registry lists port 3155 as assigned to a service called jpegmpeg. This name suggests some kind of JPEG/MPEG media streaming protocol — possibly an early attempt at a standardized image or video streaming service over TCP/UDP.
What "jpegmpeg" actually was, in practice, is hard to pin down. No widely-deployed software documented it. No RFC defined it. No major application ever announced it as its home. It's one of the many registered port entries that reflect an ambition that never shipped — someone filed the paperwork, IANA reserved the port, and nothing followed.
The registered port namespace has thousands of entries like this. A reservation is easy to make; building software that people actually run is harder.
Known Real-World Use: Tom Clancy's H.A.W.X.
The most documented real traffic on port 3155 came from Tom Clancy's H.A.W.X., the 2009 aerial combat game developed by Ubisoft Romania. H.A.W.X. used a range of ports in the 3074–3174 neighborhood for its online multiplayer and co-op modes, and port 3155 TCP appeared on its list of required open ports.1
If you're running a firewall that logged connections to port 3155 around 2009–2012 and someone in your household was into flight sims, that was probably H.A.W.X.
Security Notes
Port 3155 has historically appeared in association with the Mydoom/Novarg family of worms, which used various high ports to establish backdoor listeners on infected machines. This isn't a property of port 3155 specifically — Mydoom cast a wide net — but it's worth noting if you see unexpected listening services here.
An unrecognized process binding to port 3155 on a modern system is worth investigating.
How to Check What's Listening
On macOS or Linux:
With netstat (cross-platform):
On Windows:
The output will show the process ID (PID). Cross-reference that with your process list to identify the application.
Why Unassigned Ports Matter
Port 3155 illustrates something real about how the port namespace works: the map is not the territory. IANA's registry is a record of intent, not reality. Ports get claimed for services that never ship. Other software moves in quietly. Malware picks ports precisely because they're quiet corners of the address space where traffic won't draw attention.
When you see an unfamiliar port in your logs, the IANA registry is the first stop — but it's not the last word. The honest answer is often "check what's actually running."
Беше ли полезна тази страница?