Port 1747: ftrapid-2 — A Name with No Story

What This Port Is

Port 1747 sits in the registered port range (1024–49151). These ports are assigned by IANA, the Internet Assigned Numbers Authority, to specific services and protocols upon request. Unlike the well-known ports below 1024 — where HTTP lives at 80 and SSH at 22 — registered ports don't require special system privileges to use. Any application can bind to them.

IANA's registry shows port 1747 assigned to a protocol called ftrapid-2, registered for both TCP and UDP. The contact on file is Richard J. Williams.

That's where the trail ends.

The Ghost Registration

"ftrapid-2" has no RFC. No public documentation. No open-source implementations. No forum posts from developers asking questions about it. No company that claims to have built it.

The IANA registry is older than the web, and it carries thousands of entries from an era when registration was informal — you wrote in, named your protocol, and got your port. Many of those protocols were internal tools, proprietary systems, or products that never shipped. The registry kept the entry. The protocol vanished.

Port 1747 appears to be one of those. The name suggests something rapid (ft = file transfer, perhaps?), and the "-2" implies a second version of something. But whatever ftrapid-1 was — if it ever existed — didn't generate enough of a footprint to find.

This isn't unusual. The IANA registry has hundreds of registered ports with no surviving documentation. They're fossils: proof that something was once planned, with no evidence of what became of it.

What Might Actually Be on Port 1747

If you see traffic on port 1747, it isn't ftrapid-2. It's something else using an available port — which is normal. Applications frequently bind to registered ports that happen to be free on a given system, whether by configuration or by chance.

Common reasons a port shows up listening:

• A developer picked it arbitrarily during testing
• A proprietary application uses it by convention without IANA registration
• A misconfigured or default service bound to it

How to Check What's Using It

If port 1747 is active on your system and you want to know why:

On Linux or macOS:

# Show which process is listening on port 1747
ss -tlnp | grep 1747

# Or with lsof
lsof -i :1747

On Windows:

# Show listening ports and the process using them
netstat -ano | findstr :1747

# Then look up the PID
tasklist | findstr <PID>

On macOS (Activity Monitor alternative):

lsof -nP -iTCP:1747 -sTCP:LISTEN

Why Unassigned (and Forgotten) Ports Matter

The 65,535 ports on any given system are finite. IANA's job is to prevent collisions — to ensure that when two applications need a well-known address, they don't reach for the same number. When ports get registered and then abandoned, they're not harmful, but they do create clutter in the registry and minor confusion for anyone who encounters them.

The more interesting point: the gap between what's registered and what's documented is enormous. Port 1747 is registered. But if you need to know what's actually running on port 1747 on your machine, the registry won't help you. The tools above will.