JPKCom DB

Generator

Passwords, EFF passphrases, salts, WordPress and Wi-Fi keys with a QR code, .htpasswd lines, and TOTP codes — all generated in your browser.

One toolbox for passwords, keys, and codes

The Generator bundles the recurring chores of admin and developer life in one place: create a strong password or a memorable passphrase, generate cryptographic keys for a config file, build a Wi-Fi key together with a QR code people can scan, produce a ready-made line for a .htpasswd file, or set up two-factor authentication (2FA) via TOTP. Instead of opening five different pages for that, you click through six tabs in a single interface.

It's built for administrators securing WordPress, server, or Wi-Fi access; for developers who need a secret, a salt, or a TOTP test account in a hurry; and for anyone who wants a genuinely random password or a TOTP code for their authenticator — no account, no install, right in the browser.

What the Generator produces

The interface is organized into six tabs:

  • Passwords — random passwords in four character-set tiers (from "more specials" down to "hex only"), any length from 4 to 128 characters, optionally without look-alike characters; plus an Apple-style mode (pronounceable, memorable) and passphrases drawn from the EFF word list. Up to 20 results at once, with an entropy readout.
  • Salt — cryptographic salt keys from an extended ASCII character set, length 16 to 1024.
  • WordPress — the eight security keys as ready-made define() lines for wp-config.php or as a .env block (Bedrock), plus an Extreme Keys mode built on hash_hmac().
  • WLAN — WPA-ready Wi-Fi keys (20 to 63 characters) and, if you like, a Wi-Fi QR code that lets phones join the network directly.
  • .htpasswd — a finished user:hash line for Apache or nginx, hashed with bcrypt or the older APR1-MD5.
  • OTP — TOTP one-time codes per RFC 6238: Base32 secret, 6 or 8 digits, SHA-1/-256/-512, otpauth:// key URL, QR code, a live ticker with previous/current/next, and a check for codes from your app.

Password hashes for applications (bcrypt, Argon2id, PBKDF2), including verification, no longer live here — they're in the Hash Generator, and the .htpasswd tab links straight to it.

Architecture: everything in the browser, the API only for scripts

The key privacy property is quick to state: everything you generate on the page is created in your browser. Passwords, passphrases, salts, WordPress and Wi-Fi keys come from crypto.getRandomValues (uniformly distributed, no modulo bias), the .htpasswd hashes are computed locally via WebAssembly (the hash-wasm library), and the secret, codes, and QR codes of the TOTP tab are produced locally as well. None of it is sent to the server or stored — not even the password you type in for a .htpasswd line.

Alongside the page there's a small text API for scripts and curl (e.g. /tools/generator/pw/32/). There the server generates the values with random_int() or random_bytes(), serves them with no-cache headers, and limits requests per IP address. Both paths share the same character sets — plain printable ASCII without ' and \. The details are in the manual.

Try it now

→ Open the Generator — pick a tab, set the options, generate, copy. No account, free, right in the browser.

  • Hash Generator — checksums for text and files and, in its password-hashing tab, bcrypt, Argon2id, and PBKDF2 hashes with verification, for when you want to store a password in an application.
  • Cryptor — symmetrically encrypt and decrypt text and files.
  • UUID Generator — create unique identifiers (UUIDs) when you need an ID rather than a secret key.
  • PKI Viewer — inspect X.509 certificates, keys, and CSRs.

There's more on the subpages: the manual with every tab and parameter, examples for common workflows, and a collection of tips & tricks.