# Two-factor authentication (2FA) explained

Source: https://passwordgeneratorlab.com/guides/two-factor-authentication/

> What 2FA is, which methods resist phishing, whether SMS codes are safe, how to handle MFA fatigue and recovery codes, and where to turn it on first.

Updated 9 November 2026 · 4 min read

## Key takeaways

- Two-factor authentication means a stolen password alone is no longer enough to get into your account.
- Passkeys and hardware security keys (FIDO2/WebAuthn) resist phishing; authenticator-app codes, push prompts and SMS codes do not.
- SMS codes are vulnerable to SIM swapping and phishing, and NIST SP 800-63B-4 treats them as a restricted method — but they're still far better than no 2FA.
- Never approve a sign-in prompt you didn't start; repeated prompts mean someone has your password.
- Turn on 2FA first for your email, password manager, bank and phone or platform account, and store recovery codes safely.

Last reviewed 9 November 2026

Two-factor authentication (2FA) adds a second check when you sign in, on top of your password. You may also see it called 2-step verification (2SV) or multi-factor authentication (MFA). Even if someone steals your password, they still need that second factor. It's one of the most effective protections you can switch on, and most of it takes a few minutes.

## How 2FA works

A sign-in factor is something you know, something you have, or something you are:

- **Something you know:** a password or PIN.
- **Something you have:** your phone, a security key, or a device holding a passkey.
- **Something you are:** a fingerprint or face, usually used to unlock the device that holds the key, not sent to the website.

2FA combines two different kinds. A stolen password alone is no longer enough, which defeats most automated attacks that use leaked passwords.

## Not all 2FA is equal

The biggest difference between methods is whether they can be **phished**. A fake login page can ask for your one-time code just as easily as your password, and pass both to the real site within seconds. Only some methods stop that.

| Method | Phishing-resistant? | Notes |
| --- | --- | --- |
| Passkeys and hardware security keys (FIDO2 / WebAuthn) | Yes | The key is tied to the real website's address, so a lookalike site gets nothing usable. The strongest option widely available. |
| Authenticator app codes (TOTP) | No | Codes change every 30 seconds and never travel by text. Much better than SMS, but can be phished. |
| Push notifications | No | Convenient. Safer with number matching, where you type a number shown on the sign-in screen. |
| SMS or voice codes | No | Vulnerable to SIM swapping and interception. Still far better than no 2FA at all. |

The US Cybersecurity and Infrastructure Security Agency (CISA) calls phishing-resistant MFA the most secure form, and names FIDO/WebAuthn as the widely available option. NIST's current guidelines (SP 800-63B-4) treat SMS and voice codes as a *restricted* method that services may use only after weighing the risks, and accept synced passkeys alongside device-bound security keys.

## Is SMS 2FA safe?

It's safer than nothing, and the UK National Cyber Security Centre is clear that text-message codes still offer a huge advantage over a password alone. Its weaknesses are real, though:

- **SIM swapping:** a criminal persuades your mobile carrier to move your number to their SIM card, then receives your codes. Ask your carrier about a port-out PIN or account lock.
- **Phishing:** a fake site asks for the code and uses it immediately.
- **Lost access:** if you change numbers or lose signal abroad, you may be locked out.

If a service offers only SMS, use it. If it offers an authenticator app or passkey, switch to that.

## MFA fatigue: don't approve what you didn't start

With push-based 2FA, attackers who have your password sometimes trigger sign-in prompts over and over, hoping you'll tap "Approve" to make them stop. This is called MFA fatigue or push bombing. The rule is simple: **if you didn't just try to sign in, deny the request**, then change that account's password, because someone knows it. Number matching, where you have to type the number shown on the real sign-in screen, makes this attack much harder.

## Backup codes and recovery

Most services give you a set of one-time **recovery codes** when you turn on 2FA. They get you in if you lose your phone or key. Store them somewhere safe: your password manager works for most accounts, but keep the password manager's own recovery codes outside it, for example printed and kept at home.

- Register two security keys or passkeys where you can, so losing one isn't a crisis.
- Check which recovery path each account uses. A weak fallback, such as SMS, can undo a strong first choice.
- Moving to a new phone? Transfer your authenticator app *before* wiping the old one.

## Where to turn it on first

You don't have to do everything at once. Start with the accounts that unlock the rest:

1. **Your main email:** it can reset the password of almost every other account.
2. **Your password manager:** it holds everything. See [do you need a password manager?](https://passwordgeneratorlab.com/guides/do-you-need-a-password-manager/)
3. **Banking, payments and investment accounts.**
4. **Your phone account and Apple, Google or Microsoft account:** they control your devices, backups and often your passkeys.
5. **Social media and work accounts:** takeovers are used to scam your contacts.

## 2FA and strong passwords work together

2FA doesn't make the password irrelevant. Some recovery flows skip the second factor, some sites don't offer it at all, and a weak password lets attackers keep trying the second step. Use both:

- A unique, random password for every account. Our [password generator](https://passwordgeneratorlab.com/) makes one in your browser.
- The strongest second factor each service offers, preferring passkeys or security keys.
- A quick check that your current passwords haven't leaked, with the [leak check](https://passwordgeneratorlab.com/password-strength-checker/#leak-check).

[How to create a strong password](https://passwordgeneratorlab.com/guides/how-to-create-a-strong-password/) · [Do you need a password manager?](https://passwordgeneratorlab.com/guides/do-you-need-a-password-manager/)

## Sources

- [CISA: Implementing Phishing-Resistant MFA (fact sheet)](https://www.cisa.gov/sites/default/files/publications/fact-sheet-implementing-phishing-resistant-mfa-508c.pdf)
- [CISA: More than a Password — multifactor authentication](https://www.cisa.gov/MFA)
- [NCSC: Setting up 2-Step Verification (2SV)](https://www.ncsc.gov.uk/guidance/setting-2-step-verification-2sv)
- [NIST SP 800-63B-4, Digital Identity Guidelines: Authentication and Authenticator Management (2025)](https://pages.nist.gov/800-63-4/sp800-63b.html)

## Keep reading

- [How often should you change your password?](https://passwordgeneratorlab.com/guides/how-often-should-you-change-your-password/) — Why security agencies no longer recommend changing passwords on a schedule, the situations where you should change one right away, and what to do instead.
- [Passkeys vs passwords: what changes and what doesn't](https://passwordgeneratorlab.com/guides/passkeys-vs-passwords/) — How passkeys work, why they resist phishing, how they compare with passwords and 2FA, their limits, and why you still need strong passwords.
- [Has my password been leaked? How to check safely](https://passwordgeneratorlab.com/guides/has-my-password-been-leaked/) — How to check if your email or password appeared in a data breach without exposing it, what a “not found” result really means, and what to do if it leaked.
- [Do you need a password manager?](https://passwordgeneratorlab.com/guides/do-you-need-a-password-manager/) — Why password reuse is the real risk, how password managers protect your vault, the honest tradeoffs, and how to choose one and set it up safely.
