How to reset password when email is down?

Lost access to my recovery email and can'

This query requires a disaggregated analysis because there's no single answer — it depends on whether we are discussing consumer-facing web applications, enterprise infrastructure with SSO/IDP layers, or bare-metal systems where the password file is directly accessible via local privilege escalation vectors. I will organize by attack surface and recovery chain priority.

Scenario A: Web application with email dependency for reset flow (the user case). If SMTP relay is down but the database stores a hashed peppered credential, there are three viable out-of-band flows depending on your audit logging capabilities. Option 1: Administrative override via an authenticated support account that has the permission to set user passwords directly — this should only be exposed through a hardened internal admin panel with MFA and every operation logged in a tamper-evident append-only store (e.g., CloudTrail for AWS, or a separate syslog destination). The risk here is credential stuffing on your own administrative interface; ensure you have rate limiting keyed by source IP AND per account to prevent mass password reset abuse. Option 2: Pre-shared recovery codes generated at the time of signup and stored in an encrypted form (AES-GCM with an externally managed key) — this is what Bitwarden and other security products use for non-email recovery. If you haven't implemented this, it's a gap worth closing before your next outage. Option 3: Hardware token binding if the user has already registered a FIDO2/WebAuthn credential. The WebAuthn API allows attestation verification that prevents attacker impersonation even if they control the password reset flow elsewhere.

Scenario B: Enterprise SSO (Okta, Azure AD, PingIdentity) where email is down but the IDP still responds. You can push an emergency password reset through the admin console, which will hit the user's next login attempt rather than requiring them to click a link in an email they won't receive. The flow should be: revoke all