Port 3035: fjsv-gssagt — Registered, Obscure, and Mostly Empty

What Port 3035 Is

Port 3035 sits in the registered port range (1024–49151). These are ports that vendors and developers can claim through IANA, the organization that maintains the official list of port assignments.

IANA shows port 3035 assigned to fjsv-gssagt — a Fujitsu internal service.¹ The name itself doesn't appear in Fujitsu's public documentation, and outside the IANA registry, it leaves almost no trace. The port has also been linked to Powertech Compliance Monitor, a security auditing tool for IBM i (formerly AS/400) systems.²

Neither use is widespread. For most networks, port 3035 is functionally unassigned.

The Registered Port Range

Registered ports exist so vendors can stake a claim to a number and avoid collisions with other software. The process is intentionally low-friction. This means the registry contains thousands of ports tied to enterprise software, internal tools, and products that have since been discontinued or forgotten.

Port 3035 is one of those. The registration is real. The activity isn't.

What You'll Actually See on Port 3035

The SANS Internet Storm Center logs scanning activity against port 3035 — probes from automated scanners sweeping large port ranges, not traffic from legitimate clients connecting to fjsv-gssagt.³

If your firewall logs show inbound connections to port 3035, the overwhelming likelihood is opportunistic scanning. If something on your own machine is listening on port 3035, that's worth investigating.

How to Check What's Listening

macOS / Linux:

lsof -i :3035

Linux (alternative):

ss -tlnp | grep 3035

Windows:

netstat -ano | findstr :3035

These commands show the process name and PID bound to the port. If nothing appears, nothing is listening — which is the expected result on almost every machine.

Why This Matters

The port system only works if registered ports mean something. When a port is claimed but unused, it occupies namespace without contributing clarity. Network scanners treat any listening port as a potential target, which means even quiet corners of the registry draw automated attention.

Port 3035 isn't dangerous. It isn't interesting. It's a reminder that the registry is a historical document as much as an operational one — an accurate record of every vendor who ever thought they needed a port number.