Two-Factor Authentication (2FA): What to Use and Why

SMS codes, authenticator apps, push approvals and hardware keys — how each factor type stacks up, and how to set 2FA up without locking yourself out.

Passwords are "something you know" — and everything you know can be phished, guessed, or leaked. A second factor adds "something you have" (a phone, a key) or "something you are" (biometrics), so a stolen password stops being sufficient.

Why a second factor matters

Attackers buy breached passwords in bulk and replay them automatically. 2FA changes the economics: even a perfect password replay fails without your device. It is the cheapest, highest-leverage defense available to consumers.

The main types, ranked (weakest to strongest)

  1. SMS codes. Better than nothing. Vulnerable to SIM-swapping and number port-out fraud (see Is SMS 2FA Safe in 2026?).
  2. Email codes. Similar tier; only as strong as your email account.
  3. Authenticator apps (TOTP). Free, offline, phishing-resistant-ish. Codes rotate every 30 seconds. Still typeable into a phishing page in real time.
  4. Push approvals with number matching. Convenient; approve with care — unexpected prompts mean someone has your password.
  5. Hardware security keys / passkeys (FIDO2). Cryptographically bound to the site's origin — a lookalike domain simply fails. The strongest consumer option.

Setting it up safely

  1. Start with your primary email, then banking, then your password manager, then everything else.
  2. Prefer an authenticator app or hardware key over SMS when offered.
  3. Register two factors where possible (two keys, or key + app) to avoid single-device loss.

Backup codes and recovery

When a service shows you backup codes, treat them as spare passwords: download them, print them, store them offline (a safe, a locked drawer). Recovery-phone and recovery-email settings deserve the same care — they are the side door around your 2FA.

Attacks on 2FA

  • MFA fatigue: attackers spam push prompts hoping you tap "approve". Never approve a prompt you did not trigger.
  • Real-time phishing (AiTM): a proxy site relays your password and code to the real site instantly. Only origin-bound factors (keys/passkeys) fully resist this.
  • SIM-swap: your number is ported to an attacker's SIM. Another reason to prefer app/key-based factors.

Summary

Priority order: email → money → password manager → identity providers → everything else. Best available factor for each, backup codes stored offline, and never approve a prompt you didn't cause.


Hands-On Security Practice

Apply what you learned with our zero-telemetry tools and references:

Put it into practice: run your next password through the local checker — it never leaves your browser.

Keep reading

Related guides