Port 4672Remote File Access

Port 4672 is assigned to remote file access server traffic over TCP and UDP.

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 993 of 4,593 · top 22%

also known as rfa

1 other service is registered on port 4672. compare all 2 →

Technical Details

what runs on :4672

The registered service covers both TCP and UDP, but eMule/eDonkey deployments conventionally use UDP 4672 for peer and server queries, source exchange, and Kad-related traffic; the corresponding default client TCP port is commonly 4662. There is no universal handshake or framing for every listener on this port: eMule uses its own binary UDP message formats, while other software may implement the unassociated remote-file-access assignment. Traffic is normally unencrypted.

Security Information

exposure of :4672

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.5 across 168 ports — this one sits 1.5 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

An exposed eMule-compatible listener can reveal peer and file-sharing activity and receive unsolicited peer-to-peer traffic, while cleartext protocol data may be inspected or abused for traffic amplification or unwanted content exchange. It should not be exposed to the Internet unless peer-to-peer file sharing is intended; restrict it with firewall rules and verify which process owns the socket.

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

risk mix of the 8 listed

  • caution100%

1 of 8 encrypted