Repository navigation
Building Your Own Alphabet
Last reviewed: 2026-10-02
Important
Historical and educational content. Nothing in this section is secure for real data. For protecting information, use the modern algorithms in algorithms.md and applied-crypto.md.
โ Classical Ciphers ยท ๐ Classical Index ยท Cryptanalysis โ
Construction methods, keyed alphabets, homophonic substitution, and a design checklist.
Every alphabet in this guide is built from one or more of the methods below. Combine them to create your own.
| Method | How it works | Example |
|---|---|---|
| Shape similarity | Pick a glyph that looks like the letter |
Eโ3, Aโ/-\
|
| Phonetic | Pick something that sounds like it |
Fโph, Xโks, Qโkw
|
| Positional / numeric | Use the letter's index or coordinates | A1Z26, Polybius |
| Geometric / mirror | Rotate, mirror or reverse the alphabet | Atbash, upside-down text |
| Keyed alphabet | A keyword (duplicates removed) starts the cipher alphabet | Keyword cipher (below) |
| Homophonic | Frequent letters get several symbols |
E โ 17, 42 or 88 at random |
| Code-point swap | Same letter, different Unicode block | Fraktur, fullwidth |
| Binary/steganographic | Two states hide five bits per letter | Baconian (bold/italic, upper/lower) |
| Layering | Apply two or more methods in sequence | Atbash, then leet |
Write a keyword, drop repeated letters, then append the remaining letters of the alphabet in order. With keyword ZEBRAS:
| Plain | A | B | C | D | E | F | G | H | I | J | K | L | M |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Cipher | Z | E | B | R | A | S | C | D | F | G | H | I | J |
| Plain | N | O | P | Q | R | S | T | U | V | W | X | Y | Z |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Cipher | K | L | M | N | O | P | Q | T | U | V | W | X | Y |
ATTACK AT DAWN โ ZQQZBH ZQ RZVK
The weakness of every one-for-one alphabet is that it preserves letter frequency (see Breaking Simple Substitution). Homophonic ciphers counter this by giving common letters multiple symbols in proportion to their frequency. For example, E (โ13%) might get 13 different symbols while Z gets one. The ciphertext frequency then looks nearly flat.
-
Reversibility: Can every symbol be decoded to exactly one letter?
1meaning bothIandL(and|3vs13) creates ambiguity. That is acceptable for leet, but not for a cipher. -
Tokenization: Multi-character symbols (
|-|,|\/|) need separators, or a decoder cannot tell where one letter ends. - Rendering: Test on GitHub, Discord and mobile. Some Unicode characters are missing from common fonts and show as boxes (tofu).
-
Markdown safety:
|,*,_,`and\all have meaning in Markdown. Inside GitHub tables, every|must be escaped as\|, even inside code spans. - Normalization survival: Decide whether you want the text to survive Unicode NFKC normalization (see Filter Evasion and Normalization).
โ Classical Ciphers ยท ๐ Classical Index ยท Cryptanalysis โ
- ciphers.md - the classical systems these methods come from
- cryptanalysis.md - test your design against frequency analysis
โฌ ๏ธ Back to Master Index | ๐ฏ Role Navigation | Legal Notice
๐ Source: Cryptography/Classical/build-your-own.md | โ๏ธ Suggest an edit | โฌ
๏ธ Back to Cryptography
- ๐บ๏ธ Browse by Topic
- ๐ All Repository Files
- ๐งญ Learning Paths
- ๐ Master Guide
- ๐ค Glossary
- โ๏ธ Legal & Disclaimer
๐ Foundations & Learning
๐ก๏ธ Defense & Investigations
- Incident Response
- Open Source Intelligence (OSINT)
- Reverse Engineering
- Operations Security (OPSEC)
- Compliance
โ๏ธ Platforms & Infrastructure
๐ก Hardware, Wireless & Field Projects
- PNWC Cyberdeck
- Hardware Testing
- Hardware Hacking
- Software-Defined Radio
- Wardriving
- uConsole
- Space Security
๐งฐ Assessment & Field Reference
๐ฆ Downloads & Project Resources
๐๏ธ Additional Topics