Skip to main content

Password Entropy & Brute-Force Crack Time Calculator

Calculate cryptographic password entropy bits (E = L × log2(R)), total keyspace combinations, and brute-force crack times across Bcrypt and GPU rigs.

Input Parameters

Try Example:
8128

Calculation Results

Cryptographic Entropy Strength Meter (0–128 Bit Scale)101.2 bits (79%)
0b (Lemah)40b60b (Standar)80b (Kuat)128b+ (Kriptografi)
Generated Cryptographic Password Sample
5<ihxv[ch77[W$JA
Character Length (L)
16 Chars
Character Pool Size (R)
80 Symbols
Shannon Entropy Value (E)
101.15 bits
Formatted Combinatorial Entropy
101.15 bit
Strength Rating Code
very_strong
Cryptographic Strength Classification
Sangat Kuat (Tingkat Militer / Enterprise)
Total Keyspace Combinations (R^L)
2^101.15 (~10^30.4) kombinasi
Active Character Class Sets
Uppercase (A-Z), Lowercase (a-z), Numbers (0-9), Symbols (!@#...)
Want to compare 2 design options side-by-side (e.g., Scenario A vs Scenario B)?
⚡ Production Security & Ops Standard
Debian 12 / Ubuntu 24.04 LTS + Nftables + Systemd Timer
CIS Benchmark Level 1 • Non-Root SSH Key-Only + Fail2ban/CrowdSec

Validate firewall rulesets and cron timers in staging before production rollout.

Estimated Brute-Force Crack Time Across 4 Attacker Models
Attacker Hardware / ScenarioHash Guessing SpeedAverage Time (Seconds)Estimated Duration
Serangan Online Dibatasi (100 tebakan/detik — Rate Limiting Web)100 tebakan/detik1,000,000,000,000,000,000,000,000,000,000 Seconds> 10^15 tahun (Mustahil Ditembus)
Serangan Online Cepat (10.000 tebakan/detik — API Unthrottled)10,000 tebakan/detik1,000,000,000,000,000,000,000,000,000,000 Seconds> 10^15 tahun (Mustahil Ditembus)
Serangan Offline Hash Lambat (10.000 tebakan/detik — bcrypt / Argon2)10,000 tebakan/detik1,000,000,000,000,000,000,000,000,000,000 Seconds> 10^15 tahun (Mustahil Ditembus)
Serangan Offline Hash Cepat (100 Miliar tebakan/detik — GPU Farm NTLM) [VERIFY]100,000,000,000 tebakan/detik1,000,000,000,000,000,000,000,000,000,000 Seconds> 10^15 tahun (Mustahil Ditembus)
Share to WhatsApp

How to Use This Tool

  1. Set the target password length (between 4 and 128 characters) and toggle the active character sets (uppercase, lowercase, numbers, and symbols).
  2. Choose whether visually ambiguous characters (such as 0, O, 1, l, I) should be excluded for easier manual transcription.
  3. Review the calculated entropy in bits, total keyspace combinations, and the estimated brute-force crack durations across 4 attacker capability tiers.

Worked Example: 16-Character Enterprise Standard Credential (All Sets)

Worked example: A 16-character password combining uppercase, lowercase, digits, and symbols (pool size 88) yields 103.35 bits of entropy (~1.29 × 10^31 combinations), requiring billions of years to crack.

Example Input
Password Character Length (8 - 128)
16 Chars
Include Uppercase Letters (A-Z)
Yes / Active
Include Lowercase Letters (a-z)
Yes / Active
Include Numeric Digits (0-9)
Yes / Active
Include Special Symbols (!@#$%^&*...)
Yes / Active
Exclude Ambiguous Characters (0, O, o, 1, l, I, |)
Yes / Active
Calculated Output
Generated Cryptographic Password Sample
ZG6ELP2rh&w_^&Hx
Character Length (L)
16 Chars
Character Pool Size (R)
80 Symbols
Shannon Entropy Value (E)
101.15 bits
Formatted Combinatorial Entropy
101.15 bit
Strength Rating Code
very_strong
Cryptographic Strength Classification
Sangat Kuat (Tingkat Militer / Enterprise)
Total Keyspace Combinations (R^L)
2^101.15 (~10^30.4) kombinasi
Active Character Class Sets
Uppercase (A-Z), Lowercase (a-z), Numbers (0-9), Symbols (!@#...)
Estimated Brute-Force Crack Time Across 4 Attacker Models
Attacker Hardware / ScenarioHash Guessing SpeedAverage Time (Seconds)Estimated Duration
Serangan Online Dibatasi (100 tebakan/detik — Rate Limiting Web)100 tebakan/detik1,000,000,000,000,000,000,000,000,000,000 Seconds> 10^15 tahun (Mustahil Ditembus)
Serangan Online Cepat (10.000 tebakan/detik — API Unthrottled)10,000 tebakan/detik1,000,000,000,000,000,000,000,000,000,000 Seconds> 10^15 tahun (Mustahil Ditembus)
Serangan Offline Hash Lambat (10.000 tebakan/detik — bcrypt / Argon2)10,000 tebakan/detik1,000,000,000,000,000,000,000,000,000,000 Seconds> 10^15 tahun (Mustahil Ditembus)
Serangan Offline Hash Cepat (100 Miliar tebakan/detik — GPU Farm NTLM) [VERIFY]100,000,000,000 tebakan/detik1,000,000,000,000,000,000,000,000,000,000 Seconds> 10^15 tahun (Mustahil Ditembus)

Core Concept & Engineering Notes

Password entropy is an information-theoretic metric derived from Claude Shannon's mathematical framework that quantifies the unpredictability and cryptographic strength of a credential in bits. Unlike legacy complexity rules that merely enforce predictable character substitutions, entropy measures the true combinatorial keyspace an adversary must exhaust during a brute-force attack. For a uniformly generated random password, entropy is defined by the formula E = L × log2(R), where L denotes the password length and R represents the size of the active character pool. The pool size R is determined by summing the distinct character sets enabled during generation: lowercase letters (a–z) contribute 26 characters, uppercase letters (A–Z) contribute 26 characters, numeric digits (0–9) add 10 characters, and standard printable symbols add 26 to 32 characters. When all four character classes are active (R ≈ 88–94), each additional character of password length adds approximately 6.5 bits of entropy, multiplying the total brute-force search space by nearly two orders of magnitude per character. In modern identity and access management standards (NIST SP 800-63B), real-world resistance against offline credential cracking depends heavily on the server-side password hashing algorithm. Fast, unsalted message digests such as MD5, SHA-256, or legacy NTLM can be evaluated at tens of billions of guesses per second on multi-GPU cracking rigs, whereas memory-hard key derivation functions such as Argon2id, bcrypt, and PBKDF2 intentionally throttle evaluation speeds to thousands of hashes per second. Consequently, contemporary security engineering prioritizes credential length and true randomness over predictable human substitution patterns (such as replacing 'a' with '@' or appending '123!') that dictionary rule engines crack in milliseconds. While 60 to 75 bits of entropy suffices for standard user accounts protected by rate-limiting and multi-factor authentication (MFA), privileged infrastructure secrets—including Linux root passwords, LUKS/ZFS disk encryption passphrases, and HMAC signing keys vulnerable to offline cracking—require 100 to 128+ bits of CSPRNG-generated entropy.

How It Was Calculated (Formulas & Steps)

Frequently Asked Questions (FAQ)

What is the minimum recommended entropy in bits for administrator accounts and API keys?

Standard user accounts should target at least 60–75 bits of entropy, privileged administrator accounts should exceed 80–100 bits (e.g., 16 full-pool characters), and cryptographic/JWT signing secrets require 128 to 256 bits.

Which increases entropy more effectively: adding password length or adding symbols?

Increasing password length (L) scales the keyspace exponentially, whereas expanding the character pool (R) scales polynomially. A 20-character alphanumeric passphrase is exponentially stronger than an 8-character complex password.

Why is the total keyspace divided by 2 when estimating average brute-force time?

Under a uniform probability distribution, an exhaustive search is statistically expected to locate the target key after testing 50% (half) of the total possible combinations.

Why does NIST SP 800-63B no longer recommend mandatory periodic password rotation?

Frequent mandatory rotation causes users to adopt predictable incremental patterns. NIST recommends enforcing longer high-entropy credentials paired with Multi-Factor Authentication (MFA) and breach monitoring.