2FA Authenticator
ListeningInbox
0Cryptographic password
crypto.getRandomValues(). Nothing is sent to a server or written to disk.Secret key or otpauth URI
Paste a Base32 setup secret (spaces ignored) or an otpauth://totp/... link.
Advanced parameters
Generate a fictional identity
State-synced area codes, deterministic SVG avatar, online credentials, Finance & IDs, and one-click Temp Mail handoff.
Generate test card numbers
Builds structurally valid PANs with genuine issuer prefixes and check digits for payment sandbox testing.
Check Luhn validity
Published gateway test numbers (click to copy)
When testing exact gateway states (3D Secure, declines, international failures), use the provider’s deterministic test PANs rather than random numbers.
Browser-based RFC 6238 TOTP generation explained
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.
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.
| Parameter | Default | Supported options | URI query key |
|---|---|---|---|
| Protocol | TOTP (Time-based) | TOTP only (no stateful HOTP) | otpauth://totp/ |
| Hash algorithm | SHA-1 | SHA-1, SHA-256, SHA-512 | algorithm= |
| Code length | 6 digits | 6, 7, or 8 digits | digits= |
| Time step | 30 seconds | 5 to 300 seconds | period= |
| Recovery method | Works when | Practical weakness |
|---|---|---|
| Recovery codes, stored offline | You lose your phone or authenticator app | Useless unless saved at initial 2FA setup time |
| Second enrolled authenticator | One device is lost or replaced | Both devices may be lost together if carried in one bag |
| Backed-up Base32 secret | All hardware devices are lost | Anyone holding the secret can generate live codes forever; protect like a password |
| Service support recovery | No codes or backups remain | Slow manual verification and frequent social-engineering target |