Port 3147RFIO (Remote File I/O)

RFIO provides remote file access, traditionally for CERN CASTOR storage systems and related scientific computing environments.

transport
tcp · udp

2 transports registered

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
5/10

caution

lookups
0

rank 994 of 2,366 · top 42%

also known as rfiod

Technical Details

what runs on :3147

RFIO normally uses TCP port 3147 for client-to-server remote file operations; UDP is also registered, but TCP is the transport generally associated with the service. Clients use RFIO libraries and tools such as rfcp, rfio_cat, and directory or metadata commands to access files through an RFIO daemon. It is a purpose-built file protocol rather than SMB or NFS, and legacy deployments generally do not provide transport encryption by default.

Security Information

exposure of :3147

risk score

5/ 10caution

worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.

file transfer averages 3.8 across 149 ports — this one sits 1.2 above.

in transit

cleartext

credentials and payloads are readable by anyone on path

assignment

official

registered with iana for this service — scanners fingerprint it by number

reachable over

tcp · udp

udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite

security overview

RFIO should not be exposed directly to the public Internet. An exposed daemon may provide access to sensitive research or operational data, and legacy deployments can rely on weak or site-specific authentication while transmitting traffic without modern transport encryption. Restrict port 3147 to trusted storage clients and replace or isolate obsolete deployments where possible.

the 8 most looked-up other ports in file transfer — 149 ports carry that label.

risk mix of the 8 listed

  • caution100%

1 of 8 encrypted