SHA-1
For SHA-1, purpose is hashing; current status is Deprecated; planned status is retirement scheduled under SP 800-131A Rev 3 draft; replacement is SHA-2 or SHA-3; source document is SP 800-131A Rev 3 draft, recorded from its source on 2026-08-16; source re-checked 2026-11-18.
- Algorithm
- SHA-1 verified
- Purpose
- hashing our reading
- Current status
- Deprecated our reading
- Planned status
- retirement scheduled under SP 800-131A Rev 3 draft our reading
- Replacement
- SHA-2 or SHA-3 our reading
- Source document
- SP 800-131A Rev 3 draft our reading
Values marked our reading are our classification of what the source says — the source does not print them in those words. The quote below is the evidence for each one; judge it yourself.
Cite as: SHA-1 — NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when (NIST cryptographic algorithm deprecation schedule: what is approved, deprecated, and disallowed, and when), referencesource.org/nist-cryptographic-algorithm-deprecation-schedule/sha-1/, checked 2026-11-18.
What the source says
Rev. 3 proposes moving the minimum classical security strength from 112 bits to 128 bits at the end of 2030, retires ECB confidentiality mode and DSA signature generation, and schedules the retirement of SHA-1 and 224-bit hash functions.
— encryptionconsulting.com, retrieved 2026-08-16
Source
- encryptionconsulting.comhttps://www.encryptionconsulting.com/education-center/nist-ir-8547-sp-800-131a-algorithm-transitions/
Open the page on encryptionconsulting.com that states this — the page quoted above, at its publisher. Unpaid: we earn nothing from this link and it is not an advertisement.
Does your own code still call SHA-1? npx crypto-deprecation-check reads the places where naming an algorithm is the point of the line -- createHash, a JWT alg, Cipher.getInstance, MODE_ECB, generateKeyPair, createECDH, an SSH HostKeyAlgorithms setting, an openssl subcommand -- and prints the status we hold for each with this page's sentence quoted. It fails a build only on a status that is already deprecated or disallowed, says nothing at all about algorithms we hold no record for, and makes no network calls. crypto-deprecation-check on npm