One-time delivery with a passphrase and Google Authenticator SEALED DELIVERY

Encrypt a message for someone you trust.

01 / Encrypt and send

Recipient public key · Base58

I checked the public-key fingerprint through another trusted channel Message · Up to 64 KiB Valid for · Hours, up to 7 days

02 / Keep revocation credentials separate

Check delivery status

Delivery ID · You can paste a saved ID

Checking an ID does not claim a key share. Final status records remain available for 24 hours. Save the ID yourself; this page keeps no history.

Do not send the revocation token with the encrypted message. It can destroy the delivery but cannot read the message.

Delivery ID Revocation token

The recipient must set up Google Authenticator first.
The server holds one random key share. It does not store the message or the complete encrypted package.
A claim is consumed when submitted. A network interruption or decryption failure does not restore it.
Sensitive content is not saved automatically. Minimal audit records of identities, deliveries and operation outcomes are retained for 90 days.
This does not guarantee a trace-free system. Malicious extensions, the clipboard and database backups remain outside this protection.

About this tool

One-time text delivery with recipient keys and TOTP

What does this tool do?

Verify a recipient's public-key fingerprint, encrypt text locally and share a ciphertext package or link. The recipient uses a passphrase and TOTP to claim a one-time key share, then decrypts locally. Query delivery status or revoke unclaimed delivery.

How to use it

The recipient enrolls an authenticator; the sender verifies the public-key fingerprint through a trusted channel.
Enter text and a validity period, then share the locally encrypted package or link. Keep revocation credentials separate.
The recipient claims a one-time share with their passphrase and TOTP and decrypts. A failed committed claim does not restore authorization.

Data handling and limits

Text up to 64 KiB; authorization up to seven days. The recipient must enroll an authenticator first. A committed claim is consumed even if the network or decryption fails. The server retains necessary identity, references, a random key share and audit records, not the message or complete ciphertext package. Not system-level trace removal. Revocation cannot recall previously claimed material.

Related tools