> For the complete documentation index, see [llms.txt](https://docs.gotempest.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gotempest.app/connect-to-servers/connect-to-telnet-servers.md).

# Telnet Client for macOS, Windows & Linux

Tempest works as a **Telnet client** for routers, switches, embedded devices, and legacy systems — same tabbed UI, same color schemes, same SSH-style connection list. As of Tempest 3.6+, the Telnet protocol is **fully native** (Rust implementation, no external `telnet` binary required) on **macOS, Windows, and Linux**.

If you're managing Cisco gear, MikroTik routers, factory PLCs, or anything else that still speaks Telnet, Tempest gives you a modern terminal experience without losing the ability to talk plain Telnet.

## Add a Telnet connection

1. Click `+` to add a new connection.
2. Choose **Telnet** as the protocol.
3. Set host and port (default: `23`).
4. Optional: configure proxy (HTTP CONNECT, SOCKS5, or ProxyCommand) for Telnet over a tunnel.
5. Click Connect.

The session opens in a tab. Encoding, color, and copy/paste behave identically to SSH tabs.

## Why native Telnet?

Older versions of Tempest shelled out to the system's `telnet` binary, which is no longer installed by default on macOS Sonoma+ or modern Windows. The native Rust implementation works out of the box on every platform — no `brew install telnet`, no Windows feature toggle.

## How to use Telnet on macOS (the `telnet` command was removed)

Apple removed the built-in `telnet` command in macOS 10.13 High Sierra and it never came back — on a modern Mac, typing `telnet` in Terminal prints `command not found`.

The fastest fix is Tempest: Telnet support is built in (native Rust implementation — nothing to install), so you just [download Tempest for macOS](https://gotempest.app/download/mac?utm_source=docs\&utm_campaign=telnet), add a Telnet connection with your host and port, and connect. Instead of a bare prompt you get tabs, saved connections, color schemes, and proxy support — with the same connection list synced to Windows, Linux, and your phone.

If you specifically want the classic command-line client back:

* `brew install telnet` restores it via Homebrew (or `brew install inetutils` for the full GNU network tools).
* `nc -vz <host> 23` ships with macOS and works for checking whether a Telnet port is open — but netcat doesn't negotiate Telnet options, so interactive sessions with network gear can misbehave.

Windows is similar: the optional "Telnet Client" feature is off by default on Windows 10/11, which is why a client that speaks Telnet natively saves a trip through Windows Features.

## Security note

Telnet sends passwords and session data in cleartext. Use SSH whenever possible. Telnet is appropriate for:

* Legacy device management on isolated networks
* Initial bootstrap of devices that only support Telnet
* Reaching equipment behind a tunnel that you trust

For production access, [combine with a proxy or jump host](/connect-to-servers/ssh-jump-host-bastion-chaining.md) so the cleartext segment stays inside a trusted boundary.

## See also

* [SSH Port Forwarding](/connect-to-servers/ssh-port-forwarding.md) — wrap Telnet inside an encrypted SSH tunnel
* [Connect to Game Servers via RCON](/connect-to-servers/ssh-jump-host-bastion-chaining.md) — the same Rust implementation also powers Tempest's RCON support