Raw HTTP fields
Authorization, Proxy-Authorization, Cookie and Set-Cookie are hidden by default. HTTP field names are case-insensitive; HTTP/2/3 names are serialized lowercase.
Parsed fields
duplicate-preservingParser & framing findings
Security-related response fields
presence ≠ correctnessA fast inventory only. Whether a field is appropriate depends on the response type and deployment architecture.
Safe export
Exports remain redacted until you explicitly reveal sensitive values.
Output
Duplicate-aware
Set-Cookie stays separate, while routing/framing duplicates receive special scrutiny.
HTTP/2+ aware
Checks pseudo-header ordering, lowercase names and forbidden connection-specific fields.
Proxy-boundary safety
Surfaces framing ambiguity patterns that commonly matter during request-smuggling reviews.