About privacy
What is WebRTC?
Real-time browser communication and relevant privacy considerations.
Updated: October 9, 2026
WebRTC is a set of web APIs and protocols for real-time audio, video, and arbitrary data between browsers or devices. It is used for video meetings, calls, and peer-to-peer data transfer.
How NetKarte checks it
Check WebRTC in NetKarte's Browser card to see whether the API is exposed to the current page. This result is neither a test call nor an IP leak test.
NetKarte only checks whether RTCPeerConnection exists on Window. It requests no camera or microphone permission, creates no peer connection, and contacts no STUN or TURN server.
Privacy implications
When a real WebRTC connection starts, ICE route discovery handles network information. Merely showing “Available” does not mean a connection started or IP information was sent externally.
Notes
Enterprise policy, browser settings, or extensions may restrict some functionality even when the API exists. NetKarte provides a simple check that the feature entry point is present.
Available, but a call does not work?
An API's presence, network reachability, and microphone permission are separate. For a call with no audio, check that service's permissions, input/output devices, and organizational network restrictions. NetKarte availability does not guarantee call success.
This is not a WebRTC IP-leak test: it gathers no candidate addresses and cannot report “no leak.” You do not need to grant camera or microphone permission to improve the diagnostic display. Investigate the actual calling service's error.
References
- W3C: WebRTC: Real-Time Communication in Browsers (External site)Checked: 2026-10-09
- IETF / RFC Editor: RFC 8825: Overview: Real-Time Protocols for Browser-Based Applications (External site)Checked: 2026-10-09
- MDN Web Docs: RTCPeerConnection (External site)Checked: 2026-10-09