HTTP header parser

Paste headers from a log, a browser's network panel or a raw HTTP request to see them as a table. Runs entirely in your browser: nothing you paste is uploaded, stored or logged.

By the HookWatcher team · Updated

9 headersPOST /webhooks/github HTTP/1.1Looks like: GitHubRepeated: accept
Parsed headers
NameValueNotes
Hostexample.comThe host the request was sent to.
User-AgentGitHub-Hookshot/7b3c1e2The sender's software. Informational only, never authentication.
Content-Typeapplication/jsonHow the body must be parsed (and its charset).
X-GitHub-EventpushGitHub: the event type (push, pull_request, ping…).
X-GitHub-Delivery72d3162e-cc78-11e3-81ab-4c9367dc0958GitHub: unique delivery ID; use it to ignore duplicates.
X-Hub-Signature-256sha256=757107ea0eb2509fc211221cce984b8a37570b6d7586c22c46f4379c8b043e17GitHub: sha256=<HMAC-SHA256 hex of the raw body>.
Authorization•••••• (masked)Credentials. Mask before sharing.
Accept*/*Repeated.
Acceptapplication/jsonRepeated.

What it checks

  • Repeated headers. HTTP allows some headers more than once. Frameworks join them with commas or keep only the last value, which can hide what was sent.
  • The sender. Signature and event headers identify Stripe, GitHub, Shopify, Slack, Razorpay, Twilio, PayPal, WooCommerce, Paddle, Discord and Standard Webhooks senders.
  • Credentials. Authorization, Cookie and API key headers are masked until you choose to show them, so you can screenshot the table safely.
  • Malformed lines. Invalid header names, lines without a colon and obsolete folded values are reported with their line numbers.

Header names are case-insensitive (RFC 9110), so repeated-name detection ignores case. For what each webhook header means in practice, see the webhook inspector page.

See the headers a provider really sends

Point a provider at a free endpoint: headers are recorded in their original order and case, with credentials masked.
Get a free webhook URL No account or card needed. Want to keep it? Create a free account