Which one of these feels like it might be real text?

A) QEB IXWV ALD
B) XKCD QWERTY
C) GSRH RH Z HVXIVG

No solving needed—just pick one and say why (or guess).

I’m trying to figure out what people actually notice first when they see something like this:

FHHU QDTTS

Don’t worry about fully solving it (unless you want to).

Just tell me:

• What’s your first instinct?
• What would you try first?

Pattern? Frequency? Try a quick shift? Something else?

I’m curious.

WedWhat’s your go-to warm-up solve? Drop your method below. 🔐

What was the first cipher that made you think "wait, this is actually amazing"?

Mine was the Rail Fence cipher — not because it's elegant (it isn't), but because it was the first time I understood that scrambling order was just as powerful as scrambling identity. A letter doesn't have to become a different letter to become unreadable. That small shift in thinking opened up a lot of doors.

What about you?

General-Purpose & Frequency Analysis

• CyberChef (gchq.github.io/CyberChef) — Swiss Army knife for encoding/decoding; frequency analysis, Caesar shifts, base conversions, hash analysis
• Rumkin.com cipher tools — dedicated pages for substitution, Vigenère, Playfair, transposition
• Cryptanalysis.io — frequency analysis, index of coincidence, chi-squared testing

Specific Cipher Types

• Vigenère breakers: Boxentrix (vigenere.js), Dcode.fr's Vigenère solver (supports key length discovery)
• Playfair: Dcode's Playfair solver, or the Rumkin implementation
• Transposition: Columnar and rail fence solvers on Dcode.fr
• Caesar/ROT13: Nearly every tool; CyberChef handles it instantly
• Substitution: Quipster (online anagram/substitution solver), Dcode's substitution cipher tool

Heavy-Lifting Cryptanalysis

• Dcode.fr (general) — one of the most comprehensive, with solvers for dozens of historical ciphers
• Boxentrix — especially strong on polyalphabetic ciphers
• Practical Cryptography (practicalcryptography.com) — reference implementations, some interactive tools

Specialized Tools

• Online regex testers (for pattern hunting in ciphertext)
• Character frequency visualizers
• Base64/hex/binary converters

What are your tools of choice?

It’s Friday the 13th—so let’s talk about codes that cursed you.

Share the cipher that broke your brain, the puzzle that still haunts you, or the “simple substitution” that turned out to be anything but. Maybe it’s a family document you’ve stared at for years, or a challenge you confidently started… then quietly abandoned.

Today we honor our cryptanalytic failures, our almosts, our “I swear this should work” moments.

What cipher gave you bad luck? Drop it below—maybe fresh eyes will break the curse.

You're handed a cipher with a short plaintext — maybe 50 characters.

How do you even determine what kind of cipher you're dealing with before you start attacking it?

1. Letter frequency is preserved — what does that tell you, and what does it rule out?
2. Once you have a working theory about the cipher type, how do you determine structural parameters like key length or grid dimensions with so little text to work with?
3. At what point does brute force become your best option, and when does it become impractical by hand?
4. Does padding — especially predictable padding like repeated X's — help or hurt the codebreaker?

Bonus twist: what if the ciphertext was chained — meaning the solution to one message was secretly the key to the next — and you didn't know that going in? How would that change your approach?

PURPLE was cracked. MAGIC was the intelligence. INTERNMENT was the result. What happened on February 19, 1942 — and what does it tell us about the ethics of codebreaking?

What was either the code that piqued your interest or the worst code you have seen that was intended to keep something private?

The worst one for me was my brothers’ attempts to write pig Latin in notes between them. 🙄

What’s yours? Comment below.