站点介绍

Sending a database password to a teammate over chat in plaintext felt wrong, and Base64 is a sticky note anyone can peel. The habit that stuck: encrypt with AES, send the ciphertext in chat, and speak the passphrase over the phone - a different channel. This page does exactly that job - set a passphrase, seal the text, all inside the browser, past no server at all.
The warning bar at the top is not legal boilerplate - it is the math. The key derives from your passphrase, and your passphrase lives in your head. There is nothing on the server that could help you recover it, because this page uploads nothing anywhere. A lost passphrase is a lost key; do not gamble on brute force, AES-256 does not lose to patience. Memorize the passphrase before you press Lock.
Every run generates a fresh random salt (16 bytes) and IV (12 bytes), both packed into the ciphertext. That is not instability - it is standard practice in serious cryptographic designs: if identical plaintext always produced identical ciphertext, an attacker could compare ciphertexts and infer "these two secrets are the same" - two tickets sharing a password, say, would share a ciphertext too. Randomization cuts that inference chain.
No, and there is no workaround. The key is derived from your passphrase with PBKDF2; this page stores neither the passphrase nor the key anywhere (it uploads nothing at all), so a forgotten passphrase is a lost key. Do not burn an afternoon guessing - brute-forcing AES-256 is not engineering-feasible. Store the passphrase somewhere solid before you encrypt.
Base64 is an encoding, not encryption: anyone can paste it into a decoder and read the original - a letter in a transparent envelope. This is real encryption: AES-256-GCM is the symmetric cipher used in banking protocols, and without the passphrase not a single bit of plaintext can be derived. Use Base64 to fool the eye; use this for actual confidentiality.
By design, not by accident. Every encryption run generates a fresh random salt and a fresh random initialization vector, both packed into the ciphertext - so encrypting "hello" twice yields two completely different Base64 strings. The upside: an attacker cannot compare ciphertexts to learn whether two plaintexts match. That is standard practice in serious cryptographic designs.
Two possibilities: the passphrase is wrong (case, trailing spaces, wrong keyboard layout all count), or the ciphertext was truncated or altered during copy-paste. GCM carries a built-in authenticity check and refuses to decrypt if a single bit is off - it would rather fail than hand you wrong plaintext. Check the passphrase first, then verify the ciphertext is complete (starts with v1:, nothing missing at the end).
No. Encryption and decryption run in this device's browser via WebCrypto - no upload endpoint, works offline. The page stores no passphrase, key or ciphertext: refresh it and every input box is empty, nothing kept anywhere.
中文版:https://www.9314.cn/tools/text-encrypt/
评论列表 (0条)