Empty string
- Input
- ∅
- Expected output
- da39a3ee5e6b4b0d3255bfef95601890afd80709
The FIPS 180 value for an empty input, used to check whether a SHA-1 implementation is correct before trusting it for anything else.
Carregando ferramenta… / Loading tool…
sha-1 generator
SHA-1 produces a 160-bit digest as 40 hexadecimal characters and still shows up in legacy systems that never migrated away from it. Here you generate the digest and see the real timeline that removed the algorithm from browser certificates.
The FIPS 180 value for an empty input, used to check whether a SHA-1 implementation is correct before trusting it for anything else.
The same "abc" test vector NIST has used since 1995 to validate SHA-1 and SHA-256 implementations, only the algorithm changes.
A short string typical of an old system that still validates against a SHA-1 digest recorded years ago in another database.
Yes. Text, files and HMAC secrets are processed directly in the browser without any upload.
No. Since SHAttered in 2017 and chosen-prefix in 2020, forging a collision costs reachable time and money, not decades of supercomputer time. For anything new, use SHA-256 or SHA-512.
Because changing the identifier of every object would break compatibility with every existing repository. Since version 2.29, released in 2020, Git offers an optional mode that uses SHA-256 instead, but migration is chosen project by project.
No. Chrome, Firefox, and Safari block the connection with a security warning for any TLS certificate that relies on SHA-1, a practice adopted right after the 2017 SHAttered attack.
—Hash legado amplamente reconhecido, mas com fragilidades conhecidas.
Text, files and secrets are processed locally. Nothing is sent to the server.