PailebotThe web navigator’s logbook
Logbook / Interactive

Passwords, long or weird

Type a password and see how many combinations exist for that length. Then put it up against computers from different eras and find out how long they would take to guess it.

Your password

Everything is calculated in your browser; what you type is never sent or stored. Even so, use a similar password rather than a real one.

Average time trying every combination ·

…

How the site stored the password
Choose the attacker's computer

Hive Systems' machine

Specifications

Year
2026
Graphics cards
16 NVIDIA RTX 5090, in two rented servers of 8
Attempts per second against bcrypt
138,675, measured by Hive with hashcat
Attempts per second against SHA-256
about 435 billion, 16 times what hashcat measures on one RTX 5090

History

Hive Systems, a US cybersecurity company, publishes a colour-coded table every year of how long a password would take to guess by its length and the characters it uses. The 2026 table, published in July, was calculated on this machine, assembled from rented cards.

The table assumes an offline attack on passwords stored with bcrypt at work factor 10, the same as this page's slow-hash option. Hive measures the time to try every combination; this page shows the average, which is half.

Hive only measured bcrypt. The speed against SHA-256 is our estimate, from a hashcat test on a single RTX 5090.

Sources

How many combinations exist for this length

Length
…
Alphabet you use
…
Possible combinations
…
Strength
…

The numbers assume a password chosen at random. One that looks like a word, a name or a date falls much sooner, because an attacker tries the most common things first.

With …, this is what would have to be tried depending on the symbols allowed. Every bit of strength doubles the work.

AlphabetSymbolsCombinationsBits

To match your strength you would need

    How it is calculated

    • The alphabet is deduced from what you typed. There are 26 lowercase letters, 26 uppercase, 10 digits and 33 symbols and space; accents and emoji add another 100 in this count. Up to 128 characters are counted.
    • If your password is in a dictionary of common passwords, the time to try only that dictionary is also calculated, word by word and in order, hashing each one, and the shorter of the two ways is shown. This page uses the 100,000 most used according to the UK National Cyber Security Centre, taken from Have I Been Pwned. Before looking your password up, accents and capitals are removed, because an attacker may have those variants in their list. If you add random characters to a dictionary word, it is no longer in the list and the time is that of trying every combination.
    • The password is assumed to be chosen at random among all possible ones, which is the best case for whoever defends it. On average, the attacker finds it after trying half of them.
    • Every computer gets the same calculation. Its published operations per second are taken, adjusted for its word size, and divided by the roughly 3,000 32-bit operations it costs to test one password against a hash such as SHA-256. This is generous to the attacker because it ignores memory; on several of these machines the algorithm would not even fit. For the computers someone measured with hashcat, which are the two graphics cards, the Hive machine and the PC with no graphics card, the measurement is used instead of the calculation.
    • A slow hash such as bcrypt with work factor 10, the one Hive Systems uses in its table, makes each attempt cost a processor about 470,000 times more than SHA-256, according to a hashcat test on a Ryzen 7 1700X. bcrypt costs graphics cards even more, about 3.3 million times, but the ones shown here use their own measurements.
    • The comparisons with the real world use round, approximate figures. Dates are measured up to today, so "the time since" grows as time goes by.

    To see how hashes work inside, try Hashes and ciphers.

    The list of common passwords is 100k-most-used-passwords-NCSC (SecLists, MIT).