Passwort konfigurieren
20
Ihr Passwort
—
| Stärke | — |
|---|---|
| Entropie | — |
🔢 Passwort steht. Jetzt das Netzwerk absichern.
Sichere, zufällige Passwörter — Länge, Zeichensätze und Komplexität frei wählbar.
| Stärke | — |
|---|---|
| Entropie | — |
🔢 Passwort steht. Jetzt das Netzwerk absichern.
A strong password should be at least 16 characters long and combine uppercase, lowercase, numbers, and symbols. Entropy (in bits) indicates how many attempts an attacker needs on average.
Our generator uses the cryptographically secure Web Crypto API (crypto.getRandomValues) — no predictable Math.random() values. Passwords are generated entirely client-side in your browser and never transmitted.
Recommendation: For critical systems, use at least 20 characters with all character sets (≥128 bits entropy). Combined with a password manager, you're well protected.
Social Media: 12 characters, 60 bits.
Email / Cloud: 16 characters, all character sets.
Banking / Admin: 20+ characters, ≥128 bits, plus 2FA.
Server / Root: 32+ characters in a password manager.
The password is generated exclusively in your browser — no server request, no logging. Once you leave the page, it's irretrievably gone.
Entropy (in bits) indicates how many attempts an attacker needs. An 8-character password using only lowercase letters has ~38 bits; with all character sets, ~52 bits. ≥128 bits is considered practically uncrackable. Our generator shows live how length and character sets affect entropy.
Most online generators use Math.random() — deterministic, not cryptographically suitable. Our generator uses crypto.getRandomValues(), your browser's hardware-backed randomness source.
Three typical moments: a root access needs to be re-issued, the guest Wi-Fi key should not be your birthdate again, or you need an API secret for a new integration. One click, 32 characters, done — and nothing leaves your browser. The password is created locally and is gone as soon as you close the page.
Set the length to at least 20 characters — 32 for critical systems.
Enable all character sets: upper, lower, numbers, symbols. More sets mean more entropy.
Click 'Generate' and save the password straight into your password manager.
Both are secure if the entropy is right. A random 20-character string using all character sets brings about 130 bits — practically uncrackable. A passphrase of four to five truly random words (for example from the Diceware or EFF word list) reaches 52 to 65 bits — perfectly sufficient for everyday logins and much easier to type. For Wi-Fi and laptop login, passphrases are the more convenient choice; for root access and API secrets, go with the long random string.
Math.random() is a deterministic pseudo-random generator — anyone who knows the seed can recalculate your 'random' passwords. The Web Crypto API (crypto.getRandomValues), on the other hand, uses a real randomness source from the operating system or hardware. This is the same API browsers use for TLS keys. So you can be sure that nothing here is predictable.
No. Generation runs entirely in your browser — there is no server request, as you can verify in the network tab of your developer tools. Neither we nor anyone else ever gets to see the password.
It depends on what you are protecting: social media 12+, email and cloud 16+, admin and root access 20+. For critical systems, use 32 characters plus a password manager.
Yes. Once the page has loaded, everything works without internet — for example from the browser cache. You can even save the page and open it locally; generation does not need a server.
Entropy measures how unpredictable a password is, expressed in bits. Each additional bit doubles the number of possible combinations. 80 bits is considered good, 128 bits practically uncrackable — our calculator shows you the value live.
Because you no longer have to memorize two or three 'good' passwords and reuse them everywhere. A password manager generates a unique, long password for every service. If one service is breached, all your other accounts stay safe — reused passwords are the most common cause of account takeovers.
Official recommendations: NIST SP 800-63B (Password Guidelines) and the BSI recommendations. Current practical tips: blog article Password Guidelines 2026. Generate hashes for checking and further processing with the Hash Generator.
🔢 Password generated? Now plan your network with the Subnet Calculator.