Loading...
Loading...
Transfer cryptocurrency wallet keys, SSL certificates, or any private keys with encryption.
A private key in the wallet, TLS, or code-signing sense is bearer authority over money, identity, or distribution. A 12- or 24-word BIP-39 seed reconstructs every Bitcoin and Ethereum account under BIP-32/BIP-44; whoever types those words into Sparrow or MetaMask owns the coins, no chargeback. A leaked TLS server key paired with your Let's Encrypt certificate lets an on-path attacker impersonate your domain until OCSP propagates. A leaked Authenticode or `DeveloperIDApplication` key lets attackers ship malware that customer machines trust.
Default channels punish you in unusual ways. Photos of a Ledger or Trezor recovery card uploaded to iCloud run through OCR and become indexed text. A `.p12` PFX bundle in Slack sits in the workspace export forever. A seed dictated over Zoom is captured by Otter.ai into a transcript. Apple Notes syncs through CloudKit unless explicitly locked.
PasteOnce fits narrow handoffs that genuinely need a key in transit: provisioning a hardware wallet from a custodian's offline keygen, restoring a TLS key onto an edge node before ACME is wired, or escrowing a signing key into HashiCorp Vault's Transit Engine. Pair with hardware-backed storage (Ledger, Trezor, YubiHSM 2, AWS CloudHSM) and rotate on import.
Client-side encrypted. We can't see your data.
Your data is encrypted in your browser before it leaves your device.
Messages are automatically deleted after being read once.
We never see your data. Only encrypted blobs pass through our servers.
Links work exactly once. Refresh the page and it's gone forever.
Your sensitive data is encrypted in your browser using AES-256-GCM. The encryption key is generated randomly and never sent to our servers.
Only the encrypted blob is stored in our database, with an automatic expiration time. We literally cannot read your data.
When your recipient opens the link, the encrypted data is fetched and immediately deleted from our servers using an atomic Redis GETDEL. The key in the URL hash decrypts the message in their browser.
For high-value wallets, run Ian Coleman's BIP-39 tool on an offline laptop, or use a Coldcard Mk4 or SeedSigner. The 24-word phrase ideally never touches a connected machine; when transit is unavoidable, send via PasteOnce.
Re-encrypt with `openssl pkcs8 -topk8 -v2 aes-256-cbc -in server.key -out server.enc.key` before pasting. The passphrase travels on a different channel — voice call, signed Signal — so leaking either half alone is non-fatal.
Move signing material into AWS CloudHSM, YubiHSM 2, Azure Key Vault Premium (FIPS 140-2 Level 3), or HashiCorp Vault Transit. The key never leaves the boundary; engineers submit artifacts to a sign endpoint and receive the signature with audit logs.
Trezor's SLIP-0039 and `ssss-split` divide a seed into N shares with a K threshold. Distribute shares geographically; no single courier holds enough to reconstruct. PasteOnce one share at a time over distinct channels rather than the full seed.
Your hardware wallet bricks mid-firmware-update; the recovery card sits in a deposit box across the country. A family member reads the words into PasteOnce on an offline-then-bridged laptop, you import into a Nano S Plus, then sweep to a freshly generated seed.
An ops engineer provisions a HAProxy box before ACME is configured. The wildcard private key has to land once. PasteOnce delivers the AES-wrapped `.key` from a jump host; the engineer imports into `/etc/ssl/private` and rotates at the next renewal.
A Mac packaging firm needs your Developer ID Installer key for a quarterly notarized build. You export with `security export -k login.keychain -t identities -f pkcs12 -P passphrase`, share the `.p12` via PasteOnce and the passphrase by phone, then revoke in App Store Connect after the build ships.
Effectively never for a hot website. PasteOnce is a narrow exception because encryption happens in your browser and the ciphertext self-destructs on first read. Prefer hardware-wallet recovery flows that keep words on the device, and sweep funds to a fresh seed within the hour.
Auditors accept a documented, time-bounded handoff with rotation evidence. Encrypt the `.key` with AES-256 before paste, log it in change management, and rotate the certificate after import. Long-term, move to ACME automation (cert-manager, Caddy) so keys never leave the issuing host.
This page covers keypairs that authenticate a person, server, or wallet to the outside world: BIP-39 seeds, X.509 server keys, Authenticode and Apple Developer ID. Use share-encryption-key for symmetric AES and GPG/PGP, and share-ssh-key for OpenSSH login.
Yes for high-value wallets. Use a proper Shamir scheme (SLIP-0039 or `ssss-split` 3-of-5) rather than naive halving — splitting words 1-12 from 13-24 still leaks meaningful entropy if one half is intercepted. Assemble shares inside an offline wallet.