Port 34Remote File
Remote File (RF) is an early protocol designed for file sharing and management across remote systems. It facilitates basic file access commands over a network, enabling clients to read, write, and manipulate files residing on a remote server. While largely outdated, it laid the foundation for more secure and efficient file transfer protocols used today..
- transport
- tcp · udp
- in transit
- cleartext
- assignment
- unofficial
- risk
- 4/10
- lookups
- 5,795
2 transports registered
payload readable on path
used by convention
caution
rank 853 of 993 · top 86%
Technical Details
what runs on :34-
Protocol Overview: Remote File (RF) protocol was designed to enable networked systems to perform file operations remotely, such as creating, reading, updating, and deleting files stored on a remote server. Operating over both TCP and UDP, it aimed to balance reliability and efficiency, albeit with minimal security considerations.
-
Communication Details: Typically, the protocol uses straightforward request-response messaging in which commands and file data are exchanged over an established connection. TCP facilitated reliable delivery, whereas UDP supported simpler, less reliable message transactions when speed was prioritized. Its simplicity made it accessible but also limited its scalability and robustness.
-
Current Status & Interoperability: Today, RF is considered obsolete, having been superseded by advanced file transfer protocols like FTP, SFTP, and SMB/CIFS. However, some legacy embedded systems or specialized applications may still interface with RF-based services either directly or through emulation layers.
Security Information
exposure of :34risk score
4/ 10caution
worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.
file transfer averages 4.1 across 114 ports — this one sits 0.1 below.
in transit
cleartext
credentials and payloads are readable by anyone on path
assignment
unofficial
used by convention, not registered — what answers here varies by deployment
reachable over
tcp · udp
udp is connectionless — source addresses are trivially spoofed and it is a reflection favourite
security overview
-
Common Vulnerabilities:
- Lack of encryption exposes file data and authentication credentials to interception and eavesdropping attacks.
- Minimal or absent authentication mechanisms enable unauthorized access.
- Susceptible to man-in-the-middle attacks due to absence of identity verification.
- Vulnerable to replay attacks where previous sessions are maliciously reused.
-
Mitigations:
- Replace RF with secure, modern protocols like SFTP or FTPS wherever feasible.
- Utilize network segmentation and access controls to isolate legacy RF services.
- Employ VPNs or encrypted tunnels to safeguard data transmitted over RF.
- Implement strong authentication gateways in front of RF services.
- Monitor network traffic for anomalous behavior targeting this port.
Related Ports
the 8 most looked-up other ports in file transfer — 114 ports carry that label.
| port | service | risk | |||
|---|---|---|---|---|---|
| :9080 | Groove RPC | TCPUDP | Web Services | caution | 70.8k |
| :17500 | Dropbox LAN Sync | TCPUDP | File Transfer | caution | 43.7k |
| :548 | Apple Filing Protocol | TCP | File Transfer | caution | 36.8k |
| :7000 | Vuze HTTPS Tracker | TCPtls | Security | caution | 28.9k |
| :1337 | PowerFolder P2P | TCP | Security | caution | 27.1k |
| :9001 | SharePoint Authoring | Web Services | caution | 26.3k | |
| :8080 | FilePhile Relay | UDP | File Transfer | caution | 25.6k |
| :1337 | WASTE Encrypted Sharing | TCP | Security | caution | 22.9k |
risk mix of the 8 listed
- caution100%
1 of 8 encrypted