Your files stay on your device

WebRTC Loopback Test: Local ICE Gathering

Two local peer connections over a data channel: no media, no servers, ICE candidates disclosed before you run.

Before you run it, what this reveals

Gathering ICE candidates enumerates network interfaces; host candidates carry your LAN addresses and mDNS names. Nothing leaves this tab: the second connection is another object in the same page, and only a USER-CLICKED run gathers anything.

This is a loopback test: two RTCPeerConnection objects in this page negotiate with each other over a data channel. No media is captured, no STUN/TURN server is configured, and no packet ever leaves the machine.

read, then acknowledge
Rules this tool follows
  • Gathering ICE candidates enumerates network interfaces; host candidates carry your LAN addresses and mDNS names. Nothing leaves this tab: the second connection is another object in the same page, and only a USER-CLICKED run gathers anything.
  • This is a loopback test: two RTCPeerConnection objects in this page negotiate with each other over a data channel. No media is captured, no STUN/TURN server is configured, and no packet ever leaves the machine.
  • Close releases both connections and every transport; the candidate list lives in page memory only. The active indicator goes dark the moment the run ends; an idle page here holds zero WebRTC state.
  • The acknowledge checkbox is the plan’s pre-run disclosure gate: the run button stays disabled until you have read what candidate gathering means.
Nothing in yet

Paste, drop, or type to begin. Everything stays on this device.

Next door in Device

All device tools