What This Port Is
Port 3367 is registered with IANA as satvid-datalnk — Satellite Video Data Link. The registration covers a block of ports: 3367 through 3371, all assigned for the same purpose, for both TCP and UDP.
The registrant is listed as Scott Engel. No RFC was ever published. No public documentation of the protocol exists. If satvid-datalnk was ever deployed, it left no visible footprint on the public Internet.
What the Registered Range Means
Port 3367 sits in the registered port range (1024–49151). These ports are not controlled by the operating system the way well-known ports (0–1023) are — any process can bind to them without elevated privileges. IANA maintains a registry so that services can claim a port number and avoid collisions.
The registry is voluntary. It is also permanent. A port assigned in 1998 to a service that never launched stays assigned. There is no expiration, no audit, no reclamation process. The IANA list is part museum, part active directory.
What Actually Runs Here
In practice: probably nothing intentional.
Automated port scanners probe port 3367 routinely — SANS Internet Storm Center logs probes from dozens of IPs daily — but this reflects generic Internet background noise, not targeted exploitation of a specific service. Scanners hit every port in the registered range looking for whatever happens to be listening.
If something is listening on port 3367 on a machine you control, it almost certainly isn't satvid-datalnk. It's more likely:
- A custom application that chose this port arbitrarily
- A development or debug service that was never meant to be exposed
- Something you should investigate
How to Check What's Listening
macOS / Linux:
Linux (alternative):
Windows:
The output will show the process ID and process name if anything is bound to the port. If nothing is returned, nothing is listening.
Why Ghost Registrations Matter
The IANA port registry has thousands of entries like this one. Services that were registered but never widely deployed, or that existed briefly in a closed system and then disappeared. They matter for one practical reason: they are taken.
If you're building a service and need a port number, you check the registry. Port 3367 is not available for your use — officially. In practice, nothing enforces this, and unoccupied registered ports get quietly repurposed all the time. But the friction is intentional. The goal is to avoid the situation where two different software packages independently choose the same port and conflict with each other on someone's network.
The ghost registrations are the cost of that system working at all.
Byla tato stránka užitečná?