Is it safe to enter your 2FA secret into a website?

The short version

  • Runs in your browser

    Codes are calculated on your device. The server only delivers the page.

  • Vault encrypted on your device

    AES-256-GCM, with a key derived from your passphrase (PBKDF2-SHA256, 600,000 rounds).

  • Key held in memory only

    The vault locks itself when you step away.

  • No analytics on the generator

    Ads appear only on blog articles and guides, never near your codes.

The honest limits. We cannot recover a forgotten passphrase, and clearing your browser data removes the vault. A compromised device is a compromised vault.

Short answer: it can be, if the tool genuinely runs in your browser and you can check that it does. 2Fa Live is built that way, and this page tells you exactly what it does, what it cannot do, and how to see it for yourself. We would rather you verify than believe us.

Two ways to use 2Fa Live

  • Instant mode (the default). You paste a secret key or an otpauth:// link, or scan, upload, paste or drop a QR image, and the code appears at once. No account and no passphrase. The key is held only in the page's memory. It is not written to storage, and it is wiped when you press Clear or leave the page.
  • Vault mode (optional, "My accounts"). If you press Save to my accounts, you choose a passphrase and the account is encrypted in your browser with PBKDF2-SHA256 (600,000 iterations) and AES-GCM-256, then saved in your browser's localStorage on this device.

In both modes the calculation happens in your browser and your secrets are never sent to our server.

What a 2FA secret is, and why people hesitate

When you turn on two-factor authentication, a website shows a QR code. Inside it is a secret key, a short string of letters and numbers. Anyone who has that key can generate the same codes you do, so for that account the key is as sensitive as a second password. Hesitating before pasting it into a website is the right instinct.

The threat model in plain language

A threat model is just an honest list of who might want your secret and how. Here is ours.

Who or what Can it get your secrets? Notes
The 2Fa Live team and server Not through the authenticator Instant-mode keys stay in page memory. Vault secrets are encrypted in your browser and saved on your device. Neither is sent to us.
Someone who steals the saved vault data or a backup Not without your passphrase The data is encrypted with AES-GCM-256 using a key derived from your passphrase with PBKDF2-SHA256 (600,000 iterations). A weak passphrase makes guessing easier, so choose a long one. Instant mode saves nothing to steal.
Someone watching your network Not the secrets The page is delivered over HTTPS, and your secrets are never part of any request.
Malware on your device Yes, potentially Keyloggers and screen grabbers can capture your passphrase or your codes. No authenticator can stop this.
A malicious browser extension Yes, potentially Extensions with access to page content can read what the page shows. Keep extensions to a minimum on the browser where you use the vault.
Someone with access to your unlocked device Yes If your browser is open with a key in the instant generator or an unlocked vault, they can see codes. Press Clear, lock the vault and lock your device.
Phishing sites Not your secret, but your code A fake login page can ask for the 6-digit code and relay it instantly. Check the address bar before you type any code.

What we can see, and what we cannot

We believe a privacy claim should say what is visible, not only what is not.

What our server can see when you visit: the same technical data every web server receives, such as your IP address, the page you requested, your browser type and the time. These appear in ordinary hosting logs. If you accept analytics cookies, Google Analytics may also collect usage data on pages where it is enabled. It is never enabled on the authenticator.

What our server cannot see: your secret keys, the codes generated from them, your account names, your vault passphrase, or the contents of your vault or backups. Those never leave your browser.

How instant mode and the vault protect your data

Instant mode. The key you paste or scan is used to calculate the code and is kept only in the page's memory. Nothing is saved. Pressing Clear, or closing or leaving the page, wipes it.

Vault mode works like this:

  1. You choose a passphrase. We never receive it.
  2. Your browser derives an encryption key from it using PBKDF2-SHA256 with 600,000 iterations, a deliberately slow function that makes guessing expensive.
  3. Your accounts are encrypted with AES-GCM-256 and saved in your browser's localStorage on this device.
  4. To use the vault you enter the passphrase again, and decryption happens locally.
  5. Encrypted backups use the same protection, so the file is useless without your passphrase.

Check it yourself: nothing is sent

You do not need to be a developer to do this. Use a throwaway test secret first, for example JBSWY3DPEHPK3PXP, a well-known sample value with no connection to any account.

  1. Open the authenticator in your browser.
  2. Open developer tools: press F12, or Ctrl+Shift+I (Windows and Linux) or Cmd+Option+I (Mac).
  3. Click the Network tab. Clear the list with the bin or clear icon.
  4. Keep the tab open, and paste the sample secret into the instant generator. A code appears at once.
  5. Watch the Network list. You should see no new requests when the code appears or when it refreshes.
  6. Optional: press Save to my accounts and choose a test passphrase. Then click Application (Chrome, Edge) or Storage (Firefox), open Local Storage for this site, and look at the saved entry. It should look like scrambled text, not your secret. In instant mode alone, nothing should be saved there.

What you are looking for: any request whose payload contains your secret, code or account name. You should find none. If you ever do, stop using the tool and tell us at once.

An important limit of this check: it shows what the page did on that visit. Because our code is delivered by our server each time you load the page, an observation today does not guarantee tomorrow's version behaves the same way. The code is not open source, so we cannot offer public review of it. If this matters to you, repeat the check from time to time, and follow the good habits below.

Limitations, stated honestly

  • We cannot protect you from a compromised device. If malware or a hostile extension controls your browser, your passphrase and codes are exposed no matter what we do.
  • We cannot recover a vault passphrase or your vault. Lose the passphrase and the saved data is gone. Instant mode needs no passphrase.
  • Clearing browser data deletes the vault. If you wipe site data without a backup, your accounts are lost from this device.
  • The code is not open source. You can observe behaviour, as shown above, but you cannot read the source.
  • A web authenticator is a convenience, not a vault for your most critical accounts. For accounts that would be catastrophic to lose, such as primary email or financial accounts, use stronger protection as well, for example a hardware key or passkey, and keep your recovery codes offline.
  • This page describes the web tool. The Android app is a separate product with its own privacy practices. See its Google Play listing for those.

Good habits that make any authenticator safer

  • Press Clear when you finish with the instant generator, and close the tab on a shared device.
  • If you use the vault, pick a long, unique passphrase, and store it in a password manager or somewhere offline.
  • If you use the vault, make an encrypted backup after adding each account and keep it somewhere other than the device itself.
  • Save the recovery codes each service gives you when you enable 2FA.
  • Use the authenticator on a device and browser you control, with few extensions, and lock it when you step away.
  • Do not take screenshots of QR codes and leave them in your photos. A QR code contains the secret.
  • Be cautious of any site asking for a secret key outside the moment you set up 2FA. Check the address bar before typing a code.

Questions or concerns?

If you have found a security problem, write to contact.2falive@ozoneapps.com. Read the privacy policy and the cookie policy for the full legal detail, or return to the authenticator.

Frequently asked questions

Does 2Fa Live send my secret key to a server?

No. The code that calculates your codes runs in your browser. In instant mode your key stays in the page's memory only, and if you choose to save accounts they are stored only on your device in encrypted form. You can check this yourself with the steps on this page.

Can the 2Fa Live team see my accounts or codes?

No. We do not receive your secrets, your codes or, if you use the vault, your passphrase. Our server delivers the page to you, and that is all it does with the authenticator.

If you cannot see my secrets, how can you help me if I lose my passphrase?

We cannot. Nobody can open your vault without the passphrase. Keep an encrypted backup and the recovery codes your services gave you. This only applies to the optional vault: the instant generator needs no passphrase, so you can paste your key again at any time.

Is a browser authenticator as safe as an app on my phone?

It depends on your device and habits. A web page can be reached by browser extensions and by malware in ways a locked-down app may not be. Instant mode keeps nothing after you clear it, and a browser vault on a device only you use, protected by a strong passphrase, is a reasonable choice for many accounts. For the most valuable accounts, consider a hardware security key or a passkey as well.

Why should I trust a site that is not open source?

You should not have to trust us blindly, so we explain exactly what runs and give you a way to observe it. Be aware of the limit: your browser fetches our code each time you load the page, so an observation shows what it did on that visit. We do not ask for trust we cannot back with something you can check.

Should I paste a real secret into any online generator?

Only into one you understand and have checked. Test with a throwaway secret first, then open your browser's network panel and see for yourself that nothing is sent. Treat any tool that cannot explain this the way we do with caution.

What is the biggest risk to my 2FA codes?

Malware or a malicious browser extension on your own device, and phishing pages that trick you into typing a code. Those risks apply to every authenticator, and 2Fa Live does not claim to remove them.