Enter
The recipient enters the six-character code exactly as received.
01 How it works
From six characters to a protected destination in four deliberate steps.
The visitor sees a calm transition. Behind it, Zulde performs validation, encryption, signing, and destination checks.
Open with a code →
02 Process
A visible sequence with a protected core.
Verify
Zulde checks status and rate limits without revealing whether an email exists.
Prepare
The recipient email becomes an encrypted UID inside a signed, time-bound server request.
Open
A validated one-time URL replaces the current page after the secure opening transition.
03 Detail
Built around a smaller access surface.
A new handoff every time
The six-character code remains usable until revoked, but every successful lookup asks the shared service for a new five-minute destination.
- No link cache
- No browser-visible UID
- No raw-email fallback
No unsafe shortcut
If encryption, signing, upstream communication, or destination validation fails, the visitor stays on Zulde and receives a generic retry message.
- Strict HTTPS host allowlist
- Exact token shape
- Generic public errors