HTTP response inspector
Inspect one signed, controlled HTTP response: status, safe headers, payload correlation and browser-reported protocol.
Checking network test availability…
Test this browser’s path to our endpoint
No website URL, credentials or test account is required. This checks our controlled endpoint, not an arbitrary API or another website. Nothing runs until you press the start button.
- Requests
- 1 sequential probe
- Response read limit
- 4 KiB per probe
- Request deadline
- 2 seconds
- Run deadline
- 20 seconds, plus bounded cleanup
Admission reserves an 8 MiB allowance; it does not transfer 8 MiB. Each probe conservatively debits 256 KiB of that allowance. Request headers and admission traffic are additional to the response-body limit.
What this can and cannot establish
These are browser-to-Worker HTTP observations, including application handling and quota checks. They do not isolate Wi-Fi, router, ISP, DNS or TLS delay. Negotiated protocol is reported only when the browser exposes it; unavailable data is not guessed.
A failed request can have several causes. Compare controlled runs under the same conditions and keep this tab in the foreground. No traffic shaping, arbitrary-site scanning or system-wide fault injection is performed.