Skip to content
Security

120 random passwords for servers, master keys, admin accounts

120 random passwords generated with the Unbiased Random Selection method (OS CSPRNG with rejection sampling). Lengths from 32 down to 10 characters. Click any password to copy it to clipboard.

ASCII format passwords

The most secure: 86-character printable charset, ~6.43 bit/char entropy. A 16-character ASCII password already carries about 103 bits of entropy: at one trillion guesses per second (an offline GPU rig against a fast hash) a brute-force search would take about 140 billion years on average. At 30 characters it climbs to about 193 bits, beyond the reach of any brute-force attack. Use these for critical services: server access, master keys, admin accounts.

Charset: !"#$%&'()*+,-./23456789:;<=>?@ABCDEFGHJKMNPQRSTUVWXYZ[\]^_`abcdefghjkmnpqrstuvwxyz{|}~

32 characters · Very strong (~206 bit)

2hR_&unFV<{B(Gt,p8M/]r|2r.9Q'B4C

Mk+TG!SR(/r[M7p'_K.#FSMV,zY;-/Zt

[!4G$t!ye+]|v{uPv]_VfR)b@:y9mmS9

>[email protected])n?*{~Qk@C_47

%H<n55h^7+?W`J5XZhTR-u{eU7m:RX[?

>+'2bhCPg`BQ~f#9Z_NB^^myTn?eC4:b

)($|\|}<~ce~phMc9.C_CJk#v(Jf=$'B

|b;<\<3U_/K7ZjYkXW!9!hY)BK}gA\3{

m:ZnSsD"V{#n!=r<(naTNa5G](/f%TT2

&Jccnj2M8f__3"uj!$c{TTzemq!WuA\(

24 characters · Very strong (~154 bit)

ZhNqU]vTeqCa)FDC|}-YSHb3

dxhvg[)"*xz%T88g}kPN4kxp

3^K[R[dpEX47\V?u#Hdd}8Q;

ttykwjGYZb~6q;<ch&U[VYqj

%:7%;KwR,q<Kv@gs7sf`B>{j

?599sC{,u9X3\W7MB7h[.Rj3

!{fe{9g$/Hugg=7bJ|Q.pYQP

m._Jz6w++tr<mF7.^!(f4)A"

j5gC7j`=hYTHrx@5RYjfvqJs

B2mA=e5s52X:8T.y]8y#$rvr

20 characters · Very strong (~129 bit)

6#F+zqk<e>w3F!6ZM<3U

9z>ZX}xP7aMGQp)'<u4Y

?65WQ*2BV6At!>QT)k<5

!~<"h6WCae(J4X4QhXM*

~,[ta''cD4FY(U85q(m?

$GCVa{C(3xa5KZRu%'Q-

E?G<ymp]kU($AEdxARH:

m->:QBG}X|sJ5>-*vf3s

&ZtA7Wns;4+J7J&Qc]e#

yKn|X?BcA2;w%c>W!#^t

16 characters · Strong (~103 bit)

KdmM:+V;)pTBgE}J

K[uYAcK|;Jxe^-[4

&$g(?,3XRn4~Gd:x

-)mk@s;-AT+ZWByg

~+;`FJ-p%GuE-USK

;;\-a-paU^}%x*C,

atQ4a9D!%#R)Uu?U

KQ'F<YY)wf#gf^F!

[5^um!Ap`_FCzbh%

X4a*Cc-H;{QB[@x(

12 characters · Fair (~77 bit)

aF^dzJnxm6Eu

A!&?aX5#H3]w

F{*`QD{/]qqw

eB|[[J;^&&$?

j"b).N<!-{Vd

=m&S$:!E`q7(

`yj*Q{x25y/{

^wt;8s_/#nq2

+xb|%{#3<h">

t:5Sa=bRV753

10 characters · Fair (~64 bit)

)sW,aVQ\PT

{'V*_+TvxM

%_P#dNz\ZG

26kw&p-E!W

?j\5k~nSSP

WSJm!Bv5mV

ngnUA.[C3w

|u;HyWQn$G

B]J>,/!k?2

,Z!KYj,%]>

Alphanumeric format passwords

Reduced charset (54 characters): more readable and typable, lower entropy per symbol. OK for services that forbid special characters. For everything else, prefer ASCII above.

Charset: ABCDEFGHJKMNPQRSTUVWXYZabcdefghjkmnpqrstuvwxyz23456789

32 characters · Very strong (~184 bit)

nkBv9RggdskUqmhJmHB9547Bns9NXymV

WERStM4rPpKPzzcWQURn9MHf4p5gpQBX

hFvphvacpZmD52EDJVCKJp6XFbKXmxAp

x7dgmFuXdtTN5XfNJHeqMXB5wNStvzm5

KsuxmZaG57HNsEzJbMbJjNHUWv2DmaUd

zKF5wEdaMBVRKqPfy5QcVrU4xdQ9bk4D

3jnhuXFmg6EwaXGSAbbb8NqG64W2apb6

bMkqK7nkFQfUUPrvmukherRxah4msSRT

QyNAwjAhCE3N595K7v2zwEaffpggjabY

ke9mwFS8k3Ab4AH68X2JYbukKmACdzwv

24 characters · Very strong (~138 bit)

dj4ZUDBW3qmpPKMYQegEpWvz

P5kR55XjZWXkBr2t4BKqfeBH

dWAJZn8rh7AdAdeG2ggWPmB7

vrQXhXA372UPdAAZJtJvK8zb

qYXak58EBxRs8n7u9cD9cH7H

n24suKRPPs6trnx9KkGAFzJr

5YfpwEZe72RkyEgz5hsDEW4g

2AmSFuyE3Zu5CEg3Jb86FNuf

6CUCREZnnKkbZsagAKnxV3nv

gaABKywW5XNEzFnnVuADJDh9

20 characters · Very strong (~115 bit)

brVscsPqJCPZAUnvnWBf

9xQypx9q9GN4yMC9zexf

maHHuGUybgamF68S8sxz

BjyvPCyFrKfCzZg6m8mX

pMhwbckEMcjr4QpFwmwN

zvdz6WQmzegBXbPC9PHA

hWRQ8EyynqNwpN5YgJXj

guwk528Trwd4YV2DQMjk

9gpQ8uwQWxZ7XYzuDGRa

hqyG9NvwMxY2DyGx2Q5P

16 characters · Strong (~92 bit)

D7BURqHsn4jSWvFF

Dqc4D7qwWbECbCdT

F7HnzBj9nhtpkFDD

xUcpVyQvkVaNxWy4

G9Vzrz3yB2XTSpvg

tXHDpJ8K5YnjFbR2

mdQZbrTVtEtRgYEd

DenJQVMjPRyfZ8UM

VdPpHW8qdtveb7y6

Y2WsTPc9nxq8ucv7

12 characters · Fair (~69 bit)

EWsCqxAKuMAa

dakEurcux8uE

3mWA6vd3Y3xG

bj7kU9628cHB

23fVysjAaBtQ

vMZXdU9nk8Nm

Fg87gK8hayJM

dEKb3V6eqyQq

54q7wVDT8npR

xD5fPTHnXSkC

10 characters · Weak (~58 bit)

BzyAQKQ3Dy

hzw2qsTP2W

AmYQZGBUzF

ksSuuShJAJ

Repet2Hfm8

4T29PtDdgK

yndFYvFV3p

33aWHAZ3gG

Wb2pPqC8WH

aRUh2bu4jb

Why these passwords are genuinely secure

Generation uses unbiased random sampling via PHP's random_bytes(), which calls into the OS CSPRNG (/dev/urandom on Linux, equivalents on other OSes), with rejection sampling (bit mask, out-of-range values discarded) that avoids the modulo bias many artisan generators get wrong: every character has probability exactly 1/|charset|. On 20 ASCII characters the real entropy is 128 bits. For comparison, a "strong" password picked by a human typically has 30-50 bits of entropy and is brute-forceable in hours on modern GPUs. The passwords served on the page exist only in the HTML sent to your browser: they are not logged, not persisted anywhere, and do not survive page reload.

Frequently asked questions

How long is a truly secure password in 2026?
Personal accounts: at least 16 ASCII characters (roughly 100 bits of entropy). SSH servers, API keys, admin accounts: 24-32 characters. The real security factor is total entropy, not character class: a 30-char ASCII password is more secure than a 12-char password with 'mandatory symbols'.
Why don't the passwords contain '0', '1', 'l', 'I', 'O'?
Visual ambiguity. If you have to read or type the password by hand (on mobile, on a serial console, on a remote terminal), lookalike characters cause errors. Excluding 8 chars out of 94 (0, 1 and the letters I/L/O both upper and lower case) only changes per-char entropy by ~0.13 bits, negligible compared to total length.
Are generated passwords logged or sent anywhere?
No. The PHP that generates passwords runs server-side in an isolated process, doesn't log output, doesn't store anywhere. Every page reload produces 120 fresh passwords that only exist in the HTML served to you. HTTPS always.
Is random_bytes() really secure?
Yes. In PHP 8.x random_bytes() reads from the OS CSPRNG (/dev/urandom on Linux, equivalents on other OSes): the same entropy source that backs standard cryptographic tooling, and when no entropy is available it throws an exception instead of returning weak bytes. The generator applies rejection sampling to avoid modulo bias, a critical detail many artisan generators get wrong and which leads to non-uniform character distributions across the charset.
Can I use these passwords for encryption or API keys?
For account and service passwords they are fit for purpose. For cryptographic keys (AES, RSA, ECDSA) no: keys must be generated directly with the crypto library that will use them, in the format and length specific to the algorithm. Using an ASCII password as a crypto key introduces an unnecessary KDF derivation, typically done wrong.
What if I work at a company where passwords are shared in an Excel file?
Very common, very risky, very fixable. Migrating to an enterprise password manager (self-hosted Bitwarden, 1Password Business, Vaultwarden) takes 2-3 days of setup + training. If you want a structured path for your SMB, get in touch: this is one of the areas I work on regularly.

Password hygiene at your company is a mess?

If your SMB still uses shared passwords in Excel, reused credentials across services, or lacks a centralized password manager, the compromise risk is high and measurable. I offer targeted consulting on enterprise password policy, migration to self-hosted password managers (Vaultwarden/Bitwarden), and audit of service credentials in use. 20+ years backend + applied cybersecurity.

Talk to me about password security