$ cd ~/projects icecheck Inspect the WebRTC path between two browsers ──────────────────────────────────────────────────── A two-browser WebRTC diagnostic tool for testing signaling, ICE paths, data channels, and media transport. tags: TypeScript, WebRTC, Web Development ──────────────────────────────────────────────────── ## Exchange an offer, inspect the result Open icecheck in two browsers. Create an offer on the first, copy or share its payload to the second, then return the generated answer. The tool gathers candidates before encoding each payload, so the exchange needs no room or persistent signaling server. Compare LAN-only and STUN-assisted ICE strategies. Connection state, candidate counts, the selected candidate pair, round-trip time, data-channel pings, and synthetic-video statistics help show where a connection failed. A JSON report records the diagnostic results. Open icecheck https://icecheck.vercel.app icecheck on GitHub https://github.com/michidk/icecheck ──────────────────────────────────────────────────── ## Understand what the test covers icecheck tests whether browsers can find a direct WebRTC path and carry data and generated video over it. No TURN server is configured, so the tool does not test relayed connections or measure available bandwidth. Browser privacy controls can hide local addresses or replace them with mDNS names. The app can run locally or as a stateless deployment. Its server supplies public ICE configuration and static application content; copied session descriptions move through the channel you choose. They can contain network and session details, so share them with the intended peer. Configuration and deployment https://github.com/michidk/icecheck#configuration ──────────────────────────────────────────────────── $ ls ~/pages > about curl -L lohr.dev > projects curl -L lohr.dev/projects > blog curl -L lohr.dev/blog > stats curl -L lohr.dev/stats > contact curl -L lohr.dev/contact ──────────────────────────────────────────────────── https://lohr.dev