whatportis.com
suggest an edit →

Port 5800VNC over HTTP

Port 5800 is commonly used to access Virtual Network Computing (VNC) remote desktop interfaces over HTTP. This facilitates browser-based connections to remote systems, enabling users to manage another computer’s desktop environment through a web interface without needing dedicated client software..

inWeb ServicesRemote Access
transport
tcp

single transport

in transit
cleartext

payload readable on path

assignment
unofficial

used by convention

risk
4/10

caution

lookups
30,308

rank 37 of 993 · top 4%

Technical Details

what runs on :5800

Port 5800 is primarily associated with VNC (Virtual Network Computing) operating over HTTP. Typically, a VNC server runs on port 5900 and adjacent ports, but when integrated with an HTTP server or Java-based applet delivery, it uses port 5800. This enables connecting to a remote desktop directly via a web browser embedding a Java VNC client, facilitating ease of access without the need for installing any software.

In technical terms, the HTTP server on port 5800 serves the Java applet or HTML5 client code to the user’s browser. Once delivered, the applet establishes a separate connection (normally on port 5900) to relay VNC protocol commands between client and host. This design abstracts the initial connection in a way that traverses network restrictions, leveraging the ubiquity of HTTP.

Because of this browser-accessible setup, administrators often configure port forwarding and NAT rules to expose port 5800 selectively. This use case is common in remote support, system administration, and remote access scenarios where deploying a standalone VNC client might be impractical or impossible.

Security Information

exposure of :5800

risk score

4/ 10caution

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

web services averages 3.9 across 112 ports — this one sits 0.1 above.

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

every listening transport is another surface to filter at the edge

security overview

Common vulnerabilities:

  • Port 5800 is frequently targeted due to insecure default configurations, such as weak or missing authentication on the hosted web applet.
  • Serving the VNC interface over unencrypted HTTP can expose credentials, session data, and control commands to interception (sniffing or man-in-the-middle attacks).
  • Web-based VNC access might be susceptible to cross-site scripting (XSS) and session hijacking if proper security controls are not enforced.
  • Attackers may leverage open port scans to identify accessible VNC instances for brute-force credential attacks.

Common mitigations:

  • Always secure VNC connections with encryption, preferably via SSH tunneling, VPN, or by enabling TLS/SSL support if the VNC server supports it.
  • Restrict access via firewalls or access control lists to trusted IP addresses only.
  • Apply strong authentication mechanisms, enforce strong password policies, and consider multi-factor authentication.
  • Regularly update and patch VNC server software and associated web services to close known vulnerabilities.
  • Disable HTTP-based access when not required, or replace it with secure alternatives.

Related Ports

all 112 in web services →

the 8 most looked-up other ports in web services — 112 ports carry that label.

portservicerisk
:8888Sun Answerbook & Alt HTTPcaution
:8000Intel Remote Desktop / Alternate HTTP Portsafe
:8888NewsEDGEcaution
:8888HTTP Alternative Portcaution
:8888GNUmp3d Streaming HTTPcaution
:9080Groove RPCcaution
:8881Atlasz Secure Servercaution
:80HTTPcaution

risk mix of the 8 listed

  • safe13%
  • caution88%

0 of 8 encrypted