Browser-local HTTP response log reader
Summarize pasted redirect response headers
Summarize status and Location lines from response headers you already collected. This browser-local reader does not request URLs or verify a redirect chain.
Paste response headers you already collected with curl -I -L or verbose curl output. This browser-local reader lists each captured HTTP status line and its Location header, if present. It does not contact a server, validate a destination, or prove that the pasted blocks belong to one complete redirect chain.
Paste raw header output. Lines beginning with < from curl verbose mode are accepted. Other lines, including request URLs and response bodies, are ignored.
Paste one or more response header blocks, then summarize them.
What the reader reports
- Each captured status line, in the order it appears, and its numeric status code.
- The first
Locationheader captured in that response block, including its original text. - A review flag when a captured 3xx response block has no
Locationheader in the pasted text.
Repeated status blocks are listed separately. This is useful when the pasted output contains an interim response, proxy response, or more than one request. The summary does not decide which block is the final destination, whether blocks connect to each other, or whether a redirect is appropriate. Compare the output with the command and server you actually checked.
Example input
HTTP/2 301
location: https://www.example.com/new-path
HTTP/2 200
content-type: text/html
For this illustrative text, the reader reports two captured response blocks and the Location text on the first. The example is not a live result or a claim about any website.
Collecting and interpreting response headers
curl's -I option requests headers, and -L follows redirects. Its manual documents the command options and response behavior. HTTP status and redirect semantics depend on the responses actually returned by the server. This worksheet summarizes text you collected; it cannot establish that a live URL currently behaves the same way.
- curl manual — command-line options, including header-only requests and redirect following.
- RFC 9110: HTTP Semantics — status codes, redirection, and the Location field.
- Google Search Central: site moves with URL changes — mapping URLs and testing redirects during a move.
- Redirect-map coverage checker — compare a pasted old-URL inventory with redirect-map source rows.
Nothing you paste is uploaded or saved by this page. The report describes only recognized lines in the current text field; it does not fetch URLs or provide a server-side redirect audit.
How it works
Paste raw HTTP response headers, including status lines and any Location fields. The browser lists captured response blocks and flags 3xx blocks without a captured Location header; it does not fetch URLs or infer omitted responses.
Good to know
Does the reader check a live URL?
No. It parses only text you paste. It sends no request and cannot confirm a server response or destination.
Does each listed block form one redirect chain?
The reader preserves the order of recognized status lines, but does not infer that blocks connect or that the text contains every response. Review the command output and your own test context.
What does a missing Location flag mean?
It means no Location header was captured in that pasted block. It does not determine whether the server response was complete or whether a redirect is correct.
Impact — TODO: apply/approval and configure referral URL — referral link not configured.
CJ Affiliate — TODO: apply/approval and configure referral URL — referral link not configured.
PartnerStack — TODO: apply/approval and configure referral URL — referral link not configured.