What browser exposure means
Browser exposure is the set of signals a site can read or infer when a page loads. Some signals are obvious, such as screen size or language. Others come from rendering behavior, device capabilities, storage, permissions, WebRTC behavior, or route context.
Aerod separates these checks into focused apps so each result answers one question clearly.
Common signal groups
| Signal group | Examples | Where to check it |
|---|---|---|
| Public route | Public IP, ASN, ISP or organization, approximate location | IP Lookup |
| Browser exposure | Browser identity, locale, storage, permissions, privacy controls | Browser Leak Test |
| Fingerprint surface | Rendering, WebGL, audio, fonts, screen geometry, client hints | Browser Fingerprint Check |
| WebRTC candidates | Public-looking candidates, private/local candidates, mDNS hostnames | WebRTC Leak Test |
| Route consistency | Proxy/VPN expectation, browser context, timezone, DNS, WebRTC mismatch cues | Proxy/VPN Detection |
| Media-device access | Camera preview, microphone level, selected input devices, and permission state | Online Webcam Test |
How results should be presented
Aerod should avoid alarmist language. A signal being visible does not always mean a user is compromised. The correct presentation is: visible signal, practical risk, limitation, and remediation.
Camera and microphone checks are permission-based device tests, not fingerprint or identity tests. DNS Leak Test remains separate because a real DNS leak test needs controlled resolver-path infrastructure.