Password Requirements Checker

Test custom minimum/maximum length and optional lowercase, uppercase, digit, symbol, or whitespace rules without transmitting the password.

Password to check

Minimum length

Maximum length (0 = none)

Character rules

Whitespace

—Type a password

Sensitive values stay in this browser page. Theoretical entropy/search-space math assumes uniform random generation and is not a crack-time promise for human-chosen passwords. Use a reputable password manager for real account storage.

Modern password guidance without false certainty

keeps password/passphrase generation and review browser-local while shifting guidance toward length, uniqueness, common-password blocking, password-manager compatibility, MFA, and compromise-driven changes rather than arbitrary composition rules or guaranteed crack-time claims.

Security boundary

A local meter can flag obvious patterns but cannot prove that a password is safe, unused elsewhere, or absent from every breach corpus. Do not paste sensitive production password exports into batch tools; generate unique secrets locally and store them in an appropriate password manager.

Use this result with confidence

Requirement matching is different from strength estimation

A password can satisfy length, character-set, and symbol rules while still being easy to guess because it uses a common pattern or previously exposed value. Treat the requirement checklist as compatibility testing for a policy, not proof of security. A password manager that creates unique random credentials is generally a stronger workflow than manually optimizing a memorable string to satisfy checkboxes.

Avoid pasting a real high-value password into unnecessary tools

This page is designed to process input locally, but good credential hygiene still minimizes where sensitive secrets are entered. Use a representative test string when you only need to understand a site’s policy. For an actual account, prefer the destination site’s own validation and a trusted password manager rather than copying the final credential among multiple utilities.

Policy wording can hide extra constraints

Some systems reject repeated characters, dictionary words, user names, whitespace, certain symbols, or recently used passwords even when the published summary mentions only length and character classes. If a generated credential passes this checker but the destination rejects it, read the destination error and policy rather than weakening the password until it happens to work.

Longer and unique usually matters more than arbitrary complexity rituals

Modern guidance often emphasizes sufficient length, resistance to known compromised values, and uniqueness across services. Forced periodic changes or predictable symbol substitutions can create patterns without adding much protection. Use this tool to understand explicit requirements, then rely on the actual service policy and a secure credential-storage workflow for the account itself.