DevTools Logo

Self-Destructing Encrypted Note

Self-Destructing Encrypted Note

One-time AES-256 encrypted links — ciphertext and key ride in the URL fragment, never on a server

Write a secret note

Burn link

Write a message and generate a one-time encrypted link.

How burning works

The encryption key lives in the #fragment of the link, which browsers never send to any server. After you read the note once, the key is erased from the address bar and this browser. However, anyone who copied the full link can read the note too — share it like a secret, not a billboard.

Examples

Wi-Fi handoff

Input
Note: the guest Wi-Fi password · no password
Output
Link …?n=…#k=… — readable exactly once

After the read, the address bar no longer contains the key.

About this tool

One-time encrypted messages with a visible mechanism: the ciphertext rides in the query string, the key rides in the URL fragment (#k=…) — and browsers never send fragments to servers. Opening the link wipes the fragment from the address bar, reveals the note on demand, and blocks re-decryption in that browser.

An optional password entangles its derived key material into the fragment key, so a leaked link alone is mathematically useless. The burn is honestly scoped: anyone who copied the full link holds the key too — the tool says so instead of pretending.

How to use

  1. Write the message

    Type the one-time secret; add a password for two-factor delivery.

  2. Generate the link

    Encryption is local; the key goes only into the link's fragment.

  3. Share securely

    Send the full link over a trusted channel — fragment and password together open it.

  4. Read once

    The recipient reveals the note; the fragment is gone and re-reading is blocked.

Use cases

One-time credentials

Codes and passwords that shouldn't live in chat scrollback forever.

Time-limited instructions

Instructions that self-destruct after the first read.

Common mistakes

Mistake:Treating burn as DRM

Fix:Anyone who copied the full link before opening can read it too; the burn protects against casual re-reading, not everything.

Mistake:Sending the link and password in the same message

Fix:Split channels: link by chat, password by voice.

Frequently asked questions

References & standards