en

Anonymous Email Services on the Dark Web: Complete 2026 Guide

Email is one of the most surveilled communication channels: every provider logs IP addresses, building a metadata trail linking accounts to physical locations. For users whose threat model includes adversaries capable of compelling providers to hand over logs, or who operate in jurisdictions where accessing certain services triggers surveillance, anonymous email is essential. Dark web .onion services enable email that routes entirely through Tor, preventing IP-based account linking. This guide covers major anonymous email services accessible through Tor, PGP encryption integration, and self-hosting an anonymous mail server.

Need this done for your project?

We implement, you ship. Async, documented, done in days.

Start a Brief

Threat Model for Anonymous Email

Email metadata (sender, recipient, timestamp, IP address of sender) is distinct from message content. PGP encryption protects content but not metadata. Anonymous email protects against: IP address logging that links your account to your physical location, and account registration requiring phone numbers or verified identity. It does not protect against: recipient-side exposure (emailing Gmail means Google sees the message), operational security failures (using anonymous email from a device linked to your identity), or traffic analysis by a global passive adversary. Combine anonymous email with PGP encryption for content protection and strict operational security for maximum protection.

ProtonMail and Tutanota via Tor

ProtonMail operates a verified .onion address (check the official ProtonMail FAQ for the current v3 address). ProtonMail provides end-to-end encryption between ProtonMail accounts and supports PGP for email to other providers. Account registration via .onion does not require a phone number when accessing the Tor address. Important limitation: ProtonMail has complied with Swiss law enforcement requests revealing IP addresses in documented cases. Tutanota works via standard Tor Browser without a dedicated .onion. Both providers are suitable for users with moderate threat models who are not targeted by nation-state adversaries.

Onion-Native Email Services

Several email services operate exclusively or primarily via .onion addresses. DNMX provides free .onion email requiring only a username and password - no phone, no clearnet IP required. OnionMail provides @onionmail.org addresses with SMTP access designed for Tor users. These services vary in reliability and longevity - .onion email services have historically had inconsistent uptime. Use .onion email for pseudonymous identity establishment and back critical communications with PGP encryption regardless of provider. Always assume metadata is visible to the provider and encrypt content with PGP for sensitive messages.

Self-Hosting Email Over Tor with Postfix

Self-hosting an email server as a Tor hidden service provides maximum control. Install Postfix (SMTP), Dovecot (IMAP), and optionally Roundcube (webmail) listening only on localhost, mapped through Tor to appropriate ports. For inbound email from clearnet, configure Postfix to receive on a clearnet IP - this is unavoidable for receiving from @gmail.com senders - but log minimally. For outbound email, route through Tor using Postfix's smtp_bind_address or a Tor SOCKS proxy. Note: receiving email to an .onion address from clearnet senders is not possible - clearnet MX records cannot point to .onion addresses. Self-hosted .onion email is practical for closed groups of Tor-to-Tor users sharing the same mail server.

PGP Integration with Anonymous Email

PGP encrypts email content so only the intended recipient can read it. Anonymous email providers protect metadata; PGP protects content. Use GnuPG (GPG) for key management. Generate a key pair: gpg --full-generate-key. Publish your public key to keys.openpgp.org (accessible via .onion). In Thunderbird, use the built-in OpenPGP feature. For webmail without native PGP, the Mailvelope browser extension adds PGP support. Key hygiene: use an expiring key (2-year validity), rotate annually, publish revocation certificates, and keep the primary key offline using a subkey architecture.

Why Anubiz Host

100% async — no calls, no meetings
Delivered in days, not weeks
Full documentation included
Production-grade from day one
Security-first approach
Post-delivery support included

Ready to get started?

Skip the research. Tell us what you need, and we'll scope it, implement it, and hand it back — fully documented and production-ready.

Anubiz Chat AI

Online