Ontoom

Password generator

Strong, configurable passwords for tests and temporary accounts.

Important: Generate and store passwords with a secure manager. Do not reuse real passwords here.

History

Latest generated values in this browser, grouped by date.

Nothing yet. Click generate to start.

Used

Values copied in this browser, by date.

Nothing used yet. Copy a result to record it.

How the generator works

You choose a length between 4 and 128 characters and which sets to include: uppercase (26), lowercase (26), numbers (10) and symbols (25). The generator guarantees at least one character from each selected set, fills the rest from the combined pool and shuffles the result. Every random choice comes from crypto.getRandomValues, the browser's cryptographic generator, with rejection sampling to avoid bias.

Passwords are created on your device. Ontoom never sends or stores them.

How to use it

  1. Set the length. 16 is a sensible default for accounts; use 32 or more for API secrets.
  2. Pick the character sets. Turn symbols off if the target system rejects some of them.
  3. Click Generate password and copy the result.
  4. Save it in a password manager, and never reuse it across sites.

Entropy: how strong is strong enough

The strength of a random password is measured in bits of entropy: length × log2(alphabet size). With all four sets enabled the alphabet has 87 characters, about 6.4 bits per character.

  • 8 characters, lowercase only: about 38 bits. Falls quickly to an offline attack.
  • 12 characters, all sets: about 77 bits.
  • 16 characters, all sets: about 103 bits, far beyond brute force.
  • 20 characters, lowercase and numbers only: also about 103 bits. Length makes up for skipping symbols.

What current guidance says

NIST SP 800-63B shifted the focus: length matters more than composition rules, forced periodic resets are no longer recommended, and new passwords should be checked against breach lists. For developers, that means accepting long passwords (at least 64 characters), allowing paste and never silently truncating input.

On the server, never store passwords in plain text or with a fast hash like MD5 or bare SHA-256. Use a password hashing algorithm such as Argon2id, bcrypt or scrypt.

Common uses in development

  • Passwords for test users in staging.
  • An HS256 secret for signing tokens in the JWT tool.
  • A first database password for local setups, later replaced by your secrets manager.
  • Testing form limits: maximum length, allowed symbols and fields that break on special characters.

Frequently asked questions

Is the generated password stored anywhere?
Not by Ontoom. It is created in your browser and only exists where you paste it.
How long should my password be?
For personal accounts, at least 14 to 16 random characters. For machine secrets such as API keys and JWT secrets, 32 characters or more.
Are symbols always better?
At the same length, yes, because the alphabet grows. But adding four more characters usually gains more entropy than adding symbols.
Why do some sites reject certain symbols?
It is a limitation of the target system. Generate again without symbols, or use a longer password to compensate.
Can I use this for real passwords?
The randomness is cryptographic and local, so technically yes. The important part is storing it in a password manager and not reusing it.

Written by Orlando Alves · reviewed on · Editorial policy

See also