Port 1779 sits in the registered port range with an official IANA assignment and a name almost no one has heard of: pharmasoft. The registry lists a contact email at pharmasoft.se — a Swedish pharmaceutical software company that no longer appears to operate. The software is forgotten. The port number remains, reserved in perpetuity.
This is the quiet reality of much of the registered port space.
The Range
Port 1779 falls in the registered ports range: 1024 to 49151.
These ports are assigned by IANA (the Internet Assigned Numbers Authority) to specific services and applications on a first-come, first-served basis. Unlike the well-known ports (0-1023), which are tightly controlled and home to foundational protocols like HTTP, SSH, and DNS, the registered range is sprawling. It holds thousands of assignments from companies, developers, and projects across decades — VoIP systems, database servers, game clients, enterprise software, and plenty of services that no longer exist.
Registering a port costs nothing and claims nothing enforced. Any application can listen on port 1779 regardless of the pharmasoft assignment. The registry is a coordination mechanism, not a lock.
What Pharmasoft Was
The IANA registry entry lists both TCP and UDP for port 1779 and credits Ola Strandberg of pharmasoft.se as the contact. Beyond that, the historical record is thin. This appears to have been pharmaceutical industry software — a vertical application that needed a port for client-server communication, registered it, and eventually faded. The registration persists because IANA port assignments don't expire.1
Unofficial Uses
No widely documented unofficial service runs on port 1779. Some sources list it as associated with Pingtel SIP trunking, but this appears to be an error propagated across port lookup sites — the IANA record clearly shows pharmasoft, not Pingtel.2
If you're seeing traffic on port 1779, it's most likely one of three things: opportunistic scanning (attackers probe registered ports looking for misconfigured or vulnerable services), a custom internal application that chose this port arbitrarily, or legacy software that predates its obscurity.
What's Actually Listening on This Port
If you want to know what's using port 1779 on a specific machine:
On Linux or macOS:
On Windows:
The process ID in the output will tell you what's actually there. Cross-reference it with your system's process list.
Why Unassigned-in-Practice Ports Matter
The registered port range contains thousands of entries like this one — officially named, practically orphaned. They matter for a few reasons:
Security scanning targets them. Attackers probe the entire port range systematically. A service running on port 1779 is no more hidden than one running on port 80. Security through obscurity isn't security.
They're available for internal use. When an organization needs a port for internal software, registered-but-unused ports like 1779 are reasonable choices — the IANA assignment signals no active major service is competing for the space.
They document history. The pharmasoft entry is a small artifact of the 1990s-era rush to register ports for vertical software. Hundreds of similar entries exist in the registry, each one a quiet record of an application that once mattered to someone.
The port namespace is finite. Every number from 0 to 65535 is a choice, and most of those choices are now frozen in the registry, whether or not anyone is still listening.
Bu sayfa faydalı oldu mu?