WebRTC Test

Can this browser do real-time calls โ€” safely?

Real-time calling

Detectingโ€ฆ

Capability

WebRTC
โ€ฆ
Peer connections
โ€ฆ
Data channels
โ€ฆ
Device list
โ€ฆ
Detectingโ€ฆ enable JavaScript.

What is WebRTC?

WebRTC powers video calls, voice chat and peer-to-peer data in the browser with no plugins. It needs network paths between peers, which historically could reveal local IP addresses โ€” so browsers changed the rules.

How browsers protect you now

Modern browsers mask private addresses with temporary mDNS names (like *.local) and require permission before revealing camera/microphone labels. This page therefore tests capability โ€” peer connections, data channels, media enumeration โ€” without harvesting addresses. We never trick the browser into leaking what it deliberately hides.

How it works

Open this page and the embedded script queries only documented browser APIs. Nothing is installed, no account is needed, and results reflect your current browser profile โ€” including extensions, private mode and OS display scaling.

Limitations

Support varies by browser. Privacy features (tracking prevention, user-agent reduction, fingerprint randomization) can generalize or withhold values. Treat results as a best-effort live snapshot rather than a certified hardware inventory.

Privacy

Detection runs in your browser. We do not store fingerprints or device reports. The only network call any tool makes is the optional public-IP lookup on /my-ip (via a third-party IP API, disclosed in the privacy policy).

FAQ

Does this test leak my IP?

No. We only check that WebRTC objects exist and a data channel can open. We do not collect ICE candidates or any addresses.

WebRTC shows blocked โ€” will calls fail?

Likely yes in this profile. VPNs, strict extensions or enterprise policy often disable it. Allow WebRTC for your calling app or try a fresh profile.

Related tools

Related guides