Key plus time
A TOTP code is derived from the secret key and the current time as defined in RFC 6238. A new code every 30 seconds.
Paste a 2FA secret key or upload a screenshot of the QR code. You get the current TOTP code with a countdown, just like Google Authenticator, plus a check that your two-factor setup is right.
Codes are computed in your browser only. The page stores nothing and never sends your secret anywhere.
Don’t paste secrets from real accounts
A 2FA secret is the second key to an account. This page neither stores nor sends it, but any website is one more place a key could leak. Use the generator for test keys and to check your setup. For everyday logins, keep your codes in an authenticator app on your phone.
Spaces and case don’t matter. Services show the key under the QR code when you turn on 2FA: “Can’t scan? Enter the key manually”.
Enter the code your app (Google Authenticator, Microsoft Authenticator, Authy, etc.) shows for the same key. We’ll compare it with the code on this page.
This device’s clock: checking against our server…
What goes to our server: nothing except one time request to check your clock. The key and codes never leave your browser and aren’t saved — reload the page and they’re gone.
The same maths as Google Authenticator and other 2FA apps, right in your browser.
A TOTP code is derived from the secret key and the current time as defined in RFC 6238. A new code every 30 seconds.
The maths runs in your browser’s built-in Web Crypto. The key isn’t sent to a server or written to browser storage.
If your app’s code doesn’t match, we show how far your phone clock is ahead or behind.
Generate a random key with a QR code to test how your app or service handles 2FA.
Compare the app’s code with ours for the same key and see whether the phone clock is to blame.
Check that your service issues a correct QR and accepts SHA-1, SHA-256 and SHA-512 codes.
Make sure the key you saved works before you delete the old app.
Show colleagues how two-factor authentication works using a test key.
Free network, privacy and security checks right in your browser — no install, no sign-up.
Two-factor authentication (2FA) means signing in with two independent factors: your password and a code from your device. Even if the password leaks, nobody can sign in without the code.
The most common kind of code is TOTP. An authenticator app (Google Authenticator, Microsoft Authenticator, Authy, 1Password) keeps a secret key and every 30 seconds derives a new code from it and the current time. The service does the same and compares the results.
Most often it’s the phone clock: the code depends on time, and with a gap of more than 30–60 seconds the service rejects it. The second cause is a key from another account, or an old key if 2FA was set up again. Less often the service uses non-default settings: SHA-256, 8 digits or a 60-second period.
This page computes codes in your browser and never sends the key to a server — you can confirm that in the Network tab of the developer tools. Still, a 2FA secret equals the second key to an account, so keep real keys only in the app on your phone and use the generator for tests and checks.