Use the tools to narrow the owner of a response. Do not treat a pasted capture as proof of every environment or request context.
Capture the response as delivered
Keep status, Location, cache fields, content type, X-Robots-Tag, and relevant HTML together. Record the exact URL and request context that produced them.
- Relative and absolute redirect targets
- Host and scheme changes
- Header and HTML directive conflicts
- Final response status and representation
Use unknowns as test cases
If the capture omits a request header, intermediate hop, CDN state, or authenticated variant, mark it unknown. That missing field becomes the next reproducible test rather than an excuse for a broad configuration change.
A bounded network path
Log files and IP addresses stay in the browser. Response headers, redirect chains and robots.txt rules can also be pasted and analysed locally. Their optional live modes send one public URL to a protected gateway with private-network blocking, redirect and response caps, a proof challenge and rate limits.
This is a single-URL diagnostic request, not an unrestricted crawler, port scanner or authenticated-site inspection.