Nothing leaves your browser: the Network test
What we check before every deployment, what that check does not cover, and how to run it yourself.
The claim, stated precisely
On the 31 tool pages of Praticulus, what you type, paste or upload is not sent anywhere. After the page has loaded, using a tool triggers no request, except for two kinds that carry nothing you entered: a library file the tool fetches from praticulus.com the first time you use it, and the tab icon your browser fetches again when a tool writes its state into the address bar.
We do not claim “zero requests”. Loading a page fetches its own HTML, CSS, JavaScript, fonts and icons, all from praticulus.com. Every load also appears in our web server’s access log (IP address, user-agent, URL), like on any website.
What the automated test does
Before every deployment of praticulus.com, our deploy script runs network-guard.mjs on the files about to go live. For each of the 31 tool pages, it:
- serves the page from a local server and opens it in headless Chromium, in a fresh browser context with no extension;
- fills every visible text field with a marker,
QZNETGUARDCANARY. A field that needs a valid format gets a valid value, with the marker inside wherever the format allows it: a JSON or YAML document, a JWT payload, the subject of a certificate. A color, cron expression or timestamp cannot carry it, so it gets a plain valid value; - gives every file input a file that contains the marker (a 1×1 PNG with the marker in a text chunk, or a text file);
- picks the last option of every dropdown, then clicks every visible button, checkbox and radio in the page body (up to 60), filling the fields again before each click;
- waits one more second for anything delayed by a timer, then reloads the page, to catch data kept in storage and sent on the next visit;
- on eleven tools, also checks that the marker appeared in the tool’s output, as proof that the tool actually ran rather than just showing an error.
Every request made by the page, its workers included, is recorded. Anything addressed to another host than the local server is intercepted and answered with an empty response: nothing leaves the test machine.
The four rules
- No request carries the marker, in its URL or its body, raw, URL-encoded or base64-encoded.
- No request goes to another origin than the site itself, at any moment, during load included.
- No request is triggered by using the tool, except fetching a file of the site that exists, of type script, stylesheet, font or image, with no query parameter other than a
?v=cache key, and the tab icon. Afetch, an XHR, a beacon, a WebSocket or a navigation after load is always a failure. - No request other than GET, at any moment.
If one page breaks one rule, the deployment of the site is cancelled and praticulus.com stays on its previous version. If the test cannot run at all (browser missing, page that does not load, tool that could not be exercised), the deployment goes ahead and we are alerted: a page that was not exercised is reported as unchecked, never as compliant.
Latest result
Run on November 4, 2026, in Chrome 156: 31 of 31 pages compliant, 0 violations, 0 unchecked. Each page made 10 to 19 requests while loading, all to the site itself. After interaction:
- 24 pages made no request at all;
- 5 pages (Diff Checker, Timestamp Converter, SQL Formatter, Hash Generator, HMAC Generator) made the browser fetch
/favicon.svgagain, after the tool wrote a share link or a setting into the URL. Both live in the URL fragment (after the#), which browsers do not send to the server; - 2 pages (SQL Formatter, YAML Formatter) fetched their formatting library from
/js/vendor/on first use.
The test has been part of every deployment since October 28, 2026.
What the test does not cover
- Only the 31 tool pages. The home page, its search box included, the category pages and pages like this one are not part of the test.
- Only Chromium. Firefox and Safari run the same code but are not tested automatically.
- The files, not the live server. The test runs on the files about to be uploaded, served locally. It says nothing about the HTTP headers praticulus.com sends, such as its Content-Security-Policy.
- One pass, not every combination. Each button is clicked and the last option of each dropdown is picked, but not every sequence of options a person could choose.
- What could be hidden in which file is fetched. The third rule lets a tool fetch an existing file of the site after load. The test does not judge which file is chosen, so data encoded in that choice would not be caught.
- Your browser extensions. The test runs without any. An extension can read and send what a page shows; no website can prevent that.
- The error reporter. Every page loads
error-reporter.js, which sends a beacon todash.irisdigital.tech, our own server, when the page hits a JavaScript error it did not handle. The beacon contains the error message, an excerpt of the stack trace, the hostname and the page path. In the test, it counts as a failure (another origin); it did not fire on any of the 31 pages. It is still there for real errors, on your machine. - Local storage. The two Markdown tools save your draft in your browser’s local storage so you do not lose it. The reload step checks that it is not sent; it stays on your device.
- That the test really ran. It runs on our deployment server, where you cannot watch it. That is why the method below exists.
Check it yourself, by hand
About two minutes per tool, in any browser with developer tools.
- 1. A clean window. Open a private window, where extensions are off by default, or a fresh browser profile.
- 2. Open the Network panel first. Go to a tool, for example the JSON Formatter. Open DevTools (F12, or Cmd+Opt+I on macOS), select the Network tab and tick Preserve log (Persist Logs in Firefox). Reload the page.
- 3. Read the load. Right-click a column header and show the Domain column. Every row should read
praticulus.com. - 4. Clear, then use the tool. Clear the list with the panel’s Clear button. Paste something you would recognize, such as a made-up token
MY-SECRET-1234, and use every button of the tool. - 5. Read what happened. The list should stay empty, or show only
favicon.svgor a.jsfile frompraticulus.com, fetched with GET. Click any row that appeared and read its URL and headers: your token is not there, and a GET has no body to carry it. - 6. Reload once more, with the log preserved, and check that the new requests do not contain your token either.
Rerun the automated test
The test script and its configuration are published with the site, in network-guard/ of the public repository. With Node.js 18 or later and Google Chrome installed:
On Windows, in PowerShell, set the variable first with $env:NETWORK_GUARD_CHANNEL="chrome"; msedge works too. The script prints one line per page, in French, and ends with 31/31 conformes, 0 en violation, 0 inexploitable(s) (31 of 31 compliant, 0 violations, 0 unchecked). It exits with 0 when every page complies, 1 on a violation, 2 when a page could not be checked. The rules are written at the top of the script, and they are the ones on this page.
Related
The privacy policy covers cookies, server logs and fonts. The full source of the site is at github.com/jamalofski/praticulus, under the MIT license. Found a request this page does not account for? Write to contact@praticulus.com.
Last updated: November 4, 2026