Known limitations

Clear about what the web can and cannot prove.

This page records the current product boundary. It will change only when implementation and field evidence change.

The rescue domain is a live field experiment.

The secure website and the separate plain-HTTP rescue endpoint are live. The endpoint passes deterministic production checks, but it has not yet passed the ten-network captive field gate and must not be described as broadly proven.

A browser cannot prove which network carried a request.

A successful page load may use cellular data or another interface. WiFi 4 Breakfast never treats an ordinary browser response as proof that the selected Wi-Fi works.

Modern browsers may try HTTPS first.

A bare domain can trigger an HTTPS attempt before plain HTTP. The current same-host HTTPS companion may keep the browser on the secure page instead of reaching the rescue request. Browser and captive-network field testing will determine the final topology.

Plain HTTP is not trustworthy content.

A public network can intercept or modify an unencrypted response. The rescue page never requests credentials, personal details, payment, or account information.

Guided diagnosis uses your answers, not hidden network access.

The secure website cannot inspect your SSID, BSSID, VPN route, DNS configuration, gateway, portal URL, or network traffic. It offers reversible guidance from the answers you select locally.

Recovery performance is not established yet.

The deterministic local contracts are tested, but the ten-network captive field gate is still open. No recovery-rate or superiority claim is published.