docs

Browser Exposure Tests

The browser signals Aerod may inspect and how those signals relate to fingerprinting, privacy, and connection exposure.

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, or network paths.

Aerod should make those signals visible and explain how they can combine into a more distinctive profile.

Common signal groups

Signal groupExamplesWhy it matters
Browser and platformUser agent, platform hints, device memory, hardware concurrencyHelps classify the device and browser environment
Locale and timeLanguage, timezone, date formattingCan reveal regional mismatch or profile uniqueness
RenderingCanvas, WebGL, audio behavior, fontsCan vary by hardware, driver, OS, browser, and settings
StorageCookies, local storage, session storage, indexed storageShows persistence and tracking surfaces
PermissionsCamera, microphone, notifications, geolocation promptsIndicates what the browser may expose if granted
Network-related behaviorWebRTC, IP check, DNS guidanceCan reveal route mismatch or connection context

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.