Prompt
phishing resistant authentication
Latest observation
Oct 28, 2026
OpenAI APIWeb search: off
Phishing-resistant authentication means a login method that is designed so a user cannot be tricked into giving away credentials to a fake site or app.
Common examples
- FIDO2 / WebAuthn security keys (hardware keys like YubiKey)
- Passkeys (device-bound or synced, using WebAuthn)
- Smart cards / client certificates
- Biometric unlock + device-bound credential when implemented with WebAuthn/passkeys
Why it’s phishing-resistant
These methods are tied to the real website/app origin. Even if a user enters the method on a fake phishing site, the credential won’t work there because it’s cryptographically bound to the legitimate origin.
Not phishing-resistant
- Passwords
- OTP codes from SMS or authenticator apps
- Email verification links
- Push approvals, in many cases
These can still be captured or relayed by attackers.
Key benefits
- Strong protection against credential theft
- Resists real-time phishing and replay attacks
- Often satisfies higher security standards and compliance requirements
Best practice
Use phishing-resistant authentication as part of MFA, ideally:
- Passkeys or security keys as the primary factor
- Backup recovery methods that are also secure
- Risk-based controls and device management
If you want, I can also give you:
- a plain-English definition,
- a technical definition, or
- a comparison table of phishing-resistant vs non-resistant methods.