Find the Right Tool by Task

Sixteen tools, one index.

Know the job but not the tool name? Search by what you need to do and jump straight to the right page.

Loading the toolbox.

About Quick index

How Can You Verify That Nothing Leaves This Browser?

You do not have to take our word that your data stays here. Developer tools show every request a page makes, so you can watch this page work and confirm that nothing is sent. The check takes under a minute.

Open your browser developer tools with F12, or Cmd+Option+I on a Mac, and select the Network tab.
Reload the page and let it finish. You will see the page's own files, its web fonts, and one anonymous page-view request. Nothing has been typed yet, so none of them can contain your data.
Click the clear icon in the Network tab so that the log is empty.
Use the tool with your own input.
Look at the Network tab again. It is still empty. For extra proof, turn on offline mode after the page loads and the tool keeps working.

Only two things can add a line to that log, and neither carries your data. Submitting the feedback form sends the vote and comment you typed. Typing characters in a script the page has not displayed yet, such as Cyrillic or Greek, can make the browser fetch the matching font file, and that request names only the font.

The production site also sends a Content-Security-Policy header that tells your browser to refuse connections to anywhere except this site and the anonymous analytics endpoint, so a coding mistake could not quietly send your data elsewhere.

How Is 2toolbox Organized?

Sixteen tools sit in four lanes. Generators make something you paste into a project: IDs, a .gitignore, a Content-Security-Policy, an .htaccess, or a robots.txt. Encode / Crypto computes values: hashes and HMACs, number bases, and TOTP codes.

Checkers read what you paste and report problems: XML, JSON with a jq subset, SSH configs, .env files, and keyboard events. References are searchable tables of HTTP status codes and MIME types, plus this index.

Which Tool Do You Need for Security Work?

Protecting a site against XSS and clickjacking: 2csp.
Forcing HTTPS, adding security headers, and blocking .env and log files on Apache: 2htaccess.
Hardening an SSH server and choosing a key type: 2ssh.
Verifying a download or a webhook signature: 2hash.
Testing a 2FA integration: 2otp.

Which Tool Do You Need When Setting Up a Project?

A new repository: 2gitignore.
Environment variables shared with a team: 2dotenv.
Primary keys and request IDs: 2uuid.
Search engine rules for a new site: 2robots.

Two sister apps cover larger jobs: 2json for in-depth JSON work and 2regex for regular expressions.

Is Every Tool Private?

Yes. Every tool runs on its page, in your browser, and makes no request while you use it. The only automatic request is an anonymous page-view count when a page loads. The verification steps on this page show how to confirm it in your browser's Network tab.

What Other Tools Are in the References Lane?

HTTP status: Every IANA-registered HTTP status code, searchable, with plain-English meanings.
MIME types: About 150 common file extensions and their MIME types, searchable both ways.

Elsewhere in the toolbox: 2uuid, 2gitignore, 2csp, 2htaccess, and more on the 2toolbox home page. Part of the 2suite.io privacy-first ecosystem.

Frequently Asked Questions

Are all the tools free?

Yes. No account, no limits, and no paid tier.

Can I suggest a tool?

Yes. Use the thumbs buttons at the bottom of any page to send feedback. Please do not paste any secrets into the comment.

Why are 2json and 2regex separate sites?

They are larger workbenches in the same 2suite family. The toolbox links to them rather than duplicating them.

Do the tools work offline?

Yes, after the page has loaded, because nothing depends on a server.

Was this helpful?