Server-side fetch
Pages are requested from the target server by the proxy, never directly by your browser. Your IP and fingerprint stay invisible to the destination.
Encrypted · No logs · Instant
Browse any website, privately and instantly.
Paste a URL below — Webloop fetches the page through a secure relay and renders it right here. No browser extension, no install, no trace.
Tip: try example.com,
news.ycombinator.com, or any https URL.
webloop.app/proxy
Your proxied page will appear here.
Features
A proxy that takes privacy seriously.
Four layers of protection between you and the page you want to read.
HTML sanitization
Scripts, inline event handlers and javascript: URIs are stripped before the response ever touches your browser. Rendering is read-only.
Same-origin relay
You browse from webloop.app, the target sees the proxy's IP. Cookies and storage are sandboxed away from your real session.
SSRF guard
Private IP ranges, loopback addresses and metadata endpoints are blocked at the validator, so internal services stay internal.
How it works
From URL to rendered page in four steps.
- 01
Validate
The URL is parsed, scheme-checked and run against a private-IP blocklist before any request leaves the proxy.
- 02
Fetch
The proxy server requests the page from the origin, forwarding only the headers needed for a normal GET.
- 03
Sanitize
Scripts, inline event handlers and meta-refresh tags are removed from the response body.
- 04
Render
The cleaned HTML is served back to your browser at the same origin so links and assets stay relative.
At a glance
What the proxy guarantees.
- 4 layers
- of request sanitization
- 0 logs
- stored between requests
- <800ms
- median fetch + render
- 100%
- HTML scrubbed before render
Fair-use reminder. Webloop is meant for reading public pages, not bypassing paywalls, breaking terms of service, or scraping at scale.