مولّدات التجزئة
SHA-1 hash generator
Try it
SHA-1 digest — legacy interoperability.
Loading…
How to use this tool, examples, and related tips.
Type or paste your input string into the field.
The SHA-1 hash is computed instantly and displayed as a 40-character hexadecimal string.
Copy the hash for your use case.
SHA-1 (Secure Hash Algorithm 1) is a cryptographic hash function developed by the NSA and standardized by NIST in 1995. It produces a 160-bit (20-byte) digest, represented as a 40-character hex string. SHA-1 was the dominant hash function in TLS certificates, Git object storage, and digital signatures for over a decade. However, collision attacks against SHA-1 have been demonstrated in practice — most notably the SHAttered attack in 2017, which produced two different PDF files with identical SHA-1 hashes. SHA-1 is now deprecated for all security-sensitive uses. It remains in use in legacy systems and non-security contexts such as Git object addressing.
Legacy system compatibility — Some older systems, protocols, or APIs still require SHA-1 checksums or identifiers.
Git object hashing — Git historically uses SHA-1 to address commits, trees, blobs, and tags. Understanding SHA-1 is useful when working at Git's internals level.
Non-security checksums — SHA-1 is still acceptable for non-cryptographic uses like deduplication keys or cache identifiers where collision resistance is not a security requirement.
Migration and auditing — Compare SHA-1 hashes from legacy systems against known values during data migration or audit workflows.
Answers about this tool and how your data is handled.
Not for security-sensitive applications. SHA-1 has known practical collision vulnerabilities and is deprecated by NIST and major browser vendors for cryptographic use. Use SHA-256 or SHA-3 for new systems.
SHAttered (2017) was the first practical SHA-1 collision — two different files with identical SHA-1 hashes were produced by a team at Google and CWI Amsterdam. It demonstrated that SHA-1 collision attacks are feasible with sufficient compute resources.
Yes. Git uses SHA-1 internally (though SHA-256 support is being added). Some legacy TLS systems and older software still reference SHA-1. It is acceptable for non-security checksums.
No. Hashing runs entirely in your browser. Nothing is uploaded.
Always 40 hexadecimal characters, representing 160 bits.
نفس الفئة أولاً، ثم أدوات أخرى.
مولّدات التجزئة
SHA-1 digest — legacy interoperability.