Port 1836: ste-smsc — A Registered Port That Vanished

What Is Port 1836?

Port 1836 sits in the registered ports range (1024–49151). These ports are assigned by the Internet Assigned Numbers Authority (IANA) to specific services on request, creating a global registry that helps avoid collisions between applications.

IANA's registry shows port 1836 assigned to a service named ste-smsc, listed for both TCP and UDP, with Tom Snauwaert as the registrant contact.¹ The name suggests a Short Message Service Center (SMSC) — the infrastructure that routes SMS messages between mobile devices and networks.

The Problem: There's Nothing Else

That's where the documentation ends.

No RFC. No public specification. No open-source implementation that claims port 1836. No widely-used commercial product that announces it. The "ste" prefix in "ste-smsc" likely refers to a company or product name — possibly a proprietary telecom tool registered in the 1990s or early 2000s when IANA registrations were easier to obtain — but whatever it was, it didn't leave a public record.

This isn't unusual. The registered ports range contains hundreds of assignments like this: a name was submitted, a port was granted, and then the product either never shipped, remained internal, or quietly disappeared. The registry keeps the entry forever. The port stays "assigned."

What This Means for You

If port 1836 shows up in your network traffic or firewall logs, it's almost certainly not the ste-smsc service. More likely explanations:

• A development server or internal application chose this port arbitrarily
• Peer-to-peer software is using it as a dynamic listening port
• A game or custom tool picked it to avoid conflicts with well-known services

How to Check What's Using It

On Linux/macOS:

# See what process is listening on port 1836
sudo ss -tlnp | grep 1836
# or
sudo lsof -i :1836

On Windows:

netstat -ano | findstr :1836

The process ID in the output will tell you exactly what's running there. On Linux, lsof gives you the process name directly.

Why Unassigned-in-Practice Ports Matter

The registered ports range was designed to create order — a namespace where a port number maps to a known service. But the system relies on honesty and upkeep. When ports are registered and abandoned, they accumulate in the registry as noise: technically "assigned," functionally inert.

Port 1836 is one of many. They're a reminder that the port namespace, like many Internet standards, is partly a living system and partly a fossil record.