Verifying a downloaded ISO
Use SHA-256 against the publisher's checksum. If even one byte was tampered with, the digests differ. MD5 and SHA-1 are fine for accidental corruption but do not use them against an attacker.
Hesabu hash za MD5, SHA-1, SHA-256, SHA-384, SHA-512 na CRC32 kutoka kwa maandishi au faili, moja kwa moja katika kivinjari chako. Hakuna kinachopakiwa.
La. Hashing yote hufanyika kabisa katika kivinjari chako kupitia JavaScript na Web Crypto API. Hakuna ombi la mtandao linalofanywa unapoingiza maandishi au kuchagua faili. Unaweza kuthibitisha hili katika Network tab ya kivinjari.
Kwa uadilifu wa faili (checksum) tumia MD5 au SHA-256 — zote mbili ni sawa kwa matumizi yasiyo ya usalama. Kwa usalama (hashing ya nywila, saini) tumia SHA-256 au SHA-512, kamwe MD5 au SHA-1 (zote mbili zimevunjika kwa upinzani wa mgongano). CRC32 inasaidia tu kugundua uharibifu wa data kwa bahati mbaya, siyo kwa usalama.
Achia faili hapa, au bofya ili kuvinjari
Aina yoyote ya faili. Inafanya kazi na faili kubwa (kusoma kwa vipande).
Kidokezo: hash zinahesabiwa moja kwa moja unapoandika. Ondoa algoriti usizohitaji kwa hashing ya faili ya haraka zaidi.
Haraka, ya faragha, na inashughulikia kila algoriti ya hash ya kawaida.
Hashing yote hufanyika katika kivinjari chako. Maandishi na faili zako hazitumwi, kuhifadhiwa au kurekodiwa popote.
MD5, SHA-1, SHA-256, SHA-384, SHA-512 na CRC32 — ziangalie zote kwa pamoja, au chagua tu zile unazohitaji.
Achia faili yoyote (ikiwa ni pamoja na faili za GB nyingi) na upate hash zote na upau wa maendeleo wa moja kwa moja. Kusoma kwa vipande kunaweka kumbukumbu chini.
Inapatikana katika lugha 25 na utambuzi wa kivinjari moja kwa moja. Msaada wa RTL kwa Kiarabu, Kiajemi na Kiurdu.
Hash zinasasishwa unapoandika (na debounce fupi). Nakili kwa mbofyo mmoja kwa kila matokeo. Badilisha kati ya herufi kubwa/ndogo.
Hutumia Web Crypto API ya asili ya kivinjari kwa hash za SHA — utekelezaji sawa ambao vivinjari hutumia kwa TLS na uadilifu wa subresource.
Web Crypto API for SHA family, streaming for large files.
For text input we encode it to UTF-8 bytes via TextEncoder. For files, we read them with File.arrayBuffer for small files or stream them through TransformStream for files larger than ~100 MB.
crypto.subtle.digest('SHA-256', bytes) computes the hash using the browser's hardware-accelerated implementation. This is the same algorithm OpenSSL uses, just run inside the V8 / JavaScriptCore sandbox. SHA-1, SHA-384, SHA-512 work the same way.
MD5 and CRC32 aren't in Web Crypto (because both are cryptographically broken or not cryptographic). We ship tiny WASM implementations (~5 KB each) that compute them with the same streaming pattern.
Results are shown in hex format with a one-click copy button next to each. We also offer Base64 output for the SHA family — common when comparing against AWS S3 ETags or HTTP Content-Digest headers.
Hashing has many uses — choose the right algorithm for the job.
Use SHA-256 against the publisher's checksum. If even one byte was tampered with, the digests differ. MD5 and SHA-1 are fine for accidental corruption but do not use them against an attacker.
Hash a set of photos with SHA-1 (or even MD5 if speed matters more than collision resistance). Identical hashes mean identical bytes — useful for cleaning duplicate uploads.
AWS S3 uses MD5 for single-part objects and a different scheme for multipart. iKit gives you the raw MD5 instantly, so you can verify whether your local file matches what S3 has.
Hash the original and the backup with SHA-256 separately, compare the two strings. Same hash = identical content. Different hash = the backup is corrupted or out of date.
Some online hashers upload your file just to compute a checksum — exactly the wrong way around for a privacy-sensitive operation. iKit's hash generator computes everything in the browser using Web Crypto, so even confidential or private files are hashed without ever leaving your machine.
Mafunzo ya kina na ulinganishaji wa zana kutoka blogu ya iKit.
Compare a downloaded file's checksum against the publisher's — entirely in your browser.
Hash digests are often Base64-encoded for transport; the same encoding shows up in many other places.
La. Hashing yote hufanyika kabisa katika kivinjari chako kupitia JavaScript na Web Crypto API. Hakuna ombi la mtandao linalofanywa unapoingiza maandishi au kuchagua faili. Unaweza kuthibitisha hili katika Network tab ya kivinjari.
Kwa uadilifu wa faili (checksum) tumia MD5 au SHA-256 — zote mbili ni sawa kwa matumizi yasiyo ya usalama. Kwa usalama (hashing ya nywila, saini) tumia SHA-256 au SHA-512, kamwe MD5 au SHA-1 (zote mbili zimevunjika kwa upinzani wa mgongano). CRC32 inasaidia tu kugundua uharibifu wa data kwa bahati mbaya, siyo kwa usalama.
Kwa checksums za faili na uthibitisho wa uadilifu dhidi ya uharibifu wa bahati mbaya, ndiyo — MD5 na SHA-1 bado zinatumika sana (mf., kwenye kurasa za upakuaji). Kwa madhumuni muhimu ya usalama (nywila, saini, cheti), hapana — zote mbili zina mashambulizi ya mgongano yanayojulikana. Tumia SHA-256 au juu zaidi kwa chochote nyeti cha usalama.
Ndiyo. Faili husomwa katika vipande vya 2 MB na maendeleo ya moja kwa moja. MD5 na CRC32 huchakatwa kwa ukamilifu (kumbukumbu ya kudumu). Hash za SHA zinahitaji kupakia faili kwenye kumbukumbu kwa sababu ya vikwazo vya Web Crypto API, kwa hivyo faili zaidi ya ~2 GB zinaweza zisifanye kazi kwenye vivinjari vyote.
Kila algoriti hutoa digest ya ukubwa uliowekwa: MD5 = 128 bits (32 hex), SHA-1 = 160 bits (40 hex), SHA-256 = 256 bits (64 hex), SHA-384 = 384 bits (96 hex), SHA-512 = 512 bits (128 hex), CRC32 = 32 bits (8 hex).