Loading your toolkit…

Authenticator

Privacy and drafts

Input and output are processed in your browser, without uploading them.

  • Drafts stay in this tab while you switch tools or return home. Reloading or leaving clears ordinary drafts. Nothing is saved to browser storage. A dot beside a tool marks an edited draft.
  • Copy puts the current code on your clipboard. Clearing a tool does not erase those copies.
  • Share puts your setup key in a link. Anyone with it can view that content. It lives in the link’s # part, which is not sent to the server; Bearaujus does not store the link. Reopening or reloading it restores the shared content.

Get the current two-factor code from your setup key. Codes refresh automatically and your key stays on this device.

How to use
Copies a link containing this result. Anyone who opens the link can see it. The link is not saved on Bearaujus.

Loading authenticator…

How to use

Authenticator
  1. Enter a Base32 setup key or a TOTP otpauth link, or open a local QR image.

  2. Match the account's algorithm, digit count and period. Link settings take precedence.

  3. Read the current code or choose Copy. Codes refresh using your device clock.

Setup keys and otpauth links

Paste the Base32 secret from your account’s two-factor setup, or the complete link encoded in its authenticator QR code. A Base32 key uses letters A–Z and digits 2–7; spaces are accepted.

A setup link has this shape: otpauth://totp/Issuer:account?secret=BASE32KEY&issuer=Issuer&algorithm=SHA1&digits=6&period=30.

  • secret is the setup key, not a current six-digit code.
  • Issuer and account identify the service and login.
  • algorithm, digits and period configure the code. Link settings are applied automatically and shown under Code settings.

Example loads a public demo link for Workshop demo / demo@example.com with SHA-256, eight digits and a 60-second refresh. It is not a real account. Reset clears the link and restores defaults.

Supported one-time codes

This tool generates time-based codes using TOTP (RFC 6238) and Web Crypto HMAC.

  • Defaults: SHA-1, six digits and 30 seconds.
  • Other options: SHA-256, SHA-512, eight digits and supported refresh periods.

Counter-based HOTP links are not supported.

Temporary use, without a vault

Your setup key and generated codes stay in this tab’s memory. They are not uploaded or saved by the tool.

  • Share copies a link that includes the setup key. Anyone who opens it can see the key.
  • Switching tools or returning home keeps the key in this tab.
  • Clearing, reloading or leaving the toolkit removes it. Reloading a share link shows that key again.

Keep a durable authenticator and recovery method. A setup key can generate future codes, so treat it as a secret.

Code not working?
  1. Set your device’s date and time automatically.
  2. Check that the setup key, algorithm, digits and period match your account’s instructions.
  3. Use the code before it expires.

Open Code settings to adjust manual keys. Setup links supply their own settings.

QR images and clock accuracy

PNG, JPEG and WebP images are decoded locally, up to 10 MB and 25 megapixels.

Set your device clock automatically. An incorrect clock can produce codes the service rejects.

The example key is a public test fixture from RFC 6238, not a real account.

Edited draft in this tab. Switching tools keeps it; reloading clears it.