Tool pages
Each Tamperbox tool page opens on a live result or controlled example, shows its verdict and evidence, and links here for the method behind every finding.
Browse the same groups as the tool directory. Each card starts with a reason to use the tool, followed by what its documentation covers.
A tool page on tamperbox.dev has one job: take one input, show the verdict, and show the evidence behind it. The page keeps a short “How it works”, the limits that change how you read a result, three questions people ask, and the standards it follows. Everything longer lives here.
Each tool’s documentation has the same shape, so a finding on the page always has a place to point to:
| Section | What it holds | Where the page links to it |
|---|---|---|
| Method | Every rule the tool applies, in the order it applies them, with the exact wording of each finding | “Read the method” on the What does it mean and Tool limitations cards |
| Finding reference | One row per finding: severity, what it means for whoever receives the output, the fix | The finding itself |
| Guide | Step by step, for each situation the tool can put you in, including how to verify the fix | “Step by step on docs” on the How to fix it card |
| Worked example | The live default or an explicitly loaded controlled sample, read end to end, and what each Break it case shows | “Worked examples on docs” |
| For agents | How to run the same check through the MCP server and what the result does not prove | The For agents band on the page |
APIs & HTTP
Section titled “APIs & HTTP”Web security & TLS
Section titled “Web security & TLS”Email & DNS
Section titled “Email & DNS”Domains, registration & hosting
Section titled “Domains, registration & hosting”Network & IP
Section titled “Network & IP”Data formats
Section titled “Data formats”Web & URLs
Section titled “Web & URLs”Text & test data
Section titled “Text & test data”Localization
Section titled “Localization”UI testing
Section titled “UI testing”Where processing happens
Section titled “Where processing happens”Every tool page says, next to its verdict, where your input goes. The rule is the same across tools:
- Pasted evidence is parsed locally when the tool supports that mode. A pasted domain still starts a live lookup. Website Hosting Checker also looks up network information for pasted public IP addresses. Read the tool’s processing notice before running it.
- A host name or domain means a named server-side check. The server makes the required connection, DNS queries or published-file fetches, returns what it saw, and keeps nothing. The page names the port and the records or files it checks before it runs them.
Ordinary rail links carry no input. Explicit result actions temporarily use browser session storage and a random transfer token in the URL fragment. The transferred input itself is not placed in the URL. See each guide for its input handling and network requests.
Break it, Heal it, History
Section titled “Break it, Heal it, History”Tool pages offer Break it examples and applicable Heal it repairs. Pages with History also expose Revert and Reset input:
- Break it loads a deliberate edge case built from your own input where that is possible, so you see what the finding looks like before it happens to you.
- Heal it offers the repairs the tool found, each saying what it will change. After a break with no repair, it offers to restore the input you had before.
- History, under the result, logs every change with what it replaced. Revert undoes the newest change; Reset input returns to what you entered.