whatportis.com
suggest an edit →

Port 750rfile Protocol

Port 750, typically associated with 'rfile', was historically used within the Kerberos authentication system developed by MIT. It served as an RPC-based frontend for remote file management, particularly for secure file transfer and operations in academic and research environments. While largely deprecated today, understanding rfile helps contextualize legacy authentication and file service protocols..

inSecurityFile TransferNetwork Services
transport
tcp

single transport

in transit
cleartext

payload readable on path

assignment
official

registered with iana

risk
4/10

caution

lookups
5,605

rank 870 of 993 · top 88%

2 other services are registered on port 750. compare all 3 →

Technical Details

what runs on :750

Port 750 was primarily linked with the Kerberos V4 protocol, serving as the default port for its Authentication Service and sometimes for related services like rfile. The rfile service provided authenticated, remote file manipulation capabilities similar to a file server, relying on the security provided by Kerberos tickets.

Historically, rfile facilitated operations such as copying files or executing file management commands remotely in a permissioned and authenticated manner. Using MIT's Kerberos, the communication over this port enabled secure delegation of credentials and minimized the exposure of plaintext passwords or session hijacking risk within trusted networks, especially in academic and research settings.

Due to advancements in secure transport protocols and the migration to Kerberos V5 (which defaults to port 88), the use of port 750 for these services has diminished significantly. Modern environments favor integrated directory services, SFTP, or SMB with enhanced security controls, rendering rfile obsolete except in some legacy deployments.

Security Information

exposure of :750

risk score

4/ 10caution

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

security averages 3.8 across 216 ports — this one sits 0.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

every listening transport is another surface to filter at the edge

security overview

Common Vulnerabilities:

  • Legacy Authentication Issues: Since Kerberos V4 is now considered deprecated and less secure, services operating on port 750 may be vulnerable to replay attacks, offline password guessing, or ticket forging due to weaker encryption.
  • Lack of Encryption: Without supplementary encryption layers, data transmitted may be susceptible to eavesdropping and man-in-the-middle attacks.
  • Unpatched Legacy Systems: Older implementations may have unpatched vulnerabilities that can be exploited, especially if exposed beyond trusted networks.

Common Mitigations:

  • Decommission Legacy Protocols: Migrate to Kerberos V5 or alternative secure authentication and file transfer mechanisms.
  • Restrict Network Access: Use internal firewalls and ACLs to limit exposure of port 750 to trusted systems only.
  • Encryption: Employ network-level encryption (e.g., IPSec, VPNs) if legacy services must operate.
  • Update and Patch: Ensure any legacy systems are fully patched and monitored for anomalies.
  • Segmentation: Isolate legacy authentication services to minimize potential lateral movement if compromised.

Related Ports

all 216 in security →

the 8 most looked-up other ports in security — 216 ports carry that label.

portservicerisk
:8881Atlasz Secure Servercaution
:443HTTPScaution
:8291Winbox MikroTik Admincaution
:3268Microsoft Global Catalog (GC)caution
:135Microsoft EPMAPcaution
:3128Squid Proxy HTTPcaution
:8080HTTP Alternatecaution
:7000Vuze HTTPS Trackercaution

risk mix of the 8 listed

  • caution100%

3 of 8 encrypted