havenmessenger.com valid

Haven Messenger

Haven is an end-to-end encrypted email + messaging platform built on a zero-knowledge architecture. The servers never see your plaintext, even under subpoena. PGP email, MLS chat (IETF RFC 9420), identity aliases, and an encrypted vault — all under one identity, all with keys only the user holds. Open standards, no ads, no tracking, no backdoors.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T21:26:58.970Z. Cached copy · Source on havenmessenger.com

# Haven Messenger

> Haven is an end-to-end encrypted email + messaging platform built on a zero-knowledge architecture. The servers never see your plaintext, even under subpoena. PGP email, MLS chat (IETF RFC 9420), identity aliases, and an encrypted vault — all under one identity, all with keys only the user holds. Open standards, no ads, no tracking, no backdoors.

Haven exists for two overlapping audiences:

- **Privacy enthusiasts** (the larger group). The largest segment of Haven's user base. People who use Signal on their phone, host Bitwarden themselves, run Tor Browser sometimes, who read Schneier and follow EFF / privacytools.io. They're not paid to care; they care because surveillance capitalism offends them. Often technically literate, sometimes not — but always committed. They evaluate tools against open-source posture, threat-model honesty, jurisdictional architecture, and operator trust questions. They chose Proton/Tuta over Gmail, Signal over WhatsApp, Bitwarden over LastPass.
- **Professional users with existential E2EE need**: Journalists & investigative reporters, Activists & human rights workers, Lawyers & legal professionals, Writers & authors, Healthcare workers. Higher per-user stakes; same encryption, same software.

Haven is independent — no investors, no VC funding, no board. Single-jurisdiction by deliberate choice (jurisdiction not published in machine-readable form). The architecture is auditable; the threat model is stated plainly; the financial model is "subscription, not surveillance."

## Product surfaces

- [Landing page](https://havenmessenger.com/): Product overview, feature matrix, pricing.
- [About](https://havenmessenger.com/about): The story behind Haven, what makes it different from Proton / Tutanota / Signal, the operator behind it, the threat model in plain language.
- [Blog](https://havenmessenger.com/blog/): 477 long-form posts on privacy architecture, encryption protocols, surveillance trends, product design decisions. New posts daily.
- [Privacy policy](https://havenmessenger.com/privacypolicy): What data Haven holds (very little, by design), what crypto protects it, what jurisdiction governs it.
- [Web app](https://havenmessenger.com/app): The actual encrypted email + messaging interface. Flutter Web shell — content is end-to-end encrypted and unavailable to any external observer including AI crawlers.
- Onion service: `haven4lifputq7xgqw4n5cnlivejcs55hpcuo3ah64abpfknqfen7aad.onion` (Tor v3 hidden service).

## Technical architecture (one-paragraph summary)

PGP/OpenPGP for email encryption (RSA-4096 / Ed25519+X25519 keys, generated client-side, private key encrypted with PBKDF2 at 210k iterations and never leaves the device). MLS (Messaging Layer Security, IETF RFC 9420) for chat — the same protocol behind the most rigorously analyzed next-generation messengers. Matrix federation for cross-server interop. Encrypted vault for files, notes, and credentials, keyed by the user's passphrase. Server infr
…

Machine-readable: GET /v1/resolve?q=havenmessenger.com · GET /v1/domain/havenmessenger.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for havenmessenger.com:
1. POST https://agentwebmap.com/v1/sites/havenmessenger.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://havenmessenger.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/havenmessenger.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/havenmessenger.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.