Twelve free classical cipher tools: Caesar, Vigenere, substitution, Playfair, Hill, XOR, Rail Fence and more, plus an identifier for unknown ciphertext.
The Cipher Suite is the index to every classical encryption tool on the site — twelve interactive encoders, decoders, and cryptanalysis aids covering the ciphers that appear in cryptography courses, Capture The Flag competitions, escape rooms, geocaches, and printed puzzle books. Each one runs entirely in your browser, is free and unlimited, and shows its working rather than just its answer.
This page exists because “which cipher do I need?” is usually the hard part. If you already know, jump straight to the tool. If you have a block of ciphertext and no idea what produced it, start with the cipher identifier, which analyses the statistical fingerprint of the text — character set, index of coincidence, letter distribution, repeated patterns — and ranks the likely candidates.
| Cipher | Type | Keyspace | Recognisable by |
|---|---|---|---|
| Caesar | Monoalphabetic shift | 25 keys | English letter frequencies, shifted intact |
| ROT13 | Caesar with shift 13 | 1 key | Self-inverse; applying it twice returns the original |
| Atbash | Reversed alphabet | 1 key | A↔Z, B↔Y; also self-inverse |
| Affine | Modular arithmetic | 312 keys | Frequency profile preserved but not simply shifted |
| Substitution | Arbitrary letter mapping | 26! (≈10²⁶) | Word patterns and doubled letters survive |
| Vigènere | Polyalphabetic, keyword | 26ⁿ | Flattened frequencies; repeats at key-length intervals |
| Beaufort | Polyalphabetic, reciprocal | 26ⁿ | Like Vigènere but encoding and decoding are the same |
| Playfair | Digraph substitution | 25!/2 arrangements | Even length, no doubled pairs, no J |
| Hill | Matrix / linear algebra | Invertible n×n matrices mod 26 | Flat letter frequencies, length a multiple of the block |
| Rail Fence | Transposition | n−1 keys | Letter frequencies exactly match plain English |
| XOR | Bitwise, binary | Key-length dependent | Non-printable bytes; hex or base64 presentation |
| One-Time Pad | Perfect secrecy | Key as long as the message | Uniform distribution; genuinely unbreakable if used correctly |
Two support tools round out the set: the cipher identifier for working out what you are looking at, and the encoding chain analyzer for text that has been through several layers of encoding rather than encryption.
Almost every classical cipher falls into one of two families, and telling them apart takes ten seconds with a letter count.
Substitution replaces characters with other characters. Letter frequencies change — either shifted (Caesar, Atbash, affine), scrambled (substitution), or flattened (Vigènere, Playfair, Hill). Caesar, ROT13, Atbash, affine, substitution, Vigènere, Beaufort, Playfair, and Hill are all substitution ciphers of one kind or another.
Transposition keeps every character and rearranges the order. The letter frequency distribution is identical to plain English — roughly 12.7% E, 9.1% T, 8.2% A — which is the giveaway. Rail Fence is the example here: if a ciphertext looks statistically like English but reads like nonsense, you are looking at a transposition, and no amount of substitution analysis will help.
Encoding is neither. Base64, hexadecimal, URL encoding, and Morse code have no key and provide no confidentiality; they change representation, not secrecy. Anyone who recognises the format can reverse them. Puzzle chains frequently stack encodings on top of a cipher, which is what the encoding chain analyzer is for.
+/=? Probably Base64. Non-printable bytes or hex pairs? Likely XOR or a binary encoding.None of them is secure, and that is the point. Each was broken by a specific technique, and those techniques are the foundation of modern cryptanalysis:
For anything that needs to protect real data, use modern authenticated encryption — AES-GCM, ChaCha20-Poly1305, or a vetted library that chooses for you. Classical ciphers belong in classrooms, competitions, and puzzles.
If you know the cipher, go straight to it from the table above. If you do not, use the cipher identifier — it examines the ciphertext’s statistics and ranks the likely candidates rather than making you guess.
No, with one theoretical exception. Every cipher here except the one-time pad is broken by well-known techniques, most of them in seconds on a laptop. The one-time pad is provably secure but only under conditions — truly random key, key as long as the message, never reused, securely distributed — that are impractical for ordinary use.
No. Every cipher tool in the suite runs entirely in your browser using JavaScript. Nothing is uploaded, stored, or logged.
A cipher uses a key to provide confidentiality; without the key you cannot recover the plaintext. An encoding — Base64, hex, URL encoding, Morse — has no key and provides no confidentiality at all; it only changes how data is represented. Base64 is not encryption.
Because a monoalphabetic substitution preserves the structure of the language: E is still the most common letter, it is just wearing a different mask. The attacker never searches the keyspace — they read the statistics off the ciphertext and reconstruct the mapping letter by letter. Keyspace size is necessary for security but nowhere near sufficient.
Caesar and ROT13 in warm-up rounds, then XOR (often with a repeating key), Vigènere, and substitution in the middle tiers. Playfair, Hill, and Rail Fence turn up in puzzle-heavy events. Multi-layer challenges usually wrap the result in Base64 or hex, which is where the encoding chain analyzer earns its place.
Once a tool page has loaded it runs without network access, since all computation is local. There is no installation, no account, and no rate limit.
Modern symmetric cryptography — block ciphers, modes of operation, and authenticated encryption — then public-key cryptography and hashing. The classical ciphers here are the vocabulary: plaintext, ciphertext, key, keyspace, cryptanalysis. Everything modern is built on the failures they demonstrate.
A cipher suite is a named combination of cryptographic algorithms that together secure a network connection. When a client and server establish a TLS (Transport Layer Security) connection, they negotiate which cipher suite to use. This negotiation determines the algorithms for key exchange, authentication, bulk encryption, and message integrity — the four pillars of a secure connection.
Cipher suites are central to HTTPS, email security (SMTPS, IMAPS), VPN connections, and any protocol built on TLS. Choosing the right cipher suites directly impacts your security posture, compliance status, and compatibility with clients and browsers.
During the TLS handshake, the client sends a list of supported cipher suites in order of preference. The server selects the highest-priority suite it also supports. If no common suite exists, the connection fails.
A TLS 1.2 cipher suite name encodes four algorithm choices:
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
| Component | Algorithm | Purpose |
|---|---|---|
| Key Exchange | ECDHE | Establish a shared secret using Elliptic Curve Diffie-Hellman Ephemeral |
| Authentication | RSA | Verify the server's identity using its certificate |
| Encryption | AES_256_GCM | Encrypt application data with AES-256 in Galois/Counter Mode |
| MAC/Hash | SHA384 | Ensure message integrity (built into GCM for AEAD suites) |
TLS 1.3 simplified this by fixing the key exchange to ephemeral Diffie-Hellman variants and using only AEAD ciphers, reducing the cipher suite name to just the AEAD algorithm and hash:
TLS_AES_256_GCM_SHA384