About Toolexe

Who runs Toolexe

Toolexe is an independent website. Three developers run the whole operation: the code, the servers, the page copy, and the review of each tool. Their names sit on the pages they check, with links to their full profiles.

Ads from Journey by Mediavine pay for hosting. We sell no paid plan, no premium tier, and no user data. A tool you use today stays free tomorrow, with no trial counter.

Why Toolexe exists

Pretty-printing an API response or converting a Unix timestamp takes ten seconds. Many tool sites turn the job into a sign-up form, a file upload, and a wait. Toolexe keeps each tool to one job on one page.

The work happens in your browser wherever possible. A pasted config file, a customer list, or a JWT stays on your machine. Some jobs need a server, such as a DNS lookup or an SSL certificate check. Those pages say so, and the privacy policy names each one.

Who builds and maintains the tools

Every tool page carries a byline. A named reviewer owns the page, or the byline reads Maintained by Toolexe when no single person owns the page yet.

Job history, degrees, and the pages each reviewer signs live on the editors page.

How the background maps to the tools

• Browser tools: most of the catalog is JavaScript running on your device. Front-end review catches the parsing edge cases: trailing commas in JSON, Unicode in Base64, line endings in diff tools.
• Code quality tools: linters, complexity checks, and test helpers get reviewed by someone who teaches software and data courses.
• Network tools: DNS, IP, SSL, and header checkers sit with the reviewer whose degree and job history run through networks and production systems.
• The stack: Laravel and PHP render the pages, Cloudflare delivers them, and server-backed generators answer through our own API, capped at 60 requests a minute per visitor.

How tools get tested and reviewed

1. One tool, one script. Each tool ships with its own JavaScript and stylesheet. A fix to the CSV converter never touches the JSON formatter.
2. Automated tests for server-backed generators. Each one has a test file checking a filtered result, an unfiltered result, rejection of bad input, and the page rendering its first sample.
3. Hand review for browser tools. Before a rewritten page ships, the reviewer runs the sample input plus edge cases: empty input, malformed data, and long text.
4. Empty inputs, honest samples. Input boxes load blank. A Load sample button fills them with realistic, varied data instead of stock placeholder names.
5. A visible owner and date. The byline names the reviewer. The Last updated date comes from the page file itself, so the date moves only when the page changes.

Report a wrong result or a broken tool

Email info@toolexe.com. A reviewer reads every report. Include four things:

• The page URL, for example https://toolexe.com/json/beautifier
• The input, trimmed to the smallest piece showing the bug
• The result you expected, and the result you got
• Your browser and device

Leave out passwords, API keys, and personal records. Swap them for dummy values first.

We reproduce the bug with your input, fix the tool, and the Last updated date on the page moves when the fix goes live. When the cause is a browser limit rather than our code, such as a file too large for memory, we add the limit to the page so the next person knows before pasting.

What happens to your data

• Browser tools: text you paste and files you open get processed on your device. Our server has no file upload handler for any tool.
• Server-backed tools: lookups, SSL checks, generators, the MD6 hash generator, and the performance profiler send your input to our server to build the result. None of the input goes into a database.
• Visit log: each page load records your IP address, the page address, and device details, for traffic and speed reports.
• Analytics and ads: Google Analytics and Journey by Mediavine set cookies on tool pages.
• Saved work: notes, history, and settings stay in your browser's local storage, never on our server.
• No sale: we take no money for your tool input, your email address, or the visit log.

The privacy policy lists every network request, cookie, and retention period, plus how to ask for your data or its deletion. The terms of service cover the rules for using the tools.