DevToolsmith

TOTP / HOTP Tester

Debug an authenticator integration with an exact timestamp or counter. Choose an algorithm and digit count, then compare the expected code with your application.

Runs 100% in your browser — nothing is uploaded

287082

Code for the exact timestamp or counter above. Refresh the timestamp to calculate a new current code.

Test an OTP integration

Start with the public RFC secret and timestamp 59. In SHA1 mode with six digits and a 30-second period, the expected TOTP is 287082. Switch to eight digits to get 94287082. HOTP counter 0 with six digits gives 755224.

TOTP and HOTP use different moving values

HOTP uses a monotonically increasing counter. TOTP derives that counter from elapsed Unix time and a time-step length. Use RFC 4226 and RFC 6238 test vectors to compare implementations before connecting a real account.

Frequently asked questions

Why does my authenticator show a different code?

Check the Base32 secret, algorithm, digit count, time step and device clock. This tool compares the exact time step or counter you enter; it does not search a tolerance window.

Are secrets saved or shared?

No. Secret values and generated codes remain in this page’s memory. There is no share link or automatic storage. The prefilled value is a public RFC test secret.