Encoding & Crypto
Encode and decode Base64, URL components and HTML entities. Hash with SHA-256 or bcrypt, sign a message with HMAC, encrypt text with AES and a passphrase, generate an SSH key pair, read the codes an authenticator produces, and make passwords and UUIDs.
These are the tools people most often paste a real secret into — a live token, a signing key, a password — which is exactly why every one of them runs in the page. The browser does the work with its own cryptographic implementation, and nothing is transmitted. Load a tool, disconnect from the network, and it keeps working.
Certificates are the one thing here you read rather than make. A PEM certificate holds its subject and issuer, every hostname it covers, the key size, the fingerprints and — the field that matters most often — the expiry, with the number of days left.
What a certificate starts from can be made here, though: a signing request for a certificate authority, with an RSA or ECDSA key made in the page or one you already have, every hostname as an alternative name, and the signature checked before it is copied.
Recovery phrases are here too: a BIP39 phrase of 12 to 24 words made from the browser’s cryptographic randomness, a phrase checked word by word and against its checksum, and the seed a wallet derives from it.