Test password breach detection — does your browser's password manager flag a known leaked password while ignoring a strong unique one?
Test whether your browser's password manager flags leaked credentials. Each case below is a real sign-in form: type or paste the credentials into the empty fields, then submit. The browser only offers to save a password you entered yourself, and saving is what triggers the compromised-password check.
Submitting navigates to /api/login-test, which stores, logs, and forwards nothing — it only echoes back the username and password length. After submitting, accept the “Save password?” prompt, then check chrome://settings/passwords/check (Chrome/Edge), Settings → Passwords (Safari), or about:logins (Firefox).
Why the save prompt needs a real entry
Browsers offer to save a password only when you type or paste it into the field and the form then submits with a real navigation. Pre-filled or programmatically-set values are treated as untrusted and ignored, so the prompt — and the breach check that follows saving — never appears. That is why these fields start empty.