What Telnet is

Telnet is a protocol for bidirectional, byte-oriented communication between terminals and terminal-oriented processes. It is one of the oldest protocols still documented on the internet: the current specification, RFC 854, dates to 1983, and the idea is older than that.

The job it was built for: you sit at a terminal in one place, and a computer you want to use lives somewhere else. Telnet carries your keystrokes to that machine and its output back to your screen, over a TCP connection.

The word Telnet is also used for client programs that implement the protocol. On most systems that program is literally called telnet:

telnet 192.0.2.20

This double meaning causes real confusion, so let’s settle it now. This distinction matters. You can use a Telnet client to connect to a different text protocol, but that does not turn the other protocol into Telnet. When someone says “just telnet to port 80”, they mean using the client as a generic tool. The web server on the other side has never heard of Telnet.

What the protocol provides

Telnet was designed for interactive remote terminals, connecting machines from different vendors that shared almost nothing. It provides three things: a common terminal model, so two different systems agree on what a “terminal” is; control commands, like interrupting a running process; and a way to negotiate optional behavior between two different systems, so capable clients and servers can agree on extras without breaking simple ones.

Each of these gets its own lesson in this module. Together they are the actual protocol, as opposed to the raw TCP connection underneath.

Why learn it in 2026

Nobody should use Telnet to log into machines anymore, and this course will be blunt about why: everything travels unencrypted, and SSH replaced it decades ago.

But as a learning tool, Telnet is hard to beat. The protocol is readable enough to study by hand. You can type it, read its responses, and watch its control bytes in a hex dump. It is therefore a useful way to learn how application protocols sit inside a TCP connection, even though Telnet is not a safe choice for remote login on an untrusted network.

Learn it as anatomy, not as a tool for production access.