This custom tool may run third-party scripts. To load it, agree in Cookie settings in the footer.

Candidate in, manager immediately after

Generate a 12-character candidate, confirm length and character classes against the site’s rules, then paste into a real password manager’s “new item” field—or into a throwaway lab form if you are only testing UX. The webpage is the birth of the secret, not its home.

Never email the password to yourself, drop it in a public chat, pin it in a shared channel, or leave it on a shared whiteboard photo. Managers and secure sharing tools exist because screenshots and scrollback leak for months.

Generate a fresh password instead of recycling the same string across sites. Reuse is still the most common self-inflicted breach pattern, and twelve characters will not save a reused secret that appears in a third-party dump.

If you must hand a temporary password to another person during onboarding, use your organization’s approved secret-sharing path and force a rotation on first login. After the manager stores the item, clear the clipboard on shared machines when that option exists.

  • Generate → verify policy → paste into a manager → clear clipboard.
  • No email, chat, or photo of the secret.
  • Rotate anything that was spoken aloud or screen-shared.

What twelve characters is good for (and not)

Good for: many consumer site policies, workshop demos, and fixture accounts that will be rotated. Not good for: believing length alone beats a manager with unique passwords, or treating this page as long-term storage.

Some institutions require longer secrets, passphrases, or hardware keys. Follow the stricter policy. This tool will not argue with your security team—and should not.

Screen-share demos: generate, copy, blur or navigate away, move on. Do not linger on a visible secret while chatting with an audience. Recordings turn a five-second glance into a permanent leak.

Twelve characters can still be weak if the character set is tiny or the site strips symbols you thought were included. Always re-read the policy text next to the password field before you commit the account.

Lab fixtures versus human accounts

QA teams sometimes need many lookalike passwords for form validation tests. Prefer private scripts or a private Lompu list with known patterns when you need reproducibility; public generation is for interactive picks, not deterministic test suites.

Human accounts that matter deserve unique secrets stored in a manager with MFA wherever available. A webpage dice roll is only the birth of the secret—not its home.

If a site forbids symbols or requires them, match the policy before you lock yourself out during onboarding. Failed creation loops waste time and tempt people to weaken rules or reuse an old password.

Staging environments often reuse weak shared passwords out of habit. Even lab accounts should be unique per environment when the staging stack holds realistic customer data. Document who can rotate fixture logins so orphaned demos do not become quiet backdoors.

  • Check allowed character classes first.
  • Store in a manager, not a notes app screenshot.
  • Enable MFA when the service offers it.
  • Keep lab reproducibility in private lists or scripts.

Threat model honesty

This is entertainment-and-lab grade generation in a browser experience—not a hardware security module. Do not use it to invent keys for production cryptography ceremonies or payment-signing secrets.

Phishing pages can mimic generators. Always check you are on lompu.com before typing anything sensitive nearby. Bookmark the real URL if you use the page often during workshops.

Browser extensions, malicious clipboard helpers, and shared kiosk profiles can observe what you copy. Prefer a trusted personal device and a reputable password manager when the account protects money, health, or employer access.

Product questions: Contact. Privacy and cookies: Privacy Policy. Account capacity on Lompu: Pricing. None of those pages replace a password manager; they explain how Lompu itself works.

Policies, character classes, and lockout avoidance

Before you generate, skim the destination site’s rules: minimum length, required uppercase, digits, symbols, and banned patterns such as repeated characters. A perfect twelve-character string that violates policy is still a failed signup.

Some older systems silently truncate passwords or disallow certain symbols. After creation, log out and log back in once during setup so truncation surprises appear immediately—not weeks later during an outage.

If a site rejects your candidate, generate again rather than editing by hand into a memorable shape. Manual “tweaks” often reintroduce names, years, and keyboard walks attackers try first.

Workshops teaching password hygiene should separate “how randomness looks” from “where secrets live.” Show the generator briefly, then spend most of the lesson inside a manager creating unique items and enabling MFA.

Report this tool

If this page contains abusive, illegal, or rights-infringing material, email contact@lompu.com with the URL and a short description. See also our Terms of Service and the content policy notes on Explore.

Build Your Own Random Generator

Create a custom random generator in seconds with your own list, images, and fields. Make a picker for decisions, ideas, games, giveaways, study prompts, or anything else you want to choose at random. Compare public examples on Explore, then share your finished tool with a simple link.

Frequently Asked Questions