Port 2487: PNS — A Registered Port Nobody Uses

What Port 2487 Is

IANA's registry lists port 2487 as pns — Policy Notice Service — assigned to Akiyoshi Ochi at Fujitsu (akiyoshi&net.paso.fujitsu.co.jp). ¹ Both TCP and UDP are registered.

That's the complete paper trail. No RFC. No public documentation. No open-source implementations. No discussion threads. Port 2487 is a registered port with a name, an assignee, and nothing else.

What "Registered Port" Means

Ports 1024 through 49151 are the registered range. Unlike the well-known ports below 1024, these don't require root privileges to bind to, and the services using them span the full spectrum: widely deployed protocols (like MySQL on 3306 or PostgreSQL on 5432), vendor-specific enterprise tools, and a long tail of registrations that never materialized into real software.

Port 2487 sits in that long tail. The registration exists to prevent conflicts in the event the service ever became a real product. It never did, or if it did, it stayed entirely inside Fujitsu's network.

Why These Ghost Ports Exist

The IANA port registry has thousands of entries like this one. A team builds an internal tool, applies for a port number to avoid stepping on anything else, and moves on. The product gets shelved, the team gets reorganized, the company pivots. The port number stays registered forever, a placeholder in a namespace that the Internet just routes around.

It's not waste so much as it is history. Each ghost registration is a fossil of a product that almost was.

If You See Traffic on Port 2487

If something on your network is actually using port 2487, it's not this Fujitsu service. It's almost certainly:

• A custom application or service your organization runs that happened to pick this port
• A misconfigured service meant to run on a different port
• Malware or unauthorized software — uncommon ports are sometimes chosen specifically because firewalls don't have rules for them

Check what's listening:

Linux / macOS:

# Show which process is bound to port 2487
ss -tlnp | grep 2487
# or
lsof -i :2487

Windows:

netstat -ano | findstr :2487

The output will show the process ID. From there you can identify what's running and whether it belongs.