Security Tools

ArrayKit's Security tools cover the everyday cryptographic and authentication chores developers hit while building and debugging apps. Inspect a token's claims and expiry with the JWT Decoder, or mint one using the JWT Signer with HS256/384/512. Compute SHA-256, SHA-1, SHA-384, and SHA-512 digests with the Hash Generator to verify checksums and file integrity. Create strong credentials with the Password Generator and time-based codes with the TOTP / 2FA Generator. For key management, the SSH Key Generator produces Ed25519, RSA, and ECDSA keypairs, the PPK to PEM Converter moves keys between PuTTY and OpenSSH, and the Basic Auth Generator builds and decodes HTTP Authorization headers. Every operation runs on your device using standard browser cryptography, so secrets, tokens, keys, and passwords are processed locally and nothing is uploaded.

Frequently asked questions

What can ArrayKit's Security tools do?
They cover the common crypto and auth tasks in one place: decode and sign JWTs, generate SHA hashes, create strong passwords, produce TOTP 2FA codes, generate SSH keypairs, convert keys between PuTTY .ppk and OpenSSH/PEM, and build or decode HTTP Basic Auth headers.
Is my data private when I use these Security tools?
Yes. Every tool runs on your device using standard browser cryptography, so tokens, hashes, passwords, SSH keys, and credentials are processed locally. Your data never leaves your device and ArrayKit does no tracking of what you enter.
Do the Security tools work offline?
Once the page has loaded, the tools run client-side, so hashing, signing, key generation, password creation, and JWT decoding keep working without a live connection. Loading the page for the first time still needs the internet.
Which SSH key formats are supported?
The SSH Key Generator creates Ed25519, RSA 2048/4096, and ECDSA P-256/384/521 keypairs with OpenSSH public keys and PEM private keys. The PPK to PEM Converter turns PuTTY .ppk keys into OpenSSH/PKCS#8 PEM and back, for RSA and Ed25519 keys.
Can I both create and inspect JWTs here?
Yes. Use the JWT Signer to build and sign a token from a payload and secret with HS256, HS384, or HS512, then paste the result into the JWT Decoder to read the header, payload, and exp/iat/nbf claims. The decoder does not verify signatures.
Are the passwords and 2FA codes generated securely?
The Password Generator draws from a cryptographically secure random source and shows a strength meter, while the TOTP / 2FA Generator produces standard time-based codes from a base32 secret. Both run locally in your browser.