1. Zero-Upload Web Crypto HMAC
Every token is computed inside your browser using native crypto.subtle.sign('HMAC') and dynamic truncation per RFC 4226 / RFC 6238—no backend ever sees your Base32 secret.
SECURITY & AUTHENTICATION · RFC 6238 / RFC 4226
Generate and verify RFC 6238 TOTP and RFC 4226 HOTP 2FA codes locally in your browser using Web Crypto HMAC. Supports SHA-1/256/512, 6 or 8 digits, otpauth:// URI import/export, previous/next window preview, and clock-skew verification.
otpauth://••• (click Show above to view secret in URI)Computed locally via Web Crypto API (HMAC). Secrets stay in page memory and are never transmitted.
HOW IT WORKS
Every token is computed inside your browser using native crypto.subtle.sign('HMAC') and dynamic truncation per RFC 4226 / RFC 6238—no backend ever sees your Base32 secret.
Seeing the −1 and +1 time-step codes alongside the live token makes it effortless to test server clock-skew tolerances and grab a fresh code before the countdown hits zero.
Generate a cryptographically random 160-bit Base32 secret and copy a spec-compliant otpauth:// URI ready for QR encoding or unit tests.
Generate QR codes for your URI in QR Code Studio, inspect hashes in Web Crypto Playground, or test keys in JWK & PEM Key Tool.
No. All HMAC-SHA computations run locally via your browser’s Web Crypto API (crypto.subtle). Secrets remain only in volatile page memory and are never saved to localStorage or sent over the network.
It supports SHA-1 (standard Google Authenticator / Authy), SHA-256, and SHA-512, 6-digit or 8-digit codes, custom TOTP periods (such as 30s or 60s), and RFC 4226 counter-based HOTP.
TOTP depends on your device clock being synchronized to UTC. Check the Previous (−1) and Next (+1) codes or use the ±1 step Drift Verifier to see if your system clock is off by 30 seconds, and confirm the secret, algorithm, digits, and period match.
Yes. Paste any otpauth://totp/... or otpauth://hotp/... URI to load its parameters automatically, or click Generate 160-bit Secret to create a fresh Base32 key and copy a ready-to-use otpauth:// URI for testing.
HOTP (RFC 4226) generates a one-time code from a shared secret and an incrementing integer counter, whereas TOTP (RFC 6238) replaces that counter with the current Unix timestamp divided by a fixed period (usually 30 seconds).