ip-diagnosis

Network diagnostics for IPv4 and IPv6 exposure involve assessing local routing, DNS behavior, and public IP visibility from macOS and Chrome. This process verifies reachability, VPN or proxy impact, and browser exposure including WebRTC considerations to generate a detailed ops report.

WebRTC exposure in Chrome can reveal your local IP address. Diagnosing this requires a browser validation workflow that checks WebRTC considerations and Server Response, identifying whether your real IPv4 or IPv6 address is visible despite active VPN or proxy configurations on macOS.

Diagnosing DNS behavior and default route issues on macOS involves performing local network checks that assess native interfaces, utun status, and DNS resolution. Cross-referencing this data with multi-source public IP checks provides a comprehensive view of network exposure.

Verifying IPv6 reachability and ASN organization from a browser involves running a network diagnosis that checks public IP visibility across multiple external services. This captures geolocation and ASN data, confirming whether your IPv6 connection is active and properly routed.

If your utun status is active but your public IP is not masked, your VPN or proxy routing may be misconfigured. A network diagnosis evaluates local default routes and cross-references DNS data to identify why your IPv4 or IPv6 traffic is bypassing the tunnel.

Generating a network diagnostics report with verification links requires running a full IP exposure diagnosis on macOS and Chrome. This produces a structured ops report documenting local routing, DNS behavior, public IP visibility, and WebRTC exposure, complete with review links for maintenance.