WebRTC Leak Test lives at /apps/webrtc-leak-test/. The route is the public Aerod app URL for WebRTC candidate exposure checks.
The app runtime is hosted inside the Aerod repo and mounted directly by the Astro page. The app itself should remain responsible for the test workflow, result cards, advanced ICE candidate table, and copy/export behavior.
Route standard
/apps/webrtc-leak-test/Keep WebRTC on its single public route, /apps/webrtc-leak-test/, and do not duplicate it under /leak-tests, /tools, or another app path. The WebRTC page should stay separate from IP Lookup because the search intent and result model are different.
Runtime location
public/apps/webrtc-leak-test/runtime/
public/apps/webrtc-leak-test/runtime/assets/The Astro page handles the canonical URL, metadata, SoftwareApplication schema, breadcrumb schema, FAQ schema, and a JavaScript-disabled fallback. The built Vue/Vite runtime handles the browser-side WebRTC test.
Result scope
The WebRTC app may report:
- Browser support for WebRTC.
- ICE candidates gathered in the current session.
- Public-looking IP candidates.
- Private/local IP candidates.
- Hostname or mDNS-obfuscated candidate values.
- Advanced candidate details for technical review.
A clean result should not be described as proof of anonymity. It only means the current browser session did not expose an obvious WebRTC IP leak during that test run.
Data handling review
Before release changes, confirm whether the WebRTC app:
- Uses public STUN servers only for browser-side candidate gathering.
- Stores no persistent WebRTC result history.
- Sends no candidate details to Aerod servers.
- Uses no analytics inside the app runtime.
- Presents VPN/proxy mismatches as configuration review signals, not as universal privacy failure claims.