Skip to main content
WizTools123
Free Online Tools

Tool Categories


Security Tools 11 Tools Available

Free Online Hash, Encryption, Certificate, JWT & Password Hash Tools

Do the exact small jobs security work is made of, without the input ever leaving the tab. Hash text or a file and compare it, work out an HMAC, identify a hash you were handed, hash a password with PBKDF2 or bcrypt, encrypt with AES, generate an RSA key pair, read a certificate or a CSR, sign and verify a JWT, and escape text so it cannot break out.

Nothing Uploaded, Ever No Keys Stored The Browser Own Crypto Limits Stated Plainly Works on a Phone
Free Online Hash, Encryption, Certificate, JWT & Password Hash Tools
Share this tool
Advertisement Slot (Top Banner) Google AdSense Unit • Responsive Banner

Choose a Security Tool

Pick the job you need done, and each tool opens on its own page.

Buy Us A Coffee

Enjoying WizTools123? Help keep our server infrastructure 100% free and open for everyone.

Buy Us A Coffee
Sponsored Content (Below Tool) Google AdSense Placement

About Security Tools

Security work involves a long tail of small, exact jobs. Hash this file and compare it with the one the vendor published. Read the certificate somebody emailed and find out when it expires. Sign a token so a test will accept it. Turn a passphrase into a key and encrypt one file. None of these is difficult, and all of them are the kind of thing people reach for a web tool to do, which is where the problem starts: the input is usually the secret, and most web tools send it to a server.

Everything in this category runs in the page. Where the browser provides the algorithm, the browser does the work: AES, RSA, HMAC, the SHA-2 family and PBKDF2 all come from Web Crypto, which is the same implementation the browser uses for HTTPS and has been examined far more carefully than anything written for a tools site could be. Where the browser does not provide something, it is written here and said so, which is true of MD5, of bcrypt, and of the DER parser behind the certificate decoder.

The hardest part of building these was deciding what not to do. There is no Argon2, because the only way to run it in a browser is a WebAssembly bundle that takes a second or two on a phone and would still be the wrong answer, since a password hash should be computed where the password arrives and not in a browser tab. Nothing saves your input, so none of these pages has the saved setups and history that the rest of the site has. And no page claims to validate trust: a certificate decoder can tell you what a certificate says, and only a browser with a root store can tell you whether to believe it.

What every page does carry is the parameters and the caveats. The iteration count, the key size, the cipher mode, the salt, the cost factor: all visible, all editable, and all explained where the choice actually matters. That is the part a tool can genuinely help with, because the arithmetic was never the hard bit. Knowing that the same password with the same salt and a hundred times fewer iterations produces an answer that looks exactly as convincing and is worth far less, that is the bit worth putting on the screen.

Frequently Asked Questions

Common questions about these tools.

No. Every tool in this category works entirely in your browser: open the Network tab and the page loads its own code and then makes no further requests. You can switch the network off after the page has loaded and everything still works, which is the easiest way to prove it to yourself.

The code never sends them anywhere, so the risk is not this site. It is the machine and the browser you are sitting at: an extension, a shared computer or a screen recorder sees what is on the page whatever the page does. For a production private key, generating it on the server that will use it is still the right habit.

Because real systems still use it, and a checksum from a download page is often an MD5. Broken means two different inputs can be made to produce the same hash, which ruins it for signatures and for passwords. It is still useful for spotting accidental corruption, and every page that offers it says exactly that.

Deliberately. The rest of this site saves setups and history in your browser so you can come back to them, and in this category that would mean a passphrase or a private key sitting in browser storage waiting to be found. There is no storage here to clear, which is why closing the tab is the whole of the cleanup.

No, and that is a decision rather than an omission. Argon2 in a browser needs a WebAssembly bundle that is slow on a phone, and a password hash should be computed where the password arrives, which is your server. The password hash page offers PBKDF2 and bcrypt and explains where Argon2 belongs instead.

They can tell you what it says: who it was issued to, by whom, when it expires, which names it covers and what its fingerprint is. Whether to trust it is a different question that needs a root store and a revocation check, and no page here pretends to answer it.

Yes, once the page has loaded. The algorithms come from your browser and from the page itself, so there is nothing to fetch. The only tools that would need a network are the ones that would have to reach another site, and there are none of those in this category.

Every Other Category

21 more sets of tools on the site. All free, all in your browser.

Advertisement Slot (Bottom Banner) Google AdSense Unit • Responsive Banner