SHA-3 aur Keccak-256 mein kya farq hai?

Ye wahi Keccak sponge chalate hain lekin padding se pehle ek alag domain-separation byte append karte hain (SHA-3 ke liye 0x06, Keccak ke liye 0x01). Yeh ek farq unke digests ko poori tarah alag bana deta hai, isliye SHA3-256 se hash ki gayi value kabhi Keccak-256 se hash ki gayi ussi value ke barabar nahi hogi.

Ethereum SHA3-256 ke bajaye Keccak-256 kyun use karta hai?

Ethereum ne NIST ke SHA-3 ko thodi alag padding ke saath finalize karne se pehle original Keccak submission se Keccak-256 apnaaya. Compatible rehne ke liye Ethereum aur Solidity ke keccak256 ne original variant rakha, isiliye addresses aur function selectors Keccak-256 par bane hain.

SHAKE128 aur SHAKE256 kya hain?

Ye extendable-output functions (XOFs) hain: ek fixed size ke bajaye aap chunte hain ki aapko kitne bits digest chahiye. 128 aur 256 unki security strength ko batate hain, output length ko nahi, isliye aap kisi bhi ek se 128, 256, 512 ya usse zyada bits maang sakte hain.

ABI-encoded data par ek keccak256 call se match karne ke liye main raw bytes kaise hash karoon?

Input toggle ko Hex par switch karein aur bytes ko hexadecimal ke roop mein paste karein — ek optional 0x prefix aur spaces theek hain. Tool un exact bytes ko hash karta hai, unke UTF-8 text ko nahi, jo encoded data par ek Solidity keccak256 expect karta hai.

Kya SHA-3 sirf SHA-256 ka ek tez ya zyada secure version hai?

Nahi. SHA-3 ek poori tarah alag design hai — SHA-256 ke peeche wali Merkle–Damgård construction ke bajaye ek Keccak sponge — jise ek standardized alternative ke roop mein chuna gaya. Same digest size par ye comparable collision resistance dete hain, aur inke outputs poori tarah alag hote hain, isliye SHA-3 ek drop-in replacement nahi hai.

SHAKE ke liye main kaunsi output length chunoon?

Jo specification aap implement kar rahe hain woh jo maange usse match karein. Ek common default SHAKE128 ke liye 256 bits aur SHAKE256 ke liye 512 bits hai, lekin 8 bits ka koi bhi positive multiple kaam karta hai — yeh tool woh defaults bhar deta hai aur aapko unhe override karne deta hai.

SHA-3 & Keccak Hash Generator

Text ya hex bytes se SHA3-224/256/384/512, Keccak-256/512 aur SHAKE128/256 digests compute karein, seedhe aapke browser mein.

SHA-3 & Keccak Hash Generator poori tarah aapke browser mein chalta hai. Jo text aur hex bytes aap hash karte hain woh aapke device par process hote hain aur kabhi ArrayKit ko upload nahi hote.

SHA-256 & SHA-1 Hash tool kholein

SHA-3 & Keccak Hash Generator ke baare mein

SHA-3 & Keccak Hash Generator poore FIPS 202 family — SHA3-224, SHA3-256, SHA3-384 aur SHA3-512 — plus original Keccak-256 aur Keccak-512 aur SHAKE128/SHAKE256 extendable-output functions ko compute karta hai. UTF-8 text type karein ya raw bytes hash karne ke liye hex mode par switch karein, aur lowercase digest aap type karte hi update hota hai. Yeh in algorithms ke aas-paas ki rozmarra confusion ke liye bana hai: SHA3-256 aur Keccak-256 ek jaise dikhte hain lekin ek padding byte se alag hote hain, aur Ethereum ne standard finalize hone se pehle Keccak-256 par decide kiya tha. Ise ek Ethereum function selector derive karne, ek Solidity keccak256 result verify karne, ek SHA-3 checksum check karne, ya ek SHAKE output length chunne ke liye use karein. Har digest aapke browser mein compute hota hai, isliye jo values aap hash karte hain woh aapke device par rehti hain.

Features

NIST FIPS 202 se SHA3-224, SHA3-256, SHA3-384 aur SHA3-512 cover karta hai
Ethereum bhar mein use hone wale original Keccak-256 aur Keccak-512 shamil karta hai
SHAKE128 aur SHAKE256 aapke chune hue byte-aligned output length ke saath
UTF-8 text hash karein ya ek one-click toggle se raw hex bytes paste karein
Digest aap type karte hi live update hota hai aur ek click mein copy hota hai
Digest length bits mein dikhata hai taaki aap sahi variant confirm kar sakein
Jab paste kiya hex odd length ya bure characters wala ho to saaf error
Poori tarah aapke browser mein chalta hai — jo aap hash karte hain kuch upload nahi hota

SHA-3 & Keccak Hash Generator kaise use karein

Ek algorithm chunein — SHA3-256, Keccak-256, SHAKE256, aur bhi
Text hash karne ke liye UTF-8 chunein ya raw bytes hash karne ke liye Hex
Apna input type ya paste karein; digest turant dikhta hai
SHAKE ke liye output length bits mein set karein, phir hex digest copy karein

Example

Input

algorithm: Keccak-256
input: "" (empty string)

Output

c5d2460186f7233c927e7db2dcc703c0e500b653ca82273b7bfad8045d85a470

Empty-string Keccak-256 hash jispar Ethereum tooling har jagah depend karti hai.

Common errors aur troubleshooting

SHA3-256 aur Keccak-256 ek hi text ke liye alag results dete hain. — Yeh expected hai — ye alag padding use karte hain. Ethereum aur Solidity ke keccak256 ke liye Keccak-256 use karein; NIST-standard hash ke liye SHA3-256 use karein.
Hex mode odd number of digits batata hai. — Har byte do hex characters ka hota hai, isliye input ki length even honi chahiye. Koi stray nibble ya non-hex character hataayein aur dobara try karein.
Ek SHAKE digest expected se lamba ya chhota hai. — SHAKE length bits mein set hoti hai, bytes mein nahi — 256 bits hai 64 hex characters. Sunishchit karein ki length 8 ka ek positive multiple ho.
Digest mere Solidity keccak256 output se match nahi karta. — Solidity ABI-encoded value ke raw bytes ko hash karta hai. Hex mode par switch karein aur human-readable text ke bajaye wahi exact bytes paste karein.

Aksar pooche jaane wale sawaal

SHA-3 aur Keccak-256 mein kya farq hai?: Ye wahi Keccak sponge chalate hain lekin padding se pehle ek alag domain-separation byte append karte hain (SHA-3 ke liye 0x06, Keccak ke liye 0x01). Yeh ek farq unke digests ko poori tarah alag bana deta hai, isliye SHA3-256 se hash ki gayi value kabhi Keccak-256 se hash ki gayi ussi value ke barabar nahi hogi.
Ethereum SHA3-256 ke bajaye Keccak-256 kyun use karta hai?: Ethereum ne NIST ke SHA-3 ko thodi alag padding ke saath finalize karne se pehle original Keccak submission se Keccak-256 apnaaya. Compatible rehne ke liye Ethereum aur Solidity ke keccak256 ne original variant rakha, isiliye addresses aur function selectors Keccak-256 par bane hain.
SHAKE128 aur SHAKE256 kya hain?: Ye extendable-output functions (XOFs) hain: ek fixed size ke bajaye aap chunte hain ki aapko kitne bits digest chahiye. 128 aur 256 unki security strength ko batate hain, output length ko nahi, isliye aap kisi bhi ek se 128, 256, 512 ya usse zyada bits maang sakte hain.
ABI-encoded data par ek keccak256 call se match karne ke liye main raw bytes kaise hash karoon?: Input toggle ko Hex par switch karein aur bytes ko hexadecimal ke roop mein paste karein — ek optional 0x prefix aur spaces theek hain. Tool un exact bytes ko hash karta hai, unke UTF-8 text ko nahi, jo encoded data par ek Solidity keccak256 expect karta hai.
Kya SHA-3 sirf SHA-256 ka ek tez ya zyada secure version hai?: Nahi. SHA-3 ek poori tarah alag design hai — SHA-256 ke peeche wali Merkle–Damgård construction ke bajaye ek Keccak sponge — jise ek standardized alternative ke roop mein chuna gaya. Same digest size par ye comparable collision resistance dete hain, aur inke outputs poori tarah alag hote hain, isliye SHA-3 ek drop-in replacement nahi hai.
SHAKE ke liye main kaunsi output length chunoon?: Jo specification aap implement kar rahe hain woh jo maange usse match karein. Ek common default SHAKE128 ke liye 256 bits aur SHAKE256 ke liye 512 bits hai, lekin 8 bits ka koi bhi positive multiple kaam karta hai — yeh tool woh defaults bhar deta hai aur aapko unhe override karne deta hai.

Related tools

Hash Generator — Web Crypto API ke through SHA-256 / SHA-1 / SHA-384 / SHA-512.
File Hash & Checksum — Kisi file ke MD5, SHA-1, SHA-256 aur SHA-512 checksums compute karein aur expected hash se verify karein.
HMAC Generator — Ek message ko secret key se SHA-256/512 HMAC se sign karein
Base64 Encode / Decode — UTF-8 safe Base64 encoding aur decoding.
AES Encryption Tool — Text ko passphrase se AES-256-GCM se encrypt aur decrypt karein
X.509 Certificate Decoder — Ek PEM ya DER certificate ko subject, issuer, validity, SANs aur fingerprints mein decode karein.