↗ WAYPOINT SCAN

Waypoint Scan BETA

This private beta explains the network activity of one allowed HTTPS page reload. Capture, sanitization and temporary reports stay in Chrome. The hosted application serves the viewer and authentication, not a capture backend.

Access

The intended Chrome Web Store distribution is Private, with the owner as the sole trusted tester. No Store publication is announced by this page. Application Google sign-in remains owner-restricted. Chrome review access is a separate revocable identity, using the same product path.

Owner sign-in · Restricted reviewer access

Capture steps

  1. Sign in to the viewer using the approved identity.
  2. Select an ordinary allowed HTTPS page.
  3. Open the extension popup, read its disclosure and click Analyze this page.
  4. The selected page reloads once; Chrome displays a debugger indicator.
  5. After capture detaches, the protected report opens. If signed out, complete sign-in in that same tab within ten minutes.
  6. Inspect Summary, Visit, request details and evidence. Use Clear local report when finished.

Allowed HTTPS target policy

Ordinary HTTPS targets and public-to-public HTTPS redirects are allowed. Local/private/special IPs, internal names, unsafe schemes, the private Waypoint Scan viewer/control surfaces and application Vercel aliases are refused where identifiable. Normal public CDNs, APIs, analytics, advertisements, fonts and media are not rejected merely because they are third-party.

This is an allowed-target and evidence-safety policy, not a browser firewall or malware blocker. A hostname does not prove the destination is public. If an identifiable prohibited navigation becomes observable, Waypoint Scan immediately fences collection, stops capture, detaches the debugger, discards the interrupted report, revokes its handoff and clears temporary evidence. Where supported, it also fails paused document requests and asks Chrome to stop the pending navigation before detaching.

These interception measures are defense-in-depth. Waypoint Scan does not guarantee that zero packets or requests reach every prohibited destination: DNS resolution, browser behavior, caches, proxies and observation timing can prevent that guarantee. Authentication, TLS validation, enterprise restrictions, CAPTCHAs and site protections are never bypassed by the extension.