Prove that you store passwords securely

Storing passwords properly is something not all websites are doing. Every now and then we read about leaked password and it turns out even big companies are doing it wrong. Do you want to prove to your users that you are storing their passwords correctly?

Register and get your site verified

Why do you need to use secure algorithms when storing passwords?

Standard hashing functions are not designed for storing passwords. If an attacker gets your database, modern hardware allows for easy brute-force attacks. And when you leak the password of your users and they use the same password on other sites, all their accounts are compromised. See here for more details.


Below is are the steps needed for verifying your site's password storage mechanism:
  1. Register on this site.
  2. Add your site to the list.
  3. Specify "Endpoint path" to be the path to the service which you are going to expose in the next step.
  4. Expose a RESTful service endpoint that conforms to the requirements below. We invoke that endpoint periodically (roughly once a day) to test your compliance.
  5. Place a badge we provide on your registration form to show your users that you store passwords securely.

The RESTful service that we need in order to verify your password storage mechanism must use the same functionality that is used for storing user passwords in the database.

It needs to accept the following input:

Content-Type: application/json

    password: "randompassword"
And produce the following output as a response:
Content-Type: application/json

    algorithm: "BCRYPT", // the one-way password transformation algorithm you use, one of: BCRYPT, PBKDF2, SCRYPT.
    hash: "$2a$10$rBV2JDeWW3.vKyeQcM8fFO47l4bVeQgDL6VIkxqlzQ7TCa", // the hash that you store in the database. If it's binary, BASE64-encode it.
    salt: "vKyeQcM8fFO47l4bVe", // (optional, used only for PBKDF2) the salt used if it's not included in the hash. If it's binary, BASE64-encode it.
    algorithmDetails: { // (optional, used only for PBKDF2) contains additional information about the algorithm.
        hashFunction: "SHA-256", // the hash function used with the algorithm. One of SHA1, SHA-224, SHA-256, SHA-384, SHA-512.
        iterations: 100, // the number of iterations used.
        keySize: 48 // the key size.

What do you get for being compliant?

Your site stands out and is recognized as one that stores passwords securely. Even though users are not experts, a simple page linked to the badge we provide explains why storing passwords securely is important for them.

Are compliant sites really secure?

Does having an endpoint implementing the right algorithm mean a website is using this algorithm for storing passwords? Not necessarily, but if they have the right algorithm implemented in their system, why not use it for the passwords? The only scenario is that there are old, unmigrated passwords. A simple way to migrate passwords to a new algorithm is either to send a "change your password" email, or to simply re-hash the password on the next login of the user (when you have the plantext password submitted with the request)