Use origin-bound authentication for privileged accounts, register an independent backup authenticator, and secure recovery as carefully as everyday sign-in.
Phishing-resistant MFA starts with privileged accounts
Website administration extends beyond the content management system. Hosting dashboards, domain registrars, DNS consoles and the email account used for resets all deserve attention. CISA recommends phishing-resistant authentication, especially for system administrators, because conventional MFA can still leave passwords and manually entered codes vulnerable to credential theft. [1]
WebAuthn, the web authentication standard used by FIDO2 authenticators, binds authentication to the legitimate service's domain. A lookalike domain cannot obtain an authentication response valid for that service. This is different from asking someone to type a temporary code, and it is the technical basis of phishing resistance—not a promise that every account compromise becomes impossible. [2]
Passkeys for website security: check the factors
A passkey uses a cryptographic credential rather than a shared password. When the authenticator verifies the user through a local PIN or biometric, possession of the credential and that activation factor can together provide multifactor authentication. A passwordless sign-in therefore does not necessarily mean single-factor authentication. The service must evaluate user verification correctly. [2] [3]
Do not confuse touching a security key with proving a second factor. A touch establishes user presence; without local user verification, another factor is needed for MFA. [3] Check whether your administration service supports verified passkey sign-in or a security key combined with a password. Record the actual requirement rather than relying on an interface label such as 'strong authentication.'
Choose security keys with a loss plan
Synced passkeys can make access easier across devices, while device-bound credentials avoid copying the authentication key through a sync service. Both can provide phishing-resistant authentication, but synced credentials add the security of the sync account and its recovery process to the assessment. NIST identifies unauthorized sync-account access and recovery as risks requiring controls. [3]
For critical administrator accounts, register an independent spare authenticator wherever supported. Keep a backup security key in a secure location separate from the everyday key, and verify that it works before enforcing the new policy. Name credentials clearly so a lost one can be identified. Avoid depending entirely on a phone and laptop that travel together.
Recovery is part of hosting account security
Review every available recovery route before changing sign-in requirements. Check recovery email, phone numbers, backup codes and support-assisted reset policies. NIST treats recovery as a separate lifecycle event and requires notifications under its guidance. Saved recovery codes are intended for secure offline storage and must be invalidated after use; check how your service implements those protections. [4]
Document who may authorize an emergency reset and how account ownership will be verified. Protect recovery email with phishing-resistant MFA where supported. Keep recovery material accessible during an outage, not solely inside the account it restores. Connect this planning to your independent website backup strategy: recovering data and recovering administrative access are separate requirements.
Keep account protection wider than the login
Phishing-resistant authentication protects a particular sign-in mechanism; it does not replace the surrounding security controls. Use named administrator accounts with only necessary permissions. Maintain device updates, screen locks and careful browser-extension selection. Include these practices in your secure web hosting checklist so stronger authentication does not become an isolated setting.
After device loss or an unexpected recovery alert, review registered authenticators and active sessions, revoke affected access, and investigate unfamiliar changes. Review API tokens and automation credentials separately from interactive sign-ins. Revisit access when staff responsibilities change, and rehearse recovery without disabling the only working authenticator. The goal is reliable, accountable access—not simply collecting more authentication methods.
Sources & further reading
These resources provide background for the explanations above. External links are included for context, not as endorsements.
Explains the limits of conventional MFA and recommends phishing-resistant authentication, particularly for administrators.
Defines phishing resistance through verifier-name binding and the factors used by cryptographic authenticators.
Covers synced-key controls, user presence versus user verification, and risks involving sync-account recovery.
Describes account recovery methods, secure offline recovery-code storage, and recovery notifications.
Written with AI assistance and based on the sources listed above. Published November 16, 2026. No hands-on provider testing is claimed. Read our editorial policy.
