Morse Code and Caesar Ciphers Are Fun, Not Secure
What classic ciphers were actually built for, why a Caesar shift can be broken by hand in seconds, and where these tools are genuinely still useful.
Published March 14, 2026
Morse code and the Caesar cipher both get mistaken, occasionally, for ways to keep something secret. Neither was built for that, and neither holds up as one today. Understanding what they were actually built for makes it obvious why, and also why they're still genuinely useful for the very different things they're actually good at.
What Morse code is actually for
Morse code exists to transmit text over a channel that can only reliably send two states, on and off, like a telegraph click or a radio tone. It's an encoding, not a cipher: anyone who knows the standard mapping (which is public and has been for well over a century) can read it instantly. Its entire design goal was reliability over a noisy channel, not secrecy, which is why SOS specifically was chosen for being simple and unmistakable, three dots, three dashes, three dots, easy to send and recognize even under bad conditions.
Why a Caesar cipher falls apart instantly
A Caesar cipher shifts every letter by a fixed amount, and there are only 25 possible shifts (26 minus the no-op shift of 0). That's small enough to brute-force by hand: try all 25 shifts on a short piece of ciphertext and one of them will produce readable text. No computer required, no real effort, just persistence for a couple of minutes.
ROT13, a shift of exactly 13, isn't even trying to be secure. Its actual use case is different: it's a convention for temporarily hiding spoilers or punchlines in forum posts and puzzle answers, where the goal is "don't show this to my eyes until I choose to decode it," not "prevent anyone from ever reading this." That it's its own inverse (apply it twice and you're back to the original) is exactly what makes it convenient for that specific, low-stakes job.
Where these tools are genuinely still useful
Morse code shows up in amateur radio, some accessibility contexts, and as a teaching tool for encoding concepts generally. Caesar ciphers are a standard first lesson in cryptography courses specifically because they're breakable, they teach the core ideas (plaintext, ciphertext, key space, brute-force attacks) without needing real cryptographic machinery. Neither belongs anywhere near an actual secret. For that, use encryption designed and vetted for the job, AES for data at rest, TLS for data in transit, not a 19th-century telegraph code or a shift cipher a computer can crack before you finish typing the ciphertext.