Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

A well-designed website cannot read back your password because it never stores a readable copy. It stores a password verifier: the output of a password-hashing function, together with the algorithm and settings used to create it. During login, the site hashes the password you submit with those settings and compares the new result with the stored verifier. A match proves the password is correct without requiring the original text.

This design protects users if a database is stolen, although it does not make weak or reused passwords impossible to guess. The practical goal is to make every offline guess expensive enough that attackers cannot try likely passwords at useful scale.

What a site stores instead of your password

When you create an account, the service should send your password through a password-hashing algorithm designed for human-chosen secrets. The resulting verifier is stored in the account record. A typical record also includes a random salt and the algorithm’s cost parameters, such as memory, iterations and parallelism.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

At login, the application retrieves that record, applies the same algorithm to the submitted password and checks whether the calculated verifier matches. The application does not decrypt anything and does not need to discover the password. If the values match, the submitted password was almost certainly the same secret used during enrollment.

#1 Best Overall
Yojaro 4Pack Silicone Suction Phone Case Mount, Silicon Adhesive Smartphones Stand Sticky, Hands-Free Phone Accessories Holder for Selfies and Videos (Black & White & Translucent & Light Pink)
  • 【Strong Adsorption】The inspiration of the silicone phone suction case comes from the adhesive force of the octopus. Each suction cup phone mount is 3.15 inches long and 2.17 inches wide, with 24 independent suction cups providing a stronger and more stable suction force, so you don't have to worry about your phone falling during use.
  • 【Back of Phone Suction Grip】Remove the adhesive film on the phone suction cup and stick it on the phone case. You can then fix the phone on any smooth surface, which is very convenient. (The phone suction cup cannot be removed and reused after being attached to the phone case. It is recommended to attach it to a regular phone case, not a valuable one.)
  • 【Widely Used】Our non-slip silicone phone sticky grip mount attaches to almost any flat phone case and make it compatible with common mobile phones such as iPhone and Android.You can shoot, watch videos or video calls in the kitchen, gym, dance studio, bathroom and other places.
  • 【Capture the Wonderful Picture】Whether you are a TikTok creator or just like to share videos and photos, this phone suction cup can help you hands-free capture wonderful videos and photos for sharing with friends.
  • 【Note】You can fix the phone suction cup on a smooth surface such as a mirror or glass. If necessary, wipe the suction cup with a damp cloth to obtain stronger suction. Before releasing your hand, make sure the phone is firmly fixed. (Not applicable to rough walls, wooden surfaces, and other uneven surfaces)

The OWASP Password Storage Cheat Sheet states: “Passwords should never be stored in plain text.” A readable database copy would let anyone who gains access to the database immediately impersonate every user, and it would expose people who reused those passwords elsewhere. Reversible encryption has a different weakness: whoever obtains the decryption key can recover every password at once.

A hash is intended to be one-way. Given the verifier, an attacker can still make guesses, hash each guess and compare the result. Security therefore depends on the password’s strength, a unique salt and a deliberately expensive password-hashing function—not on a claim that hashes can never be cracked.

See the OWASP Password Storage Cheat Sheet for the current implementation guidance; hardware and recommended settings change over time.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Hashing, encryption and ordinary fast hashes are different

Technique Can the original value be recovered? Typical purpose Why it is or is not suitable for passwords
Password hashing No practical reverse operation; verification requires hashing a candidate Storing password verifiers Suitable when implemented with a salt and an adaptive cost
Encryption Yes, with the appropriate key Protecting data that must later be read Usually wrong for password verification because a stolen key can reveal every password
Fast cryptographic hash such as SHA-256 Not directly, but guesses are extremely cheap Integrity checks, signatures and content fingerprints Not suitable alone for passwords; attackers can test enormous numbers of guesses with hardware

Fast hashes are valuable for many security tasks precisely because they are fast. Password storage needs the opposite property: a tunable delay and, for modern algorithms, meaningful memory use. The defender performs one calculation per login, while an attacker may perform billions of calculations against a stolen database.

Rank #2
Apple EarPods Headphones with USB-C Plug, Wired Ear Buds with Built-in Remote to Control Music, Phone Calls, and Volume
  • SUPERIOR COMFORT — Unlike traditional circular ear buds, the design of EarPods is defined by the geometry of the ear. Which makes them more comfortable for more people than any other ear bud–style headphones.
  • HIGH-QUALITY AUDIO — The speakers inside EarPods have been engineered to maximize sound output and minimize sound loss, which means you get high-quality audio.
  • BUILT-IN REMOTE — EarPods with USB-C plug also include a built-in remote that lets you adjust the volume, control the playback of music and video, and answer or end calls with a pinch of the cord.
  • COMPATIBILITY — Works with all devices that have a USB-C port.
  • INTEGRATED MICROPHONE — A built-in microphone precisely captures your voice while you’re on the phone, taking a FaceTime call, or summoning Siri — so you’re always heard loud and clear.

Why every password needs a unique salt

A salt is a random, unique value generated for each password. It is normally stored next to the verifier and is not a secret. During hashing, the password and salt are combined, so two accounts using the same password produce different stored values.

  • Precomputed lookup tables become far less useful because an attacker would need a separate table for each salt.
  • An observer cannot identify accounts that share the same password merely by comparing verifier strings.
  • Compromising one account’s salt does not reveal another account’s salt or verifier.

Modern password-hashing functions require a salt, and reputable libraries generally generate and manage it automatically. Do not invent a home-grown salt format or use one global salt for the whole database. Store the complete encoded result produced by the library, including the salt and cost parameters, so verification and future upgrades remain possible.

Adaptive algorithms and the settings they need

An adaptive password-hashing function exposes a work factor that can be increased as servers become faster. The right setting is the highest cost your production environment can sustain while keeping normal authentication responsive and leaving capacity for concurrent users. OWASP’s guidance favors Argon2id where available, with scrypt as an alternative. It treats bcrypt primarily as a legacy option and recommends PBKDF2 when a FIPS-140-validated implementation is required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Algorithm Guidance and example settings Important constraints When it fits
Argon2id OWASP lists, among its minimum configurations, 19 MiB memory, two passes and parallelism one; another option is 46 MiB, one pass and parallelism one. Other listed combinations trade memory for CPU work. Requires a maintained implementation and benchmarking on your servers. Memory settings affect concurrency as well as individual login time. Preferred default for new systems when the platform has a sound implementation.
scrypt One OWASP alternative is N=217, r=8, p=1; lower-memory choices can be paired with higher parallelism. Choose parameters based on available memory, CPU and expected concurrent verification load. Useful where Argon2id is unavailable but a memory-hard function is supported.
bcrypt Use a work factor of at least 10 according to OWASP. Common implementations have a 72-byte input limit. Handle long passwords deliberately rather than silently truncating them. For existing systems or platforms that cannot provide newer choices; do not make it the default for a new design.
PBKDF2-HMAC-SHA-256 OWASP lists 600,000 iterations. Iteration counts must be measured on the target hardware. Select a FIPS-validated implementation when compliance requires it. Environments with FIPS-140 validation requirements or limited algorithm support.

OWASP’s 2025 Cryptographic Failures guidance also identifies Argon2, yescrypt, scrypt and PBKDF2-HMAC-SHA-512 as strong adaptive, salted choices. The recommendation is not a universal parameter recipe: library version, CPU type, available memory, login volume and compliance requirements all affect the safe configuration. The guidance is available in OWASP Top 10:2025 A04, Cryptographic Failures.

Rank #3
PopSockets Adhesive Phone Grip, Holder- Black | Anti-Drop, Kickstand, Secure Comfortable Hold, Black, Create a Mobile Phone Outfit
  • Secure Hold: Our PopSockets adhesive phone grip gives your cell phone a secure, comfortable hold in hand to help prevent drops while texting, taking photos, or scrolling on the go. Designed to stick firmly to most phone cases and devices.
  • Hands-Free Made Easy: Easily turn your PopSocket into a phone stand to prop up your phone anywhere, perfect for watching videos, video calls, or following recipes. A must-have phone holder that keeps your device secure and ready for anything.
  • Compatibility: Works with all phones, tablets, and Kindles. Sticks best to smooth, hard plastic cases and may not adhere to silicone or textured cases. Easily swap your PopTop to change up your style.
  • Black PopSockets: Simple, refined, and endlessly versatile. A timeless essential for any phone.
  • Travel Must-Have for People On the Go: A must-have travel accessory for flights, flying, airports, air travel, airplanes, planes, international trips, cruises, and long travel days. Key gadget for your airport haul, travel accessories and must-haves.

How to choose a work factor without creating a denial of service

Increasing memory or iterations raises the cost of each offline guess, but it also raises the cost of every legitimate login. Excessive settings can consume worker threads or memory during a login flood and become a denial-of-service aid. OWASP gives a general rule that one hash calculation should take less than one second; treat that as a starting guideline, not a universal target.

  1. Benchmark the exact library and build. Test the algorithm on the production-class servers, not a developer laptop.
  2. Measure realistic concurrency. Include normal peak logins, password resets, API authentication and the memory available to other application components.
  3. Raise the cost gradually. Increase memory, passes, iterations or the bcrypt factor until the security benefit conflicts with acceptable latency or capacity.
  4. Load-test failure paths. Rate-limit login attempts and verify that malformed requests, repeated failures and recovery flows cannot trigger unbounded expensive calculations.
  5. Record the selected parameters. Store them in the encoded verifier so a future login can use the settings that created that record.

Compare algorithms using hardware-assisted guessing resistance, memory and CPU demand, implementation availability, compliance status and measured verification latency under expected load. No single number works for every service.

What a pepper adds—and what it complicates

A pepper is an optional secret applied in addition to each account’s salt. Unlike a salt, it is shared across password verifiers and must not be stored in the password database. Keep it in a secrets vault or hardware security module, with access restricted to the authentication service.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

A database-only breach then lacks one ingredient needed to verify guesses. That can add defense when the attacker cannot obtain the application secrets, but it creates an operational dependency:

Rank #4
360° Rotating Stainless Steel Phone Tether Tab (Silvery 3-Pack) - Universal for iPhone & Other Phones (Fits Wristbands/Necklaces/Crossbody Straps)
  • [360 ° Flexible Rotation Design] Comes with a rotatable lanyard ring that supports 360 ° free rotation, effectively solving the problem of twisted and tangled lanyards
  • [Wide compatibility] The ultra-thin 0.02-inch design does not block the charging port at all, and both wired and wireless charging can be used directly without removing the pad. Compatible with most smartphones such as iPhone, compatible with various wristbands, lanyards, crossbody straps, and keychains
  • [Durable and Portable Material] Premium rust-resistant stainless steel material with good flexibility, which not only avoids scratching the phone case, but also has excellent anti rust and anti fading performance
  • [Multi scenario Practical] Paired with a lanyard or wristband, hands-free use can be achieved. The phone is within reach and not easily dropped, ideal for daily commuting and outdoor activities. Suitable for full coverage phone cases, does not support half coverage phone cases
  • [Quality Service] If you find any damage or other issues with the product upon receipt, please contact us immediately. We will handle it quickly
  • The authentication service must retrieve the pepper reliably, including during failover.
  • Rotation is difficult. If the old pepper is lost or compromised, existing verifiers cannot be recomputed with a new pepper without the user’s password.
  • A recovery plan may require forcing password resets, temporarily supporting an old pepper during migration, or re-enrolling users.
  • Do not put the pepper in source code, environment files committed to a repository or the same database backup as the verifiers.

A pepper is therefore an additional control, not a substitute for strong passwords, unique salts, adaptive hashing and database access controls.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

A safe implementation workflow

1. Select a maintained library

Use a well-maintained implementation of Argon2id, scrypt or the algorithm required by your compliance boundary. Let the library generate salts and encode the algorithm identifier and parameters. Avoid writing the primitive yourself or combining a fast hash with ad hoc delays.

2. Hash at enrollment and reset

When a user sets or changes a password, validate the service’s password policy, generate a fresh salt through the library and store only the encoded verifier. Never log the password, include it in analytics, put it in an exception message or send it by email.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

3. Verify without revealing the secret

On login, pass the submitted password and stored verifier to the library’s verification routine. Use the routine’s result rather than decrypting or comparing application-generated plaintext. Return a generic authentication failure so an attacker cannot distinguish an unknown account from a wrong password.

Best Value
Anteel 2 Pack Silicone Suction Cup Phone Case Mount Double Sided, Hands-Free Silicon Phone Grip with Higher Suction Power for Selfies and Videos, Non Slip Phone Accessories (LightPink&White)
  • 【PKYAA Double Sided Silicone Suction Phone Case Mount】PKYAA With Double Sided 40 Strong and Reliable individual suction cups, PKYAA provides a thicken and upgraded universal silicon suction mount for your phone.
  • 【Friendly to Content Creators】If you are a content creator or an online influencer, you can create videos anywhere with this suction mount completely hands free with this silicone cell phone mount for cases.
  • 【HANDS-FREE & Adhere to Mirrors】This Double Sided silicone suction phone case mount allows you to stick your phone to the mirror easily. No longer holding your phone in one hand to watch video tutorials while making up.
  • 【Strong Grip on the Smooth Surface】You can easily hang your phone anywhere with a smooth surface. All you do is you clean off your phone and smooth surface. It is STURDY and it not only sticks to mirrors, it also sticks to windows, it sticks to refrigerators, tiles and other clean, flat surfaces.
  • 【Press Down Firmly Every 30 Minutes】Use your palm or fingers to press the phone down firmly and check it's secure before letting go. Apply even pressure for a few seconds to allow the suction cup to adhere properly. To maintain the grip and prevent accidental falls, it's a good practice to periodically reapply pressure to the suction cup.

4. Protect the surrounding account flow

Rate-limit repeated attempts, monitor abnormal authentication volume, use secure transport, and protect reset tokens as carefully as passwords. A strong verifier cannot compensate for an account takeover through an exposed reset link or an unprotected login endpoint.

Upgrading old verifiers safely

Algorithm migration does not require knowing existing passwords. Store the algorithm and cost information with each verifier, accept mixed formats during a transition, and rehash after a successful login when the stored settings are weaker than the current policy.

  1. Verify the password against the old record.
  2. If verification succeeds and the record is below the current standard, hash the same submitted password with the new algorithm and parameters.
  3. Replace the old verifier atomically, preserving account state and audit information without retaining the password.
  4. Track accounts that never log in again and define a separate reset or retirement policy for hashes that must eventually be removed.

Do not convert an old hash by hashing the hash unless your migration design explicitly accounts for the resulting scheme and its security properties. Rehashing the user’s freshly submitted password gives the new function the intended password input.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Common design mistakes and their fixes

  • Plaintext or encrypted password columns: replace them with a password verifier and remove readable copies from logs, backups and support tools.
  • One global salt: generate a cryptographically random salt for every password.
  • SHA-256 alone: use an adaptive password-hashing function with a benchmarked cost.
  • Blindly copying a parameter from a blog post: benchmark the exact production environment and revisit settings as hardware changes.
  • Silent bcrypt truncation: document and test the 72-byte limitation, or choose a modern algorithm without that constraint.
  • No upgrade path: encode parameters, support mixed algorithms temporarily and rehash on successful authentication.
  • Unplanned pepper rotation: document vault access, backup, incident response and the password-reset process before deploying a pepper.

Why support staff should reset, not reveal, a password

If a service can display your existing password in an account screen or tell it to support staff, it is probably storing a readable or reversibly encrypted copy. A responsible service can send a one-time reset link or let you set a new password after stronger identity checks, but it cannot retrieve the old one from a properly designed verifier. That limitation is a security feature: database administrators and support tools do not gain a universal view of users’ secrets.

Bottom line

Password verification works without password retrieval because the site stores a one-way, salted and deliberately expensive verifier. Prefer Argon2id for new systems when available; use scrypt, bcrypt for legacy compatibility or PBKDF2 for required FIPS-validated deployments according to current guidance. Benchmark the cost, protect any pepper separately, and build an upgrade and reset plan before attackers—or changing hardware—force the issue.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.