ddl.lt/aZ3k9pQ#Xf8…
Swift
DefaultOne short link carries everything. The key lives after the # and never reaches the server.
- 128-bit key, HKDF → AES-256
- Shortest link
- Best for one trusted channel
Link it. Seal it. Send it.
Short links, secrets, files and folders. Encrypted on your device, opened only by who you choose. For people and AI agents.
AES-256-GCM in your browser
No account
Analytics without tracking you
Choose what to send — or drop files anywhere
How it works.
01
Choose
Paste a link or a secret, or drop files or a whole folder into the portal. No sign-up.
02
Encrypt
AES-256-GCM runs in your browser in one of three modes. The server only ever stores ciphertext.
03
Share
A short ddl.lt link with expiry, view limits, a password or a split key — plus live stats.
The server keeps the ciphertext. The key travels in the part of the link after the # — the part browsers never send.
Encryption modes
Three ways to seal.
Every mode is AES-256-GCM end to end. They differ in what someone needs to open the seal — pick the one that matches who might be watching.
#Xf8…+••••••••
Shield
PasswordThe link and a password together. A leaked link alone opens nothing, and a wrong password never burns the seal.
- PBKDF2-SHA256, 600 000 rounds
- Key = link key ⊕ password key
- Send the password another way
#1.Qm7…
#2.p0L…
Split
Two channelsA 256-bit key cut into two halves, one per link. Send them over different channels; either half alone is random noise.
- XOR secret sharing, 256-bit
- Optional password on top
- For the secrets that matter most
All modes use a possession proof: link scanners and wrong passwords can't burn a one-time seal, and 10 wrong tries destroy it.
Short links
A shortener that knows
when to forget.
Everything you expect from a link shortener — and the option to encrypt the destination itself, so not even ddl.lt knows where it leads.
Live analytics
Clicks per day, referrers, devices and countries. Bots counted apart. No cookies.
Custom names
ddl.lt/launch instead of a random code — free.
QR codes
Every link has a crisp vector QR, ready for print.
Edit later
Change where a printed link points, any time.
Preview pages
Add ~ to any link to see where it goes before you go.
Expiry & limits
Links that stop after a date or a number of clicks.
Sealed destinations
Encrypt the target URL. The server can't read it.
Agent-ready
MCP server and HTTP API. Agents shorten and seal too.
| ddl.lt | Bitly | SEAL | |
|---|---|---|---|
| Short links with analytics | ● | ● | — |
| Free custom names & QR | ● | paid | — |
| End-to-end encrypted files & secrets | ● | — | ● |
| Encrypted link destinations | ● | — | — |
| Three encryption modes incl. split key | ● | — | — |
| Scanner-proof one-time links | ● | — | — |
| MCP for AI agents | ● | ● | ● |
| No account needed | ● | — | ● |
For AI agents.
The same seals, for the agents you work with. Keys and large files move between people and agents encrypted on the sending machine — nothing secret is ever pasted into a chat.
Agent → Person
An agent seals a report, a build or a key and hands you one short link. It opens in any browser, no account.
Person → Agent
An agent asks for an API key. You answer on a ddl.lt page; it's encrypted to the agent's key, and the agent gets a file path — never the value.
Agent → Agent
A seal addressed to another agent's public key opens only for that agent. A leaked link is useless to anyone else.
Math, not promises.
AES-256-GCMEvery byte, in 1 MiB authenticated chunks
HKDF-SHA256Separate keys for content, files and proof
PBKDF2 ×600kPasswords hardened before they touch a key
ECDH P-256Seals addressed to an agent's public key
Proof-of-keyOne-time seals only burn for who holds the key