⌁ NETWORK LENSBROWSER → NETWORK → SERVER Diagnostic workspace
UNDERSTAND YOUR CONNECTION

Find where the
traffic stops.

A practical inspection of the traffic your network lets through.
Test transfers, live connections, and the small details in between.

01 / CONFIGURE A RUNSynthetic data only · no files uploaded
Fine-tune the probes

Quick scans cap transfers at 1 MiB and idle waits at 3 seconds. Full scans cap transfers at 8 MiB. Extended runs use your selected limits, test them once, and finish. No continuous load.

TESTS COMPLETE—
PASSED—
NEEDS ATTENTION—
PAYLOAD OBSERVED—
NEGOTIATED PROTOCOL—
02 / LIVE TEST RESULTSReady when you are
◎

Your connection, under the lens.

Start a scan to see each request, its timing,
and whether the expected data made it through.

KNOW THE BOUNDARIES

A diagnosis, with the evidence attached.

What we measureHTTP methods, upload/download size and integrity, content types, compression, range requests, redirects, large headers and URLs, CORS/preflights, parallel requests, streamed responses, SSE, streaming uploads, WebSocket echo and idle survival.

What needs other toolsRaw TCP/UDP, arbitrary ports, DNS filtering, certificate chains/TLS interception, explicit proxy CONNECT rules, forced HTTP/1 vs HTTP/2 vs HTTP/3, and destination categories. WebRTC/WebTransport need dedicated remote infrastructure and are not tested here.

How to read failuresThis tests two controlled hostnames on HTTPS port 443. Browser restrictions, extensions, server/hosting limits, and network outages can resemble proxy blocks. No test bypasses restrictions. An observed size cutoff is bounded by tested sizes, not an exact policy limit.