Password Policy Tester
Writing a password policy, or trying to satisfy one, means turning prose into checks. This tester makes each check explicit and shows which ones a candidate password passes.
Presets encode the published rules:
- NIST SP 800-63B (2024 revision): 8 to 64 characters, block known-breached and common passwords, no composition rules and no periodic rotation. This is the modern baseline.
- PCI DSS 4.0: 12+ characters, letters and numbers, blocklist.
- Microsoft Entra ID: 8 to 256 characters, three of four character types, banned-password list.
- Typical corporate and Strict for organisations that still require mixed sets.
Switch to custom rules to build your own from minimum length, required sets, repeated-character limits and a common-password block. The common-password check uses the same 10,000-entry list as the common password checker.
What leaves your browser
Checks run locally. Nothing is transmitted. The tester is for validating candidates and policies, not for storing anything.
Which policy should my organisation use?
Start from NIST 800-63B: length, a breach blocklist, MFA, and no forced rotation. Add composition rules only where a regulator requires them.
Why does NIST not require symbols?
Their research found composition rules push people toward predictable substitutions and written-down passwords, while a longer minimum plus a blocklist does more good with less friction.
Can I export the rules?
Not yet. The presets are documented in our password policy guide, which you can adapt for an internal policy document.