diafygi/webrtc-ips resource
Demo: https://diafygi.github.io/webrtc-ips/ observed · 2026-08-28
Health v2 · maintenance only
32/100
- Activity 0
- Release rhythm 35
- Longevity 100
Flags: no_releases
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 4237
- days_rel: n/a
- days_push: 980
- n_releases_24m: 0
Adoption not part of the score
3453 stars · 589 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
A demo and code snippet showing how WebRTC STUN requests in Firefox and Chrome expose a user's local and public IP addresses to JavaScript. It demonstrates a browser privacy leak that bypasses ad blockers and the developer console.
Use cases
- check if my browser leaks my ip via webrtc
- demonstrate webrtc ip leak to users
- test whether adblock blocks stun requests
- learn how webrtc stun exposes local ip addresses
- show privacy risks of browser tracking
When to choose
- you want a minimal copy-paste demo of the WebRTC IP leak
- you are educating users or testing browsers for STUN-based IP exposure
When to avoid
- you need a maintained production library for IP detection
- you need a fix or browser extension that blocks the leak rather than demonstrating it
- you need IPv6 or modern browser guarantees, as the demo predates current WebRTC behavior
Facets
learning-resource · maturity maintenance
security privacy developer-tools privacy browser-extensions web-development security browser webrtc stun ip-leak browser-fingerprinting demo javascript web-server
1 source
- readme: https://github.com/diafygi/webrtc-ips · fetched 2026-08-28 · 1ff35ea03c64
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| diafygi/webrtc-ips | main | 32 |
For agents
markdown · JSON · MCP: product_card(name="diafygi/webrtc-ips")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem