Skip to content
Calcrivo

Password Complexity Calculator

Turn a composition policy into the character set, combination count and entropy it actually produces.

Inputs

characters
classes

Policy Entropy Floor

78.8bits

Character Set Size

95characters

Possible Passwords

5.404 × 10²³

Classes Available

4of 4

NIST SP 800-63B Verdict

Partly compliant — length is fine, but SP 800-63B advises dropping forced composition rules

Step by step

  1. Values used

    Minimum length required = 12 characters; Lowercase allowed = Yes; Uppercase allowed = Yes; Digits allowed = Yes; Symbols allowed = Yes; Classes the policy forces = 3 classes

  2. Password Complexity

    combinations = charset size ^ minimum length, and the policy's entropy floor = minimum length × log2(charset size).

  3. Policy Entropy Floor

    = 78.8 bits

  4. Character Set Size

    = 95 characters

  5. Possible Passwords

    = 540,360,087,662,637,000,000,000.000

  6. Classes Available

    = 4 of 4

  7. NIST SP 800-63B Verdict

    = Partly compliant — length is fine, but SP 800-63B advises dropping forced composition rules

How it works

A composition policy sets a floor, not a typical value: the weakest password it permits is one of minimum length drawn from the allowed characters. Allowing symbols lifts the charset from 62 to 95, worth 0.62 bits per character, while each extra required character is worth a full log2(charset) bits. Policies are usually argued about in terms of rules; converting them into an entropy floor shows which rules buy real strength and which only annoy users.

Formula

Password Complexity

combinations = charset size ^ minimum length, and the policy's entropy floor = minimum length × log2(charset size).

charset size
26 lowercase + 26 uppercase + 10 digits + 33 symbols, per the classes you allow
minimum length
Shortest password the policy accepts

Frequently Asked Questions

How is Password Complexity calculated?

combinations = charset size ^ minimum length, and the policy's entropy floor = minimum length × log2(charset size). A composition policy sets a floor, not a typical value: the weakest password it permits is one of minimum length drawn from the allowed characters. Allowing symbols lifts the charset from 62 to 95, worth 0.62 bits per character, while each extra required character is worth a full log2(charset) bits.

Why does Password Complexity matter?

Policies are usually argued about in terms of rules; converting them into an entropy floor shows which rules buy real strength and which only annoy users.

What values do I need to enter?

This calculator takes 6 inputs: Minimum length required, Lowercase allowed, Uppercase allowed, Digits allowed, Symbols allowed, Classes the policy forces. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

Why does NIST advise against forced composition rules?

SP 800-63B found that mandatory class rules push users toward predictable patterns — a capital at the front, a digit and an exclamation mark at the end — which mangled wordlists model directly. The guidance keeps the length minimum and the breach-list check, and drops the class requirements.

Does forcing classes lower the entropy?

Slightly, in theory: requiring at least one of each class removes some passwords from the keyspace. The effect is a fraction of a bit. The real cost is behavioural, not mathematical.

You might also need