I lost my phone
Use a backup code or another enrolled method to sign in, then remove the old authenticator and set up 2FA again on your new device.
AltF Authenticator
An authenticator app is safer than SMS for most people, because the code is made on your device and cannot be stolen by a SIM swap or intercepted on the phone network. Passkeys and hardware security keys are stronger again, because they also resist phishing. Any second factor is far better than a password alone.
TOTP codes are made on your device from a secret, so a SIM swap does not give an attacker your codes, and they work without signal. They can still be phished in real time. And if you lose the phone without backup codes, recovery can be slow. NIST's digital identity guidance (SP 800-63B) treats SMS as a restricted method and accepts app-based one-time passwords.
A passkey or a hardware security key signs a challenge that is tied to the real website's address. A fake site gets nothing it can reuse, so these methods resist phishing. Where a service offers them, they are the strongest common choice. Keep a backup method enrolled.
Add a secret, an otpauth:// link or a QR screenshot. Codes are calculated on this device with the Web Crypto API and refresh every period.
No accounts yet
Try the RFC demo secret to see how it works.
Secrets stay in this tab. No request made by this page contains a secret or a code, and nothing goes to analytics. Saving is optional and encrypted on this device; set a passphrase or wipe it in the 2FA Authenticator vault tool.
Yes. It still stops most attacks that rely only on a leaked password.
The codes themselves cannot be predicted without the secret. The risks are malware on the phone, phishing in real time, and losing the phone without a backup.
Where you have an authenticator app or passkey set up, removing SMS as a fallback reduces SIM swap risk. Make sure you have backup codes first.
It is when someone moves your phone number to a SIM card they control, often by tricking your carrier. They then receive your calls and text messages.
Use a backup code or another enrolled method to sign in, then remove the old authenticator and set up 2FA again on your new device.
Check your device clock first. If it is right, verify the code against the secret to see whether it matches a nearby time step.
Export from the old app, import on the new one, and check every account works before you wipe the old phone.
Generate a secret, show it as an otpauth:// QR code, and test your server's verification against the RFC vectors.
Store recovery codes offline, away from the phone that holds your authenticator, and mark each one as used.
Add the same secret here and compare codes, or run the RFC self-test to confirm the maths on this device.
AltFTool never receives your secrets or codes. The only network request any tab makes is the clock check, which asks AltFTool's server for the time and carries nothing else.