Link Detonator
An AI agent that investigates links you do not trust, inside a throwaway browser on Vultr. Hostile pages try to hijack the agent. The model only proposes; a rule engine decides, and the sandbox and firewall enforce. You get evidence of what the page tried, what was blocked and what was verified. Then the chamber is destroyed.
- DetonateThe link opens in a throwaway browser, in a container behind a firewall. It never clicks, types or submits.
- The AI judges, the rules decideThe model reads the evidence and proposes. A rule engine allows or denies every action. The model cannot grant itself anything.
- Evidence you can verifyEach claim in the report is tied to recorded events. Containment is shown only when the evidence proves it.
Start here
The Gauntlet
One test page that throws most of the hostile tricks we know at the chamber: a fake login, concealed instructions, a forced download, a run at private addresses, a small memory allocation and a frozen tab. Watch what each one does. Memory has its own test charge, because pressing the limit would crash the page before the freeze.
Or scan a QR code
Decode a QR image
Point your phone at a QR code, or upload an image. Large photos are shrunk on your device first. The image is decoded inside a throwaway container with no network, and nothing is opened until you choose to investigate.
Or check an email
Check a suspicious email
Save the email as a .eml file (in most mail apps: More, then Download or Save as) and drop it here. It is read inside a throwaway container with no network. Links and QR codes are listed, nothing is opened, and attachments are never opened or offered for download.
These checks are copied from the email's own headers. They are not verified here.
What stands out
These are facts about the email, not a verdict. A safe email can show some of them, and a harmful one can show none.
Links
QR codes
Attachments
Test charges
Fictional pages served only inside the sandbox. Nothing hostile is hosted anywhere public.
How a deployed chamber behaves
- Hands off The browser only looks. No clicks, no typing, no submits, no kept downloads.
- Walled in On the deployed host, a firewall stops the chamber reaching private networks, cloud metadata or the host itself.
- No secrets inside Nothing is passed into the container. Evidence leaves through one output stream, treated as hostile.
- Destroyed, then checked Every chamber is removed after its scan, and the host confirms it is gone.
None of the four applies in this dev run. The worker is a plain local process.