Toolvore
🔐

Security Toolkit

Hash, inspect, encode, and generate secrets — privately, in your browser.

Security work involves a lot of small, sensitive operations: fingerprinting a value with a hash, checking a file's integrity, inspecting a token, generating a strong secret. Doing any of these on a site that uploads your input is a risk in itself. This workspace keeps every operation on your machine.

From verifying a download's checksum to auditing what a JWT actually carries, these are the privacy-critical utilities you don't want running on someone else's server.

The workflow

  1. 1

    Fingerprint or verify

    Generate a SHA-256 hash of text, or hash a file to verify its integrity against a published checksum.

  2. 2

    Sign with a key

    Produce an HMAC to sign or verify messages with a shared secret.

  3. 3

    Audit a token

    Decode a JWT to see exactly which claims, scopes, and expiry it carries — no secrets should be in the payload.

  4. 4

    Generate strong secrets

    Create cryptographically random passwords and keys with the secure browser generator.

Tools in this workspace (8)

Frequently asked questions

Are these security tools safe to use with sensitive data?

Yes — every tool runs locally in your browser. Your inputs, files, and secrets are never uploaded.

What is the difference between hashing and encryption?

Hashing is a one-way fingerprint you can't reverse; encryption is reversible with a key. Use hashing for integrity and comparison, encryption for confidentiality.

Can I hash a file without uploading it?

Yes — the file hash tool reads the file locally in your browser and never uploads it.

Related workflows

Last updated August 2026