AES Encrypt / Decrypt
Encrypt text with modern AES-GCM or decrypt legacy CryptoJS-compatible AES payloads for non-sensitive compatibility checks.
- Use a small sample first, then process the full non-sensitive input.
- Review the output before copying it into documentation, code, or another system.
- Keep the original text nearby so changed formatting, encoding, units, or whitespace can be compared.
Use cases and limits
Encrypt text with modern AES-GCM or decrypt legacy CryptoJS-compatible AES payloads for non-sensitive compatibility checks. Use non-sensitive sample text first and keep production secrets out of browser utilities.
AES output format boundary
Modern AES-GCM output starts with ymir-aes-gcm-v1: and is not compatible with legacy CryptoJS/OpenSSL passphrase ciphertext. Legacy CryptoJS mode is kept only to inspect or decrypt old compatible payloads; it cannot decrypt the modern AES-GCM format.
- Use Modern AES-GCM for new non-sensitive test payloads.
- Use Legacy CryptoJS only when a historical system already produced that format.
- Do not paste production passwords, API keys, tokens, private keys, or customer data into either mode.
AES Encrypt / Decrypt 的具体使用判断
AES Encrypt / Decrypt 适合处理明确、短小、非敏感的 开发调试 任务。页面保留为独立入口，是为了让用户在知道具体任务名称时能直接打开，而不是在一个大型混合工具里反复切换。Encrypt text with modern AES-GCM or decrypt legacy CryptoJS-compatible AES payloads for non-sensitive compatibility checks. 这样的任务通常耗时不长，但错误复制到目标系统后会造成排查成本，因此需要在复制前完成最基本的上下文检查。
重点检查输入是否是目标格式本身，还是日志、HTML 错误页、控制台包装或代理层信息。工具结果应回到项目环境验证。 对于 aesencrypt 这类页面，建议使用公开样例学习操作，再处理自己的脱敏输入。输出结果如果会进入代码、配置、文档、表格、邮件、工单或客户交付材料，应把原始输入和工具输出并排保存，至少确认一次目标系统如何解释该结果。
不建议使用本页的情况
- 输入包含密码、密钥、token、客户资料、内部域名或完整生产日志。
- 任务需要权限、审计记录、团队审批、官方控制台或专用 SDK。
- 你需要的是安全证明、合规结论、工程设计结论或财务最终数值。