Port 1736: Street-Stream — A Name Without a Service

Port 1736 sits in the registered ports range, officially assigned to something called "street-stream." That's where the trail goes cold.

What the Registry Says

IANA lists port 1736 on both TCP and UDP as reserved for "street-stream." That's the full entry: a name, a port number, two transport protocols. No RFC. No documentation. No company or contact on record.¹

This is more common than you might expect. The registered port range (1024-49151) was designed for applications that needed a stable, predictable port. You filed with IANA, got your number, and software could find your service reliably. In practice, many registrations from the 1990s and early 2000s are orphaned — the product never shipped, the company folded, or the protocol was quietly abandoned while the registry entry persisted.

Street-stream was likely some kind of streaming media application, based on the name. Beyond that, there's nothing to go on.

What Actually Uses This Port

In practice, port 1736 appears in network scans and firewall logs as generic probe traffic — automated scanners sweeping the registered port range looking for anything that responds. The SANS Internet Storm Center shows occasional scan activity but nothing that suggests an active, organized service running here.²

If you're seeing traffic on port 1736 in your environment, it's almost certainly one of three things:

• Automated Internet-wide scanning (background noise)
• A custom internal application your organization chose to run on this port
• A misconfigured service that accidentally bound to it

Checking What's Listening

To see if anything on your system is using port 1736:

Linux/macOS:

ss -tlnp | grep 1736
# or
lsof -i :1736

Windows:

netstat -ano | findstr :1736

If something is listening, the process ID will tell you what it is. On Linux, lsof shows the process name directly.

The Registered Range and What It Means

The 1024-49151 range is sometimes called "user ports" or "registered ports." Unlike the well-known ports below 1024 (which require root privileges to bind on most systems), registered ports can be used by any application. IANA maintains a registry of which services have claimed which numbers, but registration is voluntary and enforcement is nonexistent.

The result: the registry is partly a historical document. Thousands of entries point to services that no longer exist, companies that dissolved, and protocols that were replaced before anyone wrote documentation. Street-stream is one of them.

The ports that matter are the ones with active software behind them. Port 1736 has a name but no software. It's a door with a placard and nothing behind it.