ShareYourGroupShareYourGroupSubnet and Ports

Remote access ports: SSH 22, Telnet 23, RDP 3389 and VNC 5900

What the IANA registry records for these ports, and how to use them safely.

What IANA records

PortProtocolsRegistered nameIANA descriptionAssigneeReferenceNote
22tcp, udp, sctpsshThe Secure Shell (SSH) Protocoln/a[RFC 4251]Defined TXT keys: u=<username> p=<password>
23tcp, udptelnetTelnetJon Postel[RFC 854]Defined TXT keys: u=<username> p=<password>
3389tcp, udpms-wbt-serverMS WBT ServerJordan Marchesen/a
5900tcp, udprfbRemote FramebufferTristan Richardson[RFC 6143]

Why this group matters most

Remote access ports let someone control a computer from far away, which makes them valuable to attackers. Servers that have SSH or Remote Desktop open to the internet are tried by automated password guessers within minutes of going online.

The ports

Safe habits

  1. Do not expose these ports to the whole internet. Allow only your own address, or put them behind a VPN.
  2. Use keys or strong passwords plus two-step verification. For SSH, use key-based login and turn off password login.
  3. Keep the software updated. Remote access services have had serious security flaws.
  4. Consider a different port only as a small extra: changing the port reduces noise in logs, but it is not security.
  5. Log and watch failed logins. Many failed attempts in a short time mean someone is guessing.

If you must support a home user

Use a tool that makes an outgoing connection and requires the user to accept (so no inbound port is open) instead of opening 3389 on a home router.

This is an independent guide. It is not connected with IANA, the IETF or any network equipment maker. Address and port data come from the IANA registries as fetched on 14 November 2026; RFC texts were read from rfc-editor.org. Check the originals for anything you rely on.