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.

Published on · Updated on · by

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)

\[9x`Sx_:-`*_!2FJ/Avc;Hn97$y8p$'

gqA`p?xu3%S=fg48F^@kh_m!-wpev~+P

G37&T+7]z69%@D3\cPkWqJ9=Ab(5?Z?`

.:23>[V4H]x]nu>?"Mh+<vh|/p|&.>,D

*Xq6Q\$`*:e^w92B,X8N,WQ&A*^#CWu~

ET|rD$m/{5?JV2bd;"J/g$-~ws6;+*p<

Cz6.J"v@Rsz{XEdba3ghfQBNdfev3gR5

"}e$[|a(T9tVE@_pzV-Fm+q'}D*ja|gc

NQ$A)#t#{<<Nu\@vZ%Kev-uu\YK.GSuk

+R@2@Y$k7c_^,@fBVf,7[^W7Peg)gYHK

24 characters · Very strong (~154 bit)

SAm]y=K<R"A=8(~Y^skpWSev

eJXWWTWAg<.q_MTq6HQ\55)w

Ae|||GZ.(J%`=Kn3Y&7BS!)[

3c&'}?dz5)[VF?\a_~55P%q]

_X9'wyN9q!ag6bkaW$+aT9CD

\{Md$6"krmU;6hw(jTnwd;ur

Jj]&st_GS|sqwr:%XcZFv`6n

C.'#RBpA#`,:aX-[Q6Xx=8nW

w]<9[?V`R;W6W\H*./.aq4PU

n;~X&yk~Tr?E]vj6Bx2x<x/q

20 characters · Very strong (~129 bit)

T;te\JwDeC<R|B2/=BCe

#/~{NFCke@:vK]N@?X@:

ghz^d5u>{-|6RyVaxN)%

Ua_cP;,9@MU86db|a;$Z

b!ghws]tu+uf=Aw;cZz#

.JbrEr<;fbp@_9P>$vD{

!26Yn<5{W^;TR,NeP(?G

YPu.(.rDY';:J4Wx;=f@

W`k'r"s/"Qqcfw5&6k]H

g5$K.-gvrQHh5V#{m<^X

16 characters · Strong (~103 bit)

3B[x2EYNZ&YeED.7

Y55s}>T{K`D9'|7_

q(6<q5GwqXy}dU@e

<NpJN.#~nE%Mw9aB

):\5Z29[_P`+!t$y

*wARASX%Rx2H~gU*

XJ6"8c_hSEv\!Sn]

UqN)KSfS.d;W$z"m

`=@wmj,Jn*tG-5W,

y%g/-G\(}3yFBve+

12 characters · Fair (~77 bit)

<DNP-qP)]HUD

GC`<ubvJ=56,

x=E~X]W9>/B<

U}Np'R6_?Fd,

24F#jw>#{.u}

M~`c#s`AX/Z]

T7]+!r{z+P&`

j+C5@5|Sny5c

,=NeP2Z_QT.p

_m>eu/uy48vA

10 characters · Fair (~64 bit)

SX.:bYjF<"

/mB2ZcdbD5

p`anbw_98>

-xbH;4:)x<

"dCZ}z?xU%

z){4$vadG.

"2vR@("N,8

\2a{JMer?W

].^W+u;7xb

(GWb(>c~d&

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)

esvNStxyRmqnxyqbSHbaANgespNmPEs6

DZrafqT56fvYtuRFgxFbnFHsgNmBq9Np

KJXjXHevbtzHP4RawpzYeacrfy7zjmve

pubeNfJDM6375jH6djZPF9e8dPagYchH

CNGgFSw9Cn6SjQ6DMrJ29R4BwSCjYn5A

VbZJjgStyea9JgtKRN7sFYQDYzWUrmyS

PeKWkxCUcdPNv9tr3Rnnfk3xMGsyAPM9

4XURkTMBCqJ68ZrSgGEwAJxCAD2NhVkk

qyTxGj5JssBFKSzJCz5zPKCgswY7Q7yw

DpGxUJTafmAGzsuJu8pd9gtJ5cXyxwyK

24 characters · Very strong (~138 bit)

86qrGBKDB2DPbreHHmdB4cjb

F4XZaVC5fE56DECgQU4U6Pxs

XwfQpKBN9z6fAcrPN5KUS9He

Hrxk96D9MDutuakmZZdbfdUp

S2AVbyhZsa5EHATcbtp8WeAV

NctTsGZtvDdm5qJVx8pqjvjr

72vsSgcERXqZr3RR9hbbXXKE

qhKdxQzGktc2WsrY3ArCez8B

UKXCJsDuWfng8BqTJ3CUTmNX

JANsBqBuWEUV9RtsHVTs7hVa

20 characters · Very strong (~115 bit)

6EbEhZDd8XbMAMbddvn2

c8W7M3rrhTd8dsvHRFNz

yGgbQarwwf5FFTZjYqjF

R5MuTxtJwBU7Kymguavp

J8qRgcMRSRePc2DsFaZV

AmxBzCg5bSvmkjVaa7PH

BpvKqtvWtTkxtk8gEakN

SjVetvzth2KxSMUJ3tjD

7Fkm5DbQPpxCDuQVdtcN

3aSh8ba7eGnDfx4TBHBH

16 characters · Strong (~92 bit)

7fu844kUft8bhjaW

yxDJ3QN7Gm9Dexwb

e8fn4sKFA8JrbVgy

3n5QshGsHk48QYaJ

mW7M6m7A5Kqw7qFH

3kywWBzrTfEHAYMK

ZWpc9473BNAJZUCS

d3JHNmd8Mb5EFqCV

bx4wH6NWJj85nZBx

WykxEbQA2GcmNTAD

12 characters · Fair (~69 bit)

yXzb7V85yRxb

Rssa5Y4xuMpU

d9KhW3T8gJev

R6TSwEGVpTxw

EGSsqAxsXAaT

Te2FjXk7cqJH

BsP4WD6WTnUF

gzaS8G4CuehC

QYmzet93ZZde

yeFUf5rd8nPe

10 characters · Weak (~58 bit)

8YpkwG22Zy

ZMPBvmnuv2

PJ3zQarSWu

39Am7aJk38

Ffd9KHXGgG

XQeqSSfydP

mxC3enuhTz

PwhUwgG5mB

gQHvTgNK8Q

8MnbxqVGgg

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