Webhook HMAC Signer
Sign and verify GitHub, Stripe, and Slack webhook signatures locally.
OpenClean a browser network capture so you can attach it to a ticket without leaking sessions.
Use Chrome DevTools → Network → Save all as HAR with content.
Vendor is safe for support tickets; Strict also strips bodies.
Check domains, redaction counts, and leftover-secret warnings.
Download sanitized HAR or inferred API artifacts without uploading.
A vendor's support team asks for a HAR file to reproduce a checkout bug. The capture holds your session cookie, a bearer token, customer emails and probably a card number in a request body, and sending it as is would hand all of that to a third party.
Paste the HAR JSON (in Chrome DevTools, the Network panel's "Save all as HAR with content") and choose a profile. Minimal masks credentials only: sensitive headers such as Authorization, Cookie and X-API-Key, cookies, token-like query parameters and JWTs anywhere in the text. Vendor, the default, also redacts headers whose names contain token, secret, key or auth, email addresses, secret-looking JSON fields such as password or client_secret, and card-like numbers of 13 to 19 digits. Strict goes further and replaces every query value and every request and response body.
The summary counts entries, redactions and domains, then scans the sanitized output for leftover Bearer tokens or JWT patterns and warns if any remain. Skim the result yourself anyway, since personal data in free-text fields can slip past pattern matching. From the cleaned capture the studio infers an OpenAPI 3.1 draft (long numeric ids and UUIDs in paths become parameters, JSON bodies become schemas), a Postman v2.1 collection and a list of cURL commands. For timing and size statistics on a capture, the HAR summarizer is quicker, and the OpenAPI analysis studio can validate the inferred spec.
The HAR is processed in your browser and never uploaded, and the optional privacy receipt records counts rather than content.
Keyboard shortcut
Answers for this tool. For site-wide help, open the FAQ hub.
Only numeric segments of six or more digits, UUIDs and long hex strings are treated as ids. Shorter numbers stay literal, so rename those paths in the OpenAPI draft yourself.
Paths, methods, query parameter names and status codes survive, but with bodies removed there is nothing to infer schemas from. Use Vendor if you need request and response schemas.
The number of entries, the redaction profile, the number of findings and a short fingerprint of the output. None of the HAR content itself is included.