SMS and Email-Based MFA
What you'll learn: How SMS and email deliver one-time codes for MFA, and why they're convenient but vulnerable.
How It Works
After you enter your username and password, the system generates a random numeric code and sends it to your registered phone number (via text message) or email address. You must retrieve and enter this code within a short time window (usually 5–10 minutes) to complete authentication.
Think of it like a hotel safe that requires both a PIN and a physical key card — except the "key card" here is temporary and delivered through a separate communication channel.
The Appeal
Convenience: Most people already have a phone number and email address. No extra apps or hardware required.
Accessibility: Works on any device that can receive SMS or email, including basic phones.
The Vulnerabilities
SMS-Based MFA
- SIM swapping attacks: Attackers convince your carrier to transfer your number to their SIM card
- SS7 protocol weaknesses: Telecom infrastructure vulnerabilities allow message interception
- Phishing: Attackers trick you into revealing the code on fake login pages
- No encryption: SMS travels in plaintext through cellular networks
Email-Based MFA
- Compromised email accounts: If your email is hacked, attackers bypass MFA entirely
- Weak second factor: Email is often protected by... just a password (no true "second factor")
- Phishing susceptibility: Same risk as SMS
When They're Acceptable
Despite limitations, SMS/email MFA is better than passwords alone for low-risk scenarios: newsletter subscriptions, forum accounts, or situations where TOTP apps aren't feasible.
Key Takeaway: SMS and email MFA deliver one-time codes through separate channels but suffer from interception risks, phishing vulnerabilities, and dependence on potentially compromised communication systems — use them only when stronger MFA methods aren't available.