Home/Port Lookup/Port 3389
Network port detail · TCP/UDP
3389
ms-wbt-server
[ 01 ] — Context

About port 3389.

Updated  ·  Confidence: High

Port 3389/tcp is the IANA-assigned home of Microsoft's Remote Desktop Protocol and one of the most-attacked ports on the internet. RDP provides graphical remote access to and control of Windows desktops and servers, transmitting screen images, keystrokes, and mouse input between the client (mstsc.exe) and the Remote Desktop Services host; it is an extension of the ITU-T T.128 application-sharing protocol and supports Network Level Authentication (NLA), encryption, multi-monitor, and clipboard/printer/audio redirection. The IANA service name is ms-wbt-server ("MS WBT Server", contact Jordan Marchese, Microsoft; both 3389/tcp and 3389/udp are officially registered), but the registry cites no RFC — the protocol is documented in Microsoft's open MS-RDPBCGR specification series. Two security facts dominate the picture. First, BlueKeep (CVE-2019-0708) is a wormable, pre-authentication remote-code-execution flaw in Remote Desktop Services on legacy Windows, patched in May 2019 and the subject of CISA advisory AA19-168A and an NSA advisory. Second, exposed RDP is a relentless brute-force target and a leading ransomware initial-access vector — Sophos observed roughly two million failed logins across 999 source IPs over fifteen days in one study. For an analyst, an open 3389/tcp is RDP exposure and a high-risk finding when internet-facing: verify NLA is enforced, check the patch level for BlueKeep, review brute-force/lockout logs, and confirm whether the service should sit behind a VPN or RD Gateway rather than be public.

IANA assignment
ms-wbt-server — "MS WBT Server"; reference (blank — no RFC cited in IANA registry); governing spec Microsoft MS-RDPBCGR (not the IANA-cited reference); contact Jordan Marchese (Microsoft), modified 2022-11-03 [IANA-assigned] — IANA Service Name and Transport Protocol Port Number Registry
Range class
registered (1024–49151) — User Ports / Registered Ports range per RFC 6335 §6 [IANA-assigned] — RFC 6335, IANA registry header
Primary use
Microsoft Remote Desktop Protocol — graphical remote access/control of Windows hosts; both TCP and UDP 3389 registered (UDP added for media/high-latency performance) [Well-established] — Microsoft docs, Wikipedia (RDP)
Other/unofficial uses
xrdp (open-source RDP server for Linux); registry-based port relocation (security-through-obscurity defeated by scanners) [Community-reported] — Microsoft docs
Prevalence
nmap-services open-frequency 0.083904 (a very common open TCP port, typically top ~10) [Well-established] — nmap-services file
Security implications
BlueKeep (CVE-2019-0708) wormable pre-auth RCE on legacy Windows (patched May 2019); relentless brute-force/credential-stuffing (~2M failed logins/999 IPs/15 days, Sophos); leading ransomware initial-access vector. Mitigate: never expose 3389 directly; VPN + MFA or RD Gateway; enforce NLA, lockout, strong passwords; patch [Well-established/Threat-reported] — CISA AA19-168A, NSA, Sophos, Reposify
Typically seen on
Windows servers, RDS/VDI hosts, cloud Windows instances, workstations, MSP-managed systems
Related ports
22 SSH (Unix/Linux remote-admin equivalent); 5900 VNC; 23 Telnet; 3389/udp
Analyst note
Open 3389/tcp = RDP exposure and a high-risk finding when internet-facing. Verify NLA is enforced, check patch level for BlueKeep, review brute-force/lockout logs, and confirm whether it should be behind a VPN/gateway rather than public.