Trace is a teaching and visibility surface, not a request proxy. It shows the conceptual path from public edge to logs and lets a browser check whether a specific HTTPS endpoint is visible to that browser.

The public page is trace.yshubham.com. Its Worker keeps the API intentionally small: GET /health reports service health and GET /api/trace emits a fresh synthetic trace ID with the four-stage walkthrough.

The probe runs in the browser. It accepts an explicitly supplied HTTPS URL and makes only a GET or HEAD request from the visitor's browser. The page enforces a maximum URL length and a bounded client-side timeout.

There are no custom headers, request body, URL credentials, or server-side outbound fetch. This means the tool cannot be used as an internal-network scanner or a generic request relay.

A Trace result is a browser-visibility check, not an availability SLO. It can tell you whether the chosen endpoint responded to the browser under the selected method and CORS policy. It does not prove that a private origin, upstream dependency, authentication flow, or production transaction is healthy.

For the staged visual walkthrough, use the built-in run a trace interaction. For public service reachability, check Status. For a controlled application exposure, use a Sandbox tunnel.