BEGINNER · 10 MIN · FREE LESSON
Cryptographic hash functions
Explore cryptographic hash functions through a visual, step-by-step model.
Loading interactive lesson…
BEGINNER · 10 MIN · FREE LESSON
Explore cryptographic hash functions through a visual, step-by-step model.
Loading interactive lesson…
Use {"text":"hello","byte":0}. Flip one low bit of one UTF-8 input byte and compare actual SHA-256 outputs. This demonstrates avalanche, not a proof of security.
One input bit changes before two real SHA-256 computations.
SHA-256 processes fixed-size blocks and emits 256 bits. A fixed-length digest cannot uniquely encode every input; collision resistance is a computational property, not an absence of possible collisions.
Input bytes hashed by two digests, seed 42. Plotted sample sizes respect each lesson’s explicit input limits.
Keyboard: Space play/pause · ←/→ step · R restart · 1–5 speed. Reduced motion disables transitions.
A cryptographic fingerprint is deliberately sensitive to changes anywhere in its input.
Change one bit. Compare the whole digest. The inputs are examples, never application secrets. Public fixed fixtures make repeated traces deterministic.
Predict the verification outcome or modular-arithmetic decision. Toggle tampering or change the input, then explain why the observed result changes.
O(n) input hashing and fixed-size digest state. Library calls perform real cryptographic operations; the trace illustrates protocol-level stages rather than claiming to animate every internal cipher round. Big-integer and curve costs depend on security parameters.
Node.js uses its standard crypto/TLS libraries. Python AES/Ed25519 references require the maintained cryptography package; other Python references use the standard library. Java uses JDK cryptography/TLS APIs. C++ references require OpenSSL headers and linking libcrypto/libssl where used. Textbook RSA and tiny-group DH snippets are explicitly insecure mathematical demonstrations.
Use standard cryptographic hashes for integrity constructions and established protocols, with authentication where required.
A digest is not encryption. Avalanche examples do not prove preimage or collision resistance.
Distinguish confidentiality, integrity, identity and the limits of a demonstration.
MAKE IT STICK
Progress saves on this device and merges with your account after sign-in.
0 / 5000 · Saved on this device; synced when signed in.