Prompt
I’m unhappy with SMS codes as my MFA method
Latest observation
Oct 28, 2026
OpenAI APIWeb search: off
That’s a reasonable concern. SMS-based MFA is better than no MFA, but it’s not ideal because SMS can be vulnerable to SIM-swap attacks, number porting fraud, message interception, and account recovery abuse.
Better MFA options, in order of preference:
- Hardware security key (best)
- Examples: YubiKey, Titan Key, Feitian
- Very strong against phishing and account takeover
- Authenticator app using TOTP
- Examples: 1Password, Authy, Google Authenticator, Microsoft Authenticator
- Much better than SMS, though still phishing-resistant only to a degree
- Passkeys
- If the service supports them, these are often the most convenient and secure
- Can be synced across devices or stored on a hardware key, depending on platform
- Push-based MFA
- Convenient, but can be vulnerable to “MFA fatigue” attacks if poorly implemented
What I’d suggest:
- Replace SMS with a hardware key if the account is important
- Add a second backup method so you don’t get locked out
- Save recovery codes in a password manager or offline location
- Make sure your mobile carrier has a port-out/SIM swap PIN if you must keep SMS as backup
If you want, I can help you pick the best MFA option based on:
- the sites/services you use,
- what devices you have,
- and whether you want the most secure or most convenient setup.