Port 1884: idmaps — The Internet's Forgotten Distance Map

What This Port Is

Port 1884 is a registered port — officially assigned by IANA to a service called idmaps, short for Internet Distance Map Service.

Registered ports fall in the range 1024–49151. Unlike the well-known ports below 1024 (which require root privileges to bind), registered ports are simply claimed with IANA and documented. Any application can use them.

The Assigned Service: IDMaps

In the late 1990s, researchers tackled a genuinely hard problem: how do you know how far away a host is on the Internet — not in miles, but in milliseconds of latency?

Applications care about this. A video conferencing system wants the closest server. A distributed database wants to minimize round-trip time between replicas. But the only way to know latency between two arbitrary hosts was to measure it directly, which doesn't scale. You can't ping every pair of machines on Earth.

IDMaps proposed a solution: a global infrastructure of Tracer hosts spread across the Internet, continuously measuring latency between themselves and publishing the results. Any host could query the IDMaps system and get an estimated distance to any other host — without doing its own measurements.¹

It was ambitious. It required distributed infrastructure, a query protocol (called DIP, the Distance Information Protocol), and coordinated deployment across many networks. It never achieved that deployment. CDNs, anycast routing, and simpler estimation techniques like geolocation-plus-RTT made it unnecessary.

The system was documented in a 2001 IEEE/ACM Transactions on Networking paper.² The port assignment remains in the IANA registry. The service itself is effectively defunct.

Informal Uses

Because port 1884 sits directly above port 1883 — the official MQTT port — it occasionally shows up in MQTT configurations and discussions. Some operators run alternative MQTT listeners on 1884 when 1883 is occupied, or use it for WebSocket-based MQTT connections. This is informal convention, not any standard.³

If you see traffic on port 1884, MQTT is the most likely explanation in practice. IDMaps traffic is essentially nonexistent.

What to Check if This Port Is Open

To see what's listening on port 1884 on your system:

Linux/macOS:

# Show process listening on port 1884
ss -tlnp | grep 1884
# or
lsof -i :1884

Windows:

netstat -ano | findstr :1884

The process name will tell you what's actually there. An MQTT broker like Mosquitto, EMQX, or HiveMQ is the most likely answer.

Why Unassigned and Dormant Ports Matter

The IANA port registry exists to prevent collisions — two applications accidentally claiming the same port and creating chaos. When a registered port's service goes dormant, the assignment doesn't disappear. It stays, acting as a placeholder that prevents other services from officially claiming the space.

This matters less now than it once did. With 65,535 ports available and most traffic tunneled through HTTP/HTTPS anyway, port conflicts are rarer. But the registry still serves as institutional memory: a record of what was tried, what was assigned, and what the Internet's engineers were worried about at a given moment.

Port 1884 is a small fossil from the era when researchers believed the Internet needed a global latency map, and believed they could build one.