ZeroTrace Proxy
Viewer
Fetch a web page through a proxy to see exactly what a destination sees when you use it, with full control over the request you send.
Viewer
The Viewer fetches a page through a proxy and shows you the result, so you can confirm what a destination actually sees when your traffic goes through that proxy — the address it observes, the content it serves, and how it responds.
Building the request
The Viewer lets you shape the request rather than only fetching a plain page:
| Setting | What it does | Default |
|---|---|---|
| Method | GET, POST, HEAD, PUT, or DELETE. | GET |
| Headers | Any custom header list to present yourself the way a site expects. | none |
| Cookies | A list of cookie name/value pairs, joined into a single Cookie header. | none |
| Body | Raw text sent as-is for POST/PUT requests. | empty |
| Follow redirects | Follow the destination's redirect chain rather than stopping at the first response. | on (turn off to inspect just the first hop) |
| Max response size | Caps how much of the response body is fetched, in KB. | 512 KB (range 1–8192 KB) |
Reading the response
The response comes back for inspection:
- Status — code and status text.
- Requested vs. final URL — the URL you asked for and where you actually ended up after redirects.
- Detected protocol — what the proxy actually spoke.
- Content type, byte count, truncated flag — whether the response was cut off by the size cap.
- Body — the text content (empty for images), with the page's
<title>pulled out separately for HTML. - Content flags — whether the response is HTML, JSON, plain text, or an image.
- Inline image preview — images up to 4MB are rendered directly as a data-URL preview so you can see them without leaving the app.
- Exit IP and geo — the address and location the destination saw, when country resolution was requested for the run.
- Full response headers — every header the destination sent back.