Aerod apps are designed to explain observable browser, network, and device behavior. A result should identify what was checked, what the current session returned, why it matters, what the test cannot prove, and what the user can review next.
The active app routes are IP Lookup, WebRTC Leak Test, Browser Leak Test, Browser Fingerprint Check, Proxy/VPN Detection, and Online Webcam Test. DNS Leak Test remains planned until controlled resolver infrastructure is available.
Result model
Every diagnostic app should answer five questions:
- What was checked? Identify the browser, network, rendering, permission, media-device, or connection signal involved.
- What was observed? Show the value, behavior, match, mismatch, or warning returned in this session.
- Why does it matter? Explain the practical privacy, security, or device-readiness implication.
- What is the limit? State what the current browser, request, or data source cannot establish.
- What should happen next? Point to a setting, browser profile, provider configuration, permission review, or related Aerod tool.
Active app scope
| App | What it explains | Primary limit |
|---|---|---|
| IP Lookup | Public IP, IPv4/IPv6 lookup, ASN, network owner, approximate location, timezone, and map context when available. | IP geolocation is approximate and may identify a route or provider rather than a physical device. |
| WebRTC Leak Test | Browser ICE candidates, public-looking candidates, private/local candidates, hostnames, and mDNS-obfuscated values. | One run does not prove every future session will behave the same way. |
| Browser Leak Test | Browser identity, locale, storage, permissions, privacy controls, and practical exposure guidance. | Visible signals are not automatically harmful; interpretation depends on context. |
| Browser Fingerprint Check | Rendering, WebGL, audio, fonts, client hints, screen geometry, storage, permissions, and consistency signals. | A local fingerprint-surface estimate is not proof of identity across the web. |
| Proxy/VPN Detection | Route context and mismatch cues between the expected connection, browser context, WebRTC, DNS, timezone, language, and account state. | It surfaces consistency clues rather than definitively classifying every VPN or proxy. |
| Online Webcam Test | Camera preview, camera selection, microphone input, device selection, local picture capture, and local audio recording. | It confirms browser access and device behavior; it does not diagnose hardware beyond what the browser exposes. |
Camera and microphone handling
The Online Webcam Test requests camera or microphone access only after the user starts the relevant check. Live media remains in the browser. A captured picture or audio sample is downloaded only after the user chooses that action. Browser permission settings remain the user’s control, and closing the page or stopping a test should release active media tracks.
DNS Leak Test status
A reliable DNS leak test needs controlled external infrastructure that can associate a generated request with the resolver that handled it. Aerod should not publish the DNS route as a live test until that infrastructure is working and documented.
Claims Aerod apps should avoid
Aerod apps should not claim to prove that a person is anonymous, untracked, secure everywhere, or safe from all fingerprinting. The tools inspect a current browser, route, permission, or device context. Another site, profile, account, network, browser version, or data provider can return a different result.
Update process
When app behavior changes materially, update the matching app metadata, sitemap, data-handling language, methodology, and changelog. App runtimes should not be edited as part of a site-design pass unless that change is separately approved.