Port 386 sits in the well-known port range (0-1023), officially assigned by IANA to something called "ASA Message Router Object Def."1 The assignment lists a contact person named Steve Laitinen, both TCP and UDP protocols, and nothing else. No RFC. No documentation. No software that anyone can find. Just a name in a registry and a port number that waits for traffic that never comes.
This is the ghost ship phenomenon of Internet infrastructure.
What This Port Was Supposed to Do
"ASA Message Router Object Def" suggests some kind of message routing service—probably middleware for passing data between systems or objects in a distributed architecture. The "Def" might stand for "Definition" or be part of an acronym that's been lost to time.
But that's speculation. The official IANA registry provides no details beyond the service name and protocol assignments.2 There's no RFC defining the protocol. No manual explaining how it works. No GitHub repository with implementation code. The service name exists in the registry the way a ship exists on a manifest after it's already sunk—documented, but gone.
The Well-Known Port Range
Port 386 occupies space in the well-known port range (0-1023), reserved by IANA for services considered fundamental to Internet operations.3 Getting a well-known port assignment used to mean something. These were the ports for protocols everyone needed: SMTP at 25, HTTP at 80, HTTPS at 443.
But port 386 holds a reservation for a service that may never have launched.
It's a reminder that the Internet's numbering systems were designed when bandwidth was expensive, addresses were scarce, and people assumed every assignment would matter. Port 386 is the digital equivalent of a reserved parking space for a car that was never built.
Security Context: Trojan Activity
Port 386 has been flagged in security databases because trojans and viruses have used it for communication in the past.45 This doesn't mean the port is inherently dangerous—it means malware authors sometimes use obscure, unassigned ports precisely because nobody's watching them.
An open port 386 on your system likely isn't ASA Message Router Object. It's either malware from a decade ago or some custom application that grabbed an unused port number. The official assignment is irrelevant to the actual traffic.
How to Check What's Listening
On Linux or macOS:
On Windows:
If something's listening on port 386, it's not the ghost service from the registry. It's something else wearing its number.
Why This Port Matters
Port 386 represents the archaeology of Internet infrastructure. The registry says ASA Message Router Object lives here. The reality is silence. No packets. No protocol. Just a name in a database and a number that goes unused.
The Internet is full of these ghosts—assignments made decades ago for services that never shipped, protocols that died in development, ideas that seemed essential in 1985 and irrelevant by 1995. Port 386 is one of them.
The assignment remains because removing it is harder than leaving it. The IANA registry is append-only by culture if not by rule. Once a port is assigned, it stays assigned, even if the thing it was assigned to never existed or stopped existing years ago.
Port 386 is a monument to something that might have been. A number waiting for traffic that will never arrive. A reserved seat at a table for a guest who never showed up.
That's the strangest thing about the Internet's numbering systems: they're full of holes that look like assignments, and assignments that look like holes. Port 386 is both.
Related Ports
- Port 80 — HTTP, the protocol that defined the web
- Port 443 — HTTPS, the encrypted version that saved it
- Port 25 — SMTP, still carrying email after four decades
- Ports 1024-49151 — Registered ports, where most custom services actually live
Frequently Asked Questions
ئایا ئەم پەڕەیە بەسوود بوو؟