Scenario
A code comment says Gur cnffjbeq vf abg urer. It has normal word lengths, normal punctuation, and English-looking letter frequency — the signature of ROT13, the 13-place Caesar shift that forums and old codebases use to hide spoilers and joke strings. Because 13 is half the alphabet, applying the same shift again decodes it, so recognizing the pattern is most of the work.
Broken input
Gur cnffjbeq vf abg urer
Goal
Use ROT13 / Caesar Cipher to decode the text and confirm it becomes readable English. If ROT13 produces gibberish, the tool's other Caesar shift amounts let you test the remaining 24 rotations quickly.
Tool sequence
- Open ROT13 / Caesar Cipher.
- Paste the suspicious text and apply ROT13 — the default shift of 13.
- Read the output:
The password is not here. Casing and punctuation pass through untouched, which is why the sentence shape was visible before decoding. - If the first pass had produced nonsense, step through other shift values instead of assuming the text is encrypted.
- If the string still resists, it may be encoded rather than shifted — try Base64 Encoder before escalating.
Checkpoint output
Gur cnffjbeq vf abg urer
→ The password is not here
One ROT13 pass yields plain English, confirming the comment was obfuscated, not encrypted.
Common mistakes
- Calling ROT13 secure encryption — it is a fixed, keyless letter substitution anyone can reverse.
- Applying multiple shifts without tracking which one produced readable text.
- Changing punctuation or digits that ROT13 should pass through unchanged.
- Missing that a double-ROT13 round trip returns the original, so "encoding it twice for safety" does nothing.
Related tools and lessons
- Morse Code Translator - Translate text to and from Morse code.
- Base64 Encoder - Encode or decode Base64 strings.
- SHA-256 Generator - Hash text with SHA-256.
- Related lesson: Decode a Morse Message and Check the Spacing
- Related lesson: Tell Encoding, Escaping, Hashing, and Encryption Apart