1. Ports
  2. Port 1690

What Range This Port Belongs To

Port 1690 falls in the registered ports range: 1024 through 49151. These ports are assigned by the Internet Assigned Numbers Authority (IANA) for specific services and applications, distinguishing them from the well-known ports (0-1023) that are reserved for core Internet infrastructure.

Registered ports don't require root or administrator privileges to open, which makes them attractive for application-layer services. Any software can listen on port 1690 without special system access.

What IANA Says

The IANA registry lists port 1690 (both TCP and UDP) as assigned to a service called ng-umds.1

That's where the official record ends.

No RFC defines ng-umds. No widely-used software claims it. No documentation explains what the name stands for or what the service does. It appears in the registry the way a name appears on a decades-old deed: technically on record, practically unknown.

This isn't unusual. The registered port range contains thousands of entries like this — services that were assigned a number, perhaps for an internal tool or a product that never shipped at scale, and then faded. The name gets preserved in the registry long after the context disappears.

What You Might Actually Find Here

If something is listening on port 1690 on your system or network, it almost certainly isn't ng-umds (whatever that is). More likely candidates:

  • Application-specific traffic: Some software picks ports from the registered range without advertising what they're doing.
  • Dynamic assignment: Operating systems sometimes use registered ports for ephemeral outbound connections.
  • Custom services: Internal tools, game servers, or development services sometimes pick ports opportunistically.

A port name in the registry doesn't mean that's what's using it on your machine.

How to Check What's Actually Listening

On Linux or macOS:

sudo ss -tlnp | grep 1690
# or
sudo lsof -i :1690

On Windows:

netstat -aon | findstr 1690

The process ID from these commands will tell you exactly what software opened the port. Cross-reference it with your process list (ps aux on Unix, Task Manager on Windows) to find the owner.

Why Unassigned-in-Practice Ports Matter

The port system works because most software respects the registry. When a service registers a port number, other software avoids it, and firewalls can make informed decisions about what to allow.

But the registered range has 48,127 slots. IANA has assigned many of them to services that are obscure, defunct, or never widely deployed. The result is a registry that's authoritative in principle and spotty in practice.

Port 1690 is one of those spots. It has a name, no documentation, and no notable presence in the wild. If you see traffic here, investigate it — not because it's suspicious, but because the port's official record offers no help in understanding what you're looking at.

بۇ بەت پايدىلىق بولدىمۇ؟

😔
🤨
😃