otpauth:// URI parser

Client

Inspect authenticator enrollment URIs without storing the full secret in shared links.

About otpauth:// URI parser

Parse TOTP/HOTP otpauth URIs into issuer, account, algorithm, and digits. The interactive transform on this page runs in your browser tab—Toolcore does not need your paste for the core operation described above.

How to use this page

Paste or type in the main workspace, run the primary action from the toolbar, then copy or download the result. Use Load example when the page offers it, or URL prefill (?q= / ?qb=) so agents and tickets open the same input.

Limits and safety

Utilities here are for development and inspection—do not paste live production keys, PANs, or recovery codes into any browser tab you do not control.

Loading…

Nearby workflows on Toolcore

  • TOTP / authenticator codes — RFC 6238 time-based one-time passwords from a Base32 secret—HMAC-SHA1, otpauth URI and optional QR; local only. before you trust a token, digest, or key material in production.
  • Password strength — Heuristic password strength meter—length, charset mix, common weak-password warnings; local only. before you trust a token, digest, or key material in production.
  • Random string generator — Random alphanumeric, hex, Base64 URL-safe, or custom tokens—entropy hint, local only. before you trust a token, digest, or key material in production.
  • PIN code generator — Generate 4–8 digit numeric PINs with crypto randomness in your browser—copy locally. before you trust a token, digest, or key material in production.

Common use cases

  • otpauth:// URI parser for quick local checks without uploading data.
  • Copy results into tickets, docs, or classroom notes.

Common mistakes to avoid

  • Unexpected input shape

    See the intro and how-to notes for accepted formats.

FAQ

Is processing local?

Yes—this runs entirely in your browser.

Agent prefill?

Use q or qb for the main text field when supported.

More tools

Related utilities you can open in another tab—mostly client-side.