A transparent overview of what each class of 0bps tool measures, calculates or reads — and what it cannot prove.
Speed and Internet Quality tests use browser transfers against Cloudflare edge infrastructure. Multiple transfer sizes help avoid estimating a fast connection from one tiny payload. Results still depend on route, browser, device, VPN and local network conditions.
Ping and Jitter use repeated HTTP round trips because normal web pages cannot send native ICMP echo requests. The result describes browser-to-server timing to the selected 0bps host path.
Transfer, bitrate and data-usage calculators use deterministic arithmetic. Real traffic can differ because of protocol overhead, server limits, adaptive streaming, codec behavior and shared network load.
Audio and video checker modules read supported local-file metadata in the browser. Files are not intentionally uploaded to 0bps for these checks. Codec and container support varies by browser.
DNS Lookup and Reverse DNS use the server DNS resolver for forward records or PTR data. Resolver caches, TTLs and geography can produce answers that differ from another resolver or location. Reverse DNS performs a DNS query only and does not connect to the entered IP.
The 0bps Connection Score is a documented heuristic that combines throughput and responsiveness. It is intended to make raw results easier to read, not to certify an ISP, SLA or application guarantee.
For troubleshooting, compare repeated measurements under similar conditions. Change one variable at a time — Wi-Fi vs Ethernet, VPN on vs off, router position, time of day or device — before drawing conclusions.