Use Health to prioritise a credential review. Its score is a summary of the checked vault entries, not a guarantee that every credential or account is secure.

Review the local findings

1. Open PD Password Manager → Health with Pro active and vault-view permission.
2. Review weak passwords, repeated values and ageing passwords.
3. Compare the ageing threshold with Flag vault passwords older than (days) in Settings.
4. Open the relevant entry with Fix or Open, according to your permissions.

The dashboard examines up to 1,000 entries. It can decrypt values for analysis even when your role cannot reveal them on screen. Reuse findings compare values within that analysed set. Age is based on the stored password’s rotation date, not the age of its title or folder.

Request a breach check

Choose Run breach check (HaveIBeenPwned), or Re-run with breach check, when you intend to perform an external check. The module sends a five-character password-hash prefix to the Pwned Passwords service and compares the returned results locally; it does not send the complete password or full hash. The Pwned Passwords documentation explains that range-search method.

The ordinary view can use saved breach results. A failed live request is unchecked, not a clean result. Read any unchecked warning even if the headline score looks good. A password absent from that data set is not proof that the account has never been compromised.

Fix the actual account as well as the copy

Change the password through the account or service’s supported procedure, verify it there, then update the vault copy. Fix opens an entry; it does not automatically rotate the external account. Metadata edits do not renew an unchanged password’s age. Run the relevant checks again after updating, and keep secret values out of tickets and screenshots.

See the PD Password Manager WHMCS guide for related tasks, or explore PD Password Manager.