Mail7 min read•
Encrypted email address: what it means, what it cannot mean, and how to get one
An encrypted email address stores every message sealed to a key only you hold. Here is the honest boundary with external senders, what the server can and cannot see, and how to set one up.
Try it in one click.
Three private surfaces. Same zero-knowledge architecture.
What people mean when they search for it "Encrypted email address" usually means: an address I can give out publicly, where the messages I receive are not readable by the company hosting them. That is achievable — but only with an honest description of where encryption starts.
The boundary nobody should hide When someone writes to you from a standard mail provider, that message crosses the internet under transport encryption (TLS) and arrives at the receiving server as readable content. No provider can change that; it is how SMTP works.
What a zero-access provider can do is seal the message the moment it arrives, before it is stored, using your public key — so from that point on, only your device can open it. The provider stores ciphertext and cannot read the archive, search it, or hand it over in readable form.
What DRIVUNO's mail actually does - Inbound messages are sealed to your account key (X25519) at ingestion; the stored form is ciphertext. - Bodies, subjects, attachments and HTML formatting are all encrypted, not just the body text. - Search runs on blind indexes: your device computes HMAC tags for senders, subjects and words; the server matches tags without plaintext. - Attachments open in a local viewer and can be saved straight into your encrypted drive. - Multiple addresses, display names and signatures are supported per account.
Two domains, two risk profiles Handing your main address to every form on the internet is what makes an inbox unusable. Using a separate public-facing domain for signups keeps deliverability problems, spam pressure and reputation issues away from the address your clients use. That separation is a configuration choice — and it is worth making before the volume arrives, not after.
What the server still needs Delivery requires envelope information: an address to route to, and timestamps. That is metadata, and any honest provider says so rather than claiming it encrypts everything including the routing.
When both sides are on DRIVUNO Messages between vault members never leave the sealed model at all: sender-side encryption, per-recipient key envelopes, no readable intermediate copy.
Getting started Create an address, set a display name and signature, point your existing mail forwarding at it, and keep the Recovery Kit offline. From then on, your archive is a pile of bytes nobody but you can open.
Try it in one click.
Three private surfaces. Same zero-knowledge architecture.