StageKitListening

2FA Authenticator

Listening
24h active · 10s sync
RFC 6238 Authenticator

Secret key or otpauth URI

Paste a Base32 setup secret (spaces ignored) or an otpauth://totp/... link.

Advanced parameters
Computed locally in browser memory via Web Crypto HMAC. Your secret never leaves this tab.
Live token
Time-based one-time code
Refreshes in 30sNext: —
Module Knowledge Base

Browser-based RFC 6238 TOTP generation explained

Web Crypto HMAC · SHA-1 / SHA-256 / SHA-512 · 100% local RAM
Quick Answer

A browser TOTP generator computes the exact same 6-to-8-digit one-time verification codes as mobile authenticator apps by hashing your Base32 secret key against the current 30-second UTC time slice with Web Crypto HMAC. Your secret never leaves browser memory.

RFC 6238Time-based OTP standard
30 secDefault rotation window
6–8 digitsConfigurable code width
Local RAMZero server transmission

How time-based one-time passwords stay synchronized

Instead of talking to the service, TOTP divides Unix UTC time by the period (usually 30 seconds) to get a shared counter. Both the server and this browser tab pass that counter and your decoded Base32 secret into Web Crypto HMAC-SHA1, SHA-256, or SHA-512.

Because generation relies solely on UTC time and the secret, this tool shows both the current token and the next period lookahead code so you never miss a tight cutoff.

Parsing otpauth:// provisioning links cleanly

Paste a complete otpauth://totp/Issuer:user?secret=... URI to auto-fill secret, issuer, digits, period, and algorithm without manual mistakes.

RFC 6238 specifies SHA-1 as the interoperability default. Even though SHA-1 is retired for collision-resistant certificates, HMAC-SHA1 does not depend on collision resistance and remains standard across authenticators.

Why counter-based HOTP is not supported

  • HOTP (RFC 4226) increments an event counter each time a code is used rather than reading wall-clock time.
  • A stateless browser tab cannot track how many prior codes a server already issued.
  • Time-based TOTP derives the counter automatically from your synced device clock.

Device safety and recovery code hygiene

  • Secrets are processed in transient RAM with zero outbound requests, zero logs, and zero cookies.
  • Always store one-time recovery codes offline when enabling 2FA so losing a phone never locks you out.
  • For banking, email, or primary cloud accounts, prefer a dedicated mobile authenticator or hardware key.
Supported TOTP settings and otpauth:// provisioning parameters
ParameterDefaultSupported optionsURI query key
ProtocolTOTP (Time-based)TOTP only (no stateful HOTP)otpauth://totp/
Hash algorithmSHA-1SHA-1, SHA-256, SHA-512algorithm=
Code length6 digits6, 7, or 8 digitsdigits=
Time step30 seconds5 to 300 secondsperiod=
Account recovery paths when a 2FA device is unavailable
Recovery methodWorks whenPractical weakness
Recovery codes, stored offlineYou lose your phone or authenticator appUseless unless saved at initial 2FA setup time
Second enrolled authenticatorOne device is lost or replacedBoth devices may be lost together if carried in one bag
Backed-up Base32 secretAll hardware devices are lostAnyone holding the secret can generate live codes forever; protect like a password
Service support recoveryNo codes or backups remainSlow manual verification and frequent social-engineering target

Frequently asked questions

Where do I find my secret key?
When a site displays a QR code, it usually also offers a manual Base32 setup key underneath (such as JBSW Y3DP EHPK 3PXP) or an otpauth:// link. Paste either one directly into the secret input.
Why does the code change while I am looking at it?
TOTP codes rotate every time window (30 seconds by default). The progress bar tracks the remaining window and the Next code readout precomputes the upcoming interval so you never mistype across boundaries.
Why are only time-based links supported?
HOTP uses a server-tracked click counter instead of clock time, so a stateless page cannot tell how many codes have already been generated. Only clock-synchronized TOTP works offline without counter sync.
Is it safe to paste a real 2FA secret into this page?
Your secret stays strictly inside browser RAM with zero server transmission, storage, or analytics scripts. Treat a browser tab as temporary convenience on a trusted machine, and keep high-value accounts on a hardware key or dedicated app.
Will these codes match my authenticator app?
Yes, whenever the clock and parameters match. Most services use 6 digits, a 30-second step, and SHA-1; adjust advanced options or paste the full otpauth:// URI if your service requires 8 digits or SHA-256.
StageKit · Zero trackers · Browser-local security toolsPress 1–5 on desktop to switch tools

Customize address

Generation style

Install StageKit App

Install StageKit as a standalone Android Progressive Web App for fast home-screen launch, full-screen bottom navigation, and offline access to Password, 2FA, Identity, and Card tools.

  1. Open the browser menu in Chrome on Android or desktop.
  2. Tap Add to Home screen or Install app.
  3. Confirm Install to pin StageKit to your launcher.