Yeh HMAC Generator kya compute karta hai?

Yeh ek keyed-hash message authentication code compute karta hai: yeh aapke message ko ek secret key ke saath ek hash function (SHA-256, SHA-1, SHA-384, ya SHA-512) ke under combine karta hai aur resulting signature ko hex aur Base64 ke roop mein return karta hai. Same key waala koi bhi use dobara compute karke message verify kar sakta hai.

Kya main apni key UTF-8 ya hex ke roop mein enter karoon?

Match karein ki aapki service key kaise store karti hai. Agar secret ek normal string ya passphrase hai, to UTF-8 use karein. Agar yeh hex bytes ka ek sequence hai (randomly generated keys ke liye common), to Hex par switch karein taaki exactly same bytes use hon — dono alag signatures produce karte hain.

Mujhe kaunsa HMAC algorithm chunna chahiye?

HMAC-SHA256 zyadatar APIs aur webhooks ke liye default hai. Ek longer signature ke liye SHA-384 ya SHA-512 chunein, ya SHA-1 sirf tab jab aapko ek purane system se match karna ho, kyunki SHA-1 naye designs ke liye weak maana jaata hai.

Main is se ek webhook signature kaise verify karoon?

Raw webhook payload ko message ke roop mein paste karein, shared signing secret ko key ke roop mein enter karein, provider jo algorithm document karta hai use chunein, aur hex ya Base64 output ko unke bheje signature header ke against compare karein. Ek match confirm karta hai ki payload authentic aur unmodified hai.

Output hex aur Base64 dono mein kyun hai?

Alag-alag services same HMAC bytes ko alag encode karti hain — kuch headers lowercase hex use karte hain, doosre Base64 use karte hain. Yeh tool identical signature ke dono encodings dikhata hai taaki aap bina haath se convert kiye woh format copy kar sakein jo aapka API expect karta hai.

HMAC Generator Online

Ek message aur secret key se SHA-256, SHA-1, SHA-384, ya SHA-512 ke saath ek HMAC signature generate karein aapke browser mein. Aapki key local rehti hai.

HMAC Generator poori tarah aapke browser mein Web Crypto API use karke chalta hai. Jo message aap sign karte hain aur jo secret key aap enter karte hain woh kabhi aapke device se bahar nahi jaate aur ArrayKit ko upload nahi hote.

Hash Generator kholein

HMAC Generator ke baare mein

HMAC Generator ek message ko ek secret key se sign karke ek keyed hash produce karta hai — wahi authentication code jo aapka API ya webhook yeh saabit karne ke liye use karta hai ki ek payload se cheddchaad nahi hui. Message aur secret type ya paste karein, SHA-256, SHA-1, SHA-384, ya SHA-512 chunein, aur signature ko hex aur Base64 dono ke roop mein wapas padhein. Key plain UTF-8 text ya ek hex-encoded byte string ho sakti hai, isliye woh usse align karti hai jo bhi aapka server expect karta hai. Yeh un developers ke liye bana hai jo webhook signatures verify karte hain, signed request headers wire up karte hain, ek API ka HMAC scheme test karte hain, ya ek value ko library output ke against check karte hain. Sab kuch aapke device par Web Crypto API se compute hota hai — message aur secret key kabhi aapke browser se bahar nahi jaate.

Features

Kisi bhi message ko ek secret key se sign karein aur HMAC turant padhein
SHA-256, SHA-1, SHA-384, aur SHA-512 hash functions ke beech toggle karein
Signature ko lowercase hex aur standard Base64 ke roop mein saath-saath dekhein
Secret key ko UTF-8 text ya ek hex-encoded byte string ke roop mein enter karein
Server-side aur library HMAC output ke saath byte for byte match karta hai
Hex ya Base64 signature ek click mein copy karein
Jab ek hex key ki odd length ho ya non-hex characters hon to saaf error
Web Crypto API ke zariye aapke device par chalta hai, kuch upload nahi hota

HMAC Generator kaise use karein

Woh hash algorithm chunein jo aapki service use karti hai (SHA-256 sabse common hai)
Jo message aap authenticate karna chahte hain use type ya paste karein
Secret key enter karein aur uske format se match karne ke liye UTF-8 ya Hex chunein
HMAC ko hex ya Base64 ke roop mein padhein aur jo value chahiye use copy karein

Example

Input

message: The quick brown fox jumps over the lazy dog
key: key (UTF-8)
algorithm: SHA-256

Output

hex:    f7bc83f430538424b13298e6aa6fb143ef4d59a14946175997479dbc2d1a3cd8
base64: 97yD9DBThCSxMpjmqm+xQ+9NWaFJRhdZl0edvC0aPNg=

Classic fox sentence ka HMAC-SHA256, "key" se keyed.

Common errors aur troubleshooting

Signature usse match nahi karti jo mera server produce karta hai. — Confirm karein ki aapne same hash (SHA-256 vs SHA-1) aur same key format chuna. a0b1c2 jaisi ek key raw UTF-8 text ke roop mein hex bytes se alag hai — server jaise use padhta hai usse match karne ke liye Hex toggle switch karein.
Error: Hex key must have an even number of digits. — Hex key mode mein har byte do hex characters hai, isliye key length even honi chahiye. Koi bhi stray character hatayein ya missing digit add karein, ya agar key asal mein text hai to UTF-8 mode par switch karein.
API signature ko Base64 chahti hai lekin mere paas sirf hex hai. — Aapko kuch convert karne ki zaroorat nahi — yeh tool same signature ko hex aur Base64 dono ke roop mein dikhata hai. Base64 value ko seedha doosri row se copy karein.
Trailing newline ya spaces result badal dete hain. — HMAC message ke har byte ko cover karta hai, isliye ek trailing newline ya space ek alag code produce karta hai. Apni service jo exact bytes bhejti hai unhe bina koi added whitespace ke sign karein.

Aksar pooche jaane wale sawaal

Yeh HMAC Generator kya compute karta hai?: Yeh ek keyed-hash message authentication code compute karta hai: yeh aapke message ko ek secret key ke saath ek hash function (SHA-256, SHA-1, SHA-384, ya SHA-512) ke under combine karta hai aur resulting signature ko hex aur Base64 ke roop mein return karta hai. Same key waala koi bhi use dobara compute karke message verify kar sakta hai.
Kya main apni key UTF-8 ya hex ke roop mein enter karoon?: Match karein ki aapki service key kaise store karti hai. Agar secret ek normal string ya passphrase hai, to UTF-8 use karein. Agar yeh hex bytes ka ek sequence hai (randomly generated keys ke liye common), to Hex par switch karein taaki exactly same bytes use hon — dono alag signatures produce karte hain.
Mujhe kaunsa HMAC algorithm chunna chahiye?: HMAC-SHA256 zyadatar APIs aur webhooks ke liye default hai. Ek longer signature ke liye SHA-384 ya SHA-512 chunein, ya SHA-1 sirf tab jab aapko ek purane system se match karna ho, kyunki SHA-1 naye designs ke liye weak maana jaata hai.
Main is se ek webhook signature kaise verify karoon?: Raw webhook payload ko message ke roop mein paste karein, shared signing secret ko key ke roop mein enter karein, provider jo algorithm document karta hai use chunein, aur hex ya Base64 output ko unke bheje signature header ke against compare karein. Ek match confirm karta hai ki payload authentic aur unmodified hai.
Kya mera message ya secret key kahin upload hota hai?: Nahi. HMAC aapke browser mein Web Crypto API se compute hota hai. Jo message aap sign karte hain aur jo secret key aap enter karte hain woh kabhi aapke device se bahar nahi jaate aur ArrayKit ya kisi server ko nahi bheje jaate.
Output hex aur Base64 dono mein kyun hai?: Alag-alag services same HMAC bytes ko alag encode karti hain — kuch headers lowercase hex use karte hain, doosre Base64 use karte hain. Yeh tool identical signature ke dono encodings dikhata hai taaki aap bina haath se convert kiye woh format copy kar sakein jo aapka API expect karta hai.

Related tools

Hash Generator — Web Crypto API ke through SHA-256 / SHA-1 / SHA-384 / SHA-512.
JWT Signer — Ek payload aur secret se JWT (HS256/384/512) banayein aur sign karein — Web Crypto.
JWT Decoder — Ek JWT ka header aur payload decode karein aur exp/iat inspect karein (bina verification ke).
Bcrypt Generator — Ek password ko bcrypt se hash karein ya ek hash verify karein
TOTP / 2FA Generator — Ek base32 secret se time-based one-time passwords (2FA codes) generate karein.
Base64 Encode / Decode — UTF-8 safe Base64 encoding aur decoding.