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.
No network side effects
The current inspectors parse pasted input in the browser. They do not issue an unrestricted server-side request, scan ports, or crawl a target.
Networked diagnostics remain out of scope until egress controls, DNS-rebinding protection, rate limits, response caps, abuse monitoring, and ownership are reviewed.