security
Common questions and answers about Encryption / Decryption Crypto Lab.
No. Detection, decoding, hashing, and encryption run locally in your browser with the Web Crypto API and audited client libraries. Nothing leaves your device.
Base64, Base64URL, Hex, Binary, URL encoding, HTML entities, Unicode escapes, JWT, PEM certificates, Morse, Gzip-in-Base64, ToolVerse TV1 AES payloads, and common hash lengths — each with a confidence score.
AES-GCM/CBC/CTR (Web Crypto), ChaCha20-Poly1305, XChaCha20-Poly1305, XOR (demo), plus password hashing with Argon2id, bcrypt, PBKDF2, and scrypt. RSA-OAEP, Ed25519, and X25519 for asymmetric operations.
No. Cryptographic hashes are one-way. The lab can generate and verify digests (MD5, SHA family, SHA-3, BLAKE2/3, and more) but cannot decode them back to plaintext.
TV1: is ToolVerse’s AES-256-GCM format: PBKDF2 (250,000 iterations, SHA-256) derives the key; salt and IV are packed with the ciphertext and Base64-encoded after the TV1: prefix.