Cryptographic Nonce, Salt & IV Generator
Generate cryptographically secure random nonces, salts, and IVs across Hex, Base64, and code arrays using CSPRNG.
Nonce Specifications
Why Cryptographic Nonce Uniqueness is Critical
In authenticated encryption modes like AES-GCM and ChaCha20-Poly1305, reusing a nonce with the same key is a catastrophic cryptographic vulnerability (known as the nonce-reuse catastrophe).
Reusing an IV reveals the XOR difference between plaintexts and allows an adversary to forge authentication tags. Utilizing true CSPRNG hardware entropy guarantees that every generated nonce remains statistically distinct.
Frequently Asked Questions
What is the standard IV length for AES-GCM?
NIST SP 800-38D specifically recommends 12 bytes (96 bits) for AES-GCM. Using other lengths requires an internal GHASH computation, degrading performance.
Does a nonce need to be kept secret?
No. Nonces and initialization vectors do not need to be secret; they can be transmitted openly alongside the ciphertext. However, they must be unique for each encryption operation under the same key.