Home › Guides › Utilities & Developer Tools
Part of the CalcProMaster guides library · Text, codes & security
Utility tools deserve one explanation each: what a UUID actually guarantees, why password strength is entropy rather than length theatre, and when a hash is a fingerprint versus a password. These guides cover the concepts the tools rely on.
Methodology: Standard utility formulas such as energy use, cost per unit and efficiency, using published tariffs as inputs only.
Security utilities are honest when the limits are stated. A random UUIDv4 carries 122 random bits — collision odds across a billion UUIDs are roughly one in a quintillion, so you will never see one. Password entropy is bits = log2(pool size) × length: 16 lowercase letters give about 75 bits; 8 characters from the full keyboard give about 52. Length wins because the formula multiplies, not adds.
Hashes are for verifying data, not for storing passwords: a hash is fast by design, which is exactly what an attacker wants. That is why the password tools generate client-side with cryptographically secure randomness and never transmit anything — the tool’s honesty is in what it refuses to do, not just what it computes.
Entropy math, pool sizes and honest crack-time caveats.
Pseudo-random generation — what “random” means in software.
Entropy in bits: log₂(pool size) × length. A 16-character password from a 62-character pool carries about 95 bits — far beyond offline-cracking reach. The passwords guide shows the full table.
Version-4 UUIDs carry 122 random bits, so guessing one is effectively impossible. But they are not secrets — anything that must resist guessing AND stay confidential still needs authentication on top.
Password Generator Universal Unit Converter QR Code Generator