SimplyScan logoSimplyScan
What We ScanPricingFree ToolsBlogCreate AccountLog In
  1. Home
  2. Free Tools
  3. HMAC Generator
Free Tool · Runs in your browser

Free HMAC Generator (SHA-256 / SHA-512)

Compute an HMAC signature from a message and secret key · SHA-256/384/512, hex or Base64 output, all in your browser via Web Crypto.

100% client-side · nothing you enter is ever sent to a server or stored.

Preview · sign in with a free account to run it

How to use it

  1. Paste the message, usually a webhook's raw request body, or load it from a file so every byte is kept.
  2. Enter the shared secret.
  3. Choose SHA-256, SHA-384 or SHA-512, and hex or Base64 output to match what the sender uses.
  4. Paste the signature from the request header to verify it, or turn on the Stripe preset and paste the Stripe-Signature header.

Example

Input

Message    {"id":"evt_123","type":"payment.succeeded"}
Secret     whsec_test_secret
Algorithm  SHA-256 · hex

Result

4c500144dd7f1eeaa27e2bd1058a873c46264c1c17532b0a06c5d065c220a1d1

Why signatures fail to match

The body was re-serialised
Parsing the JSON and printing it again changes spaces and key order, so the bytes differ. Sign the raw body exactly as it was received.
The provider signs more than the body
Stripe signs timestamp.body (the t= value, a dot, then the raw body). Use the Stripe preset to build that string.
Wrong encoding
GitHub sends hex (sha256=…). Others send Base64. Match the provider.
Wrong secret
Test and live modes usually have different signing secrets.

Go deeper

  • Webhook Signature Verification: Stop Trusting Unsigned Payloads

Page updated 21 November 2026

Frequently asked questions

What is HMAC used for?

Authenticating that a message came from someone holding the shared secret · most commonly webhook signatures (Stripe, GitHub, Slack) and signed API requests. The receiver recomputes the HMAC and compares.

Can I verify a Stripe or GitHub webhook signature here?

Yes · paste the raw payload as the message and your webhook secret as the key, choose SHA-256, and compare the output to the signature header (v1= for Stripe, sha256= for GitHub).

Should my server compare signatures with ===?

Use a constant-time comparison, such as crypto.timingSafeEqual in Node, so an attacker can't learn the signature from response times.

Want the full picture?

This tool covers one narrow check. A full SimplyScan runs 60 checks across 14 categories · exposed keys, RLS, XSS, auth, and speed · in 30 seconds.

Run a full security scan

Related tools

PKCE Generator

Generate a spec-compliant PKCE pair · a random code_verifier and its SHA-256 code_challenge · for testing OAuth 2.0 authorization-code flows.

Basic Auth Generator

Turn a username and password into a ready Authorization: Basic header · encoded locally, never transmitted.

CSP Generator

Build a Content-Security-Policy header from scratch · pick directives and sources, and get a copy-ready header with the risky options explained.

SimplyScan logoSimplyScan

Security Scanner for Vibe-Coded Apps.

Product

See What We ScanHow It WorksView Pricing

Resources

Security BlogSecurity ChecklistTrust BadgeUptime MonitoringIntegrationsMCP Server (Claude, Cursor & Windsurf)API DocumentationBackend Audit GuideThreat Detection GuideFAQTerms of ServicePrivacy Policy

Platforms

All platforms →Lovable ScannerBolt.new ScannerCursor ScannerReplit Scannerv0.dev ScannerWindsurf ScannerBubble Scanner

Free Tools

All free tools →SSL CheckerSecurity HeadersDNS Security CheckerCORS TesterJWT DebuggerCSP EvaluatorHash GeneratorSEO Checker

Account

Create AccountLog In

© 2026 SimplyScan. All rights reserved.