We use a Bit-Walk algorithm to expand 256 bits into a 2D path. This visualization acts like a Digital Fingerprint.
⚠️ The Birthday Paradox & Shannon Score: In only 32 bytes, there is an 86% chance of repeating bytes. A Shannon Score near 3.7 is often safer than 4.0, as "perfectly unique" keys in small samples often suggest non-random whitening or human intervention.
ℹ️
About Detection Limits
This visualizer can reliably flag low‑entropy keys,
patterned keys,
ramp‑style sequences,
and biased or human‑generated keys.
These contain strong structural fingerprints that appear even in a single 32‑byte sample.
However, it cannot reliably detect keys produced by
weak PRNGs (like Math.random()) or
LCG‑based generators from a single key alone.
These generators can still output individual keys that look statistically normal at 32 bytes,
even though the generator itself is insecure.
In other words: this tool detects structural anomalies in the key,
not the full strength of the underlying RNG.
Technical Requirements
256 × (Shannon/4) × (1 - |SCC|²) × Χᵖᵉⁿᵃˡᵗʸ ≈ (Σ bits)
Adjusting for Serial Correlation & Distribution Bias
⛔
“BAD KEY” Does Not Mean “Easily Crackable”
A key flagged as BAD is not weak in the brute‑force sense —
even a 100‑bit effective key is astronomically large. Instead, it means the key shows
structural anomalies that should never appear in high‑quality cryptographic material.
These anomalies can sometimes hint at a biased or misconfigured RNG, but
a single key is not enough to diagnose the generator itself.
Some insecure generators (like Math.random() or LCGs) can still produce individual keys
that look perfectly normal at 32 bytes.
LINUX KERNEL STATUS
Entropy Pool Check: 256 = FULL (Kernel 5.10+)
cat /proc/sys/kernel/random/entropy_avail
Starvation Remedy: