demo · v142

IoT Fleet Browser

A public web app trying to talk to anything on the LAN — printer JSON-RPC, NAS web UI, smart-bulb hub, home router admin — now has to walk through the LNA WebSocket gate. Pick a device and see how the handshake unfolds, including which devices can never speak WSS (so they never get past the requirement).

Note: live WebSocket connections from this public origin to your LAN are blocked by Chrome 142, which is the whole point. The handshake panel below renders a deterministic trace per scenario; the right-hand "try it" button attempts a real connection so you can confirm Chrome's enforcement.

pick a device on the LAN

Office printer JSON-RPC

ws://192.168.1.50:9100/jsonrpc
ws (no TLS) · vendor firmware

NAS web UI

wss://nas.local:443/api
wss · self-signed cert · mDNS

Smart-bulb hub

ws://192.168.1.20:8080/ctl
ws · Hue / Hubitat style

Router admin

ws://192.168.0.1/admin
ws · CSRF target

Vite dev server HMR

ws://localhost:5173
ws · loopback

Cloud-tunnelled hub

wss://abc-xyz.trycloudflare.com
wss · routed through CDN
—

—

handshake trace

—

try it for real

—

fix it (developer guidance)

—

see also