Borrow abrowser forten minutes.
Paste anything you would rather not open yourself. It loads inside a throwaway container and reaches you as pixels.
You paste a link.
Nothing has loaded yet. The URL is a string on your machine and nothing more.
nothing has executedA container wakes up.
Real Chrome, its own filesystem, its own network namespace, attached to an internal bridge with no published ports.
network: secure-browser-netThe page opens in there.
Scripts, trackers and downloads all run — inside the container. You are watching pixels over a WebSocket.
6080 → websockify → your tabTen minutes, then nothing.
Long enough to read a page, sign in, or pull down a file. Short enough that whatever you opened never gets a place to settle.
The container is stopped. Cookies, cache, downloads and history went with it — there was nowhere for them to persist to.
The stop button ends the session the moment you are done. You never have to wait the clock out.
At zero the backend stops the container on its own and marks the session ended. Forgetting is the safe path.
No volume is mounted from your machine, and the container is removed on stop — its writable layer goes with it.
Nothing is running.
Paste a link you don't trust.
That is the whole workflow. Close the tab whenever you like; the container stops either way.
Open a session