Why passwords are stored as hashes
A one-way scrambled value made from a password. A system stores it instead of the real password and checks a login by hashing what you type and comparing. It can't be reversed.
Understanding Why passwords are stored as hashes in Years 9–10 Digital Systems
What it does: Hashing the same password twice produces an identical value, which is why a login check by comparing hashes works. Hashing is one-way. A stolen hash can't be turned back into the password, so the thief only gets scrambled values (though they might still try to guess passwords). If the hashes don't match, the password typed is not the one that was originally set. Even a small change to the input gives a very different hash.
Common mistakes: The system should store the hash of the password, not the real password. It should be stored ← hash(password), so a stolen database does not reveal real passwords. This hashes the username instead of the password. The password is what needs protecting, so it should be stored ← hash(password).
Free printable worksheet with full answer key — or add this module to a class and your students practise it interactively.
This module's key terms are also in a printable crossword (Modules 13–24) and word search (Modules 13–40).
Take this worksheet further — free with Cloodit
Each concept is reinforced from every angle — learned, then applied, then tested.
Cloodit turns curriculum-aligned coding content into journeys students work through one biome at a time.
Over 100 of them, across seven natural biomes.
Turns their work into revision material ready for Flash Cards and Exam study.
Live, competitive practice for the start of the lesson or a teacher-led lesson finisher.
Honour your top performers, or encourage a student who's trying hard — ready to print in seconds.
Quick Questions
Match the Pairs
Key Term
hashFill in the Blanks
Spot the Error
Student with a class code? Join your class →