Multi-Inbox is Here: Manage 5 Emails at Once

We just shipped one of our most requested features ever: the ability to manage up to 5 temporary email addresses at the same time within a single browser tab. And the best part? It is completely free. No premium tier, no hidden paywall, no limitations on functionality. Every user who verifies through Discord gets the full experience.

This was not a quick feature to build. Behind the scenes, Multi-Inbox required a fundamental rethinking of our frontend architecture, our WebSocket session management, and our in-memory data model. In this post, we will explain why we built it, how it works under the hood, and how you can start using it today.

Why Do I Need Multiple Inboxes?

Sometimes one temporary email just is not enough. When we analyzed our user feedback and support tickets over the past six months, a clear pattern emerged: our most active users were opening multiple browser tabs or Incognito windows just to manage parallel email workflows. This was clunky, error-prone, and easy to mix up.

Our power users described complex workflows that require multiple simultaneous identities. Here are the most common scenarios we heard about:

• A/B Testing for Developers: Software developers signing up for their own application twice to test how two different users interact with each other. For example, testing a referral system, a friend request flow, or a messaging feature between two accounts. Previously, this required two separate browser windows.
• Service Comparisons: Signing up for Amazon Prime and Walmart+ simultaneously to compare welcome offers, trial periods, and pricing without revealing your real email to either service. This is especially useful for deal hunters and personal finance bloggers who compare subscription services regularly.
• Separate Categories: Keeping one email for tech-related downloads and another for forum signups, so the inboxes stay organized and do not get mixed up. Many users told us they wanted to keep their "shopping" temp mail separate from their "forum registration" temp mail.
• Security Research: Penetration testers and security researchers often need to create multiple accounts on a target system to test for authorization bypass vulnerabilities, session management flaws, or privilege escalation bugs. Multiple inboxes in one tab make this workflow dramatically faster.
• Journalism and Investigations: Investigative journalists who need to create multiple anonymous accounts to verify information from different angles without any of the accounts being traceable back to their real identity or to each other.

Before Multi-Inbox, you had to juggle Incognito windows, different browsers, or even different devices. Now, everything is consolidated in one clean, tabbed interface.

How to Unlock Multi-Inbox

Multi-Inbox is a powerful feature that, if left unprotected, could be abused by spammers and bots to generate thousands of parallel email addresses. To prevent this while keeping the feature free for real humans, we implemented a simple verification mechanism tied to our Discord community.

Step-by-Step Guide:

1. Go to the fake.legal homepage and locate the "Multi-Inbox" promotional box below the main email interface.
2. Click "Unlock with Discord". This will open a Discord OAuth window.
3. Join our Discord server if you have not already. It takes about 10 seconds.
4. In our server, navigate to the #verification channel. This is clearly labeled and pinned in the channel list.
5. Type /verify to trigger our verification bot. It will send you a unique 6-digit verification code via a private direct message.
6. Copy that code and paste it back into the verification modal on fake.legal. The unlock is instant.

Once verified, the lock icon on the "+" button disappears permanently for your browser session. You can immediately start adding new inbox tabs. The verification persists in your browser's local storage, so you will not need to re-verify unless you clear your browser data or switch devices.

Why Discord? Our Reasoning

We chose Discord verification over other methods for two carefully considered reasons:

1. Community Building: We genuinely want to talk to our users. Our Discord server is where we post detailed changelogs for every update, take feature requests and vote on priorities, run polls about what to build next, and provide real-time support when users encounter issues. It is also where users help each other with tips, workarounds, and creative use cases we never even thought of. Having a direct line of communication with our user base has been invaluable for making fake.legal better.
2. Effective Bot Protection: Discord has some of the best anti-bot infrastructure on the internet. Discord accounts require email verification, phone verification for certain actions, and increasingly sophisticated behavioral analysis. By linking Multi-Inbox access to a verified Discord account, we ensure that one real human gets one set of 5 inboxes. This prevents spammers and automated scripts from creating 10,000 parallel inboxes to crash our servers or use our service for mass-mailing campaigns. We considered alternatives like CAPTCHA verification, but CAPTCHAs are increasingly solvable by AI, and they provide a much worse user experience.

Technical Architecture Behind Multi-Inbox

For the technically curious, here is how Multi-Inbox works under the hood. When a standard user connects to fake.legal, a single WebSocket connection is established, linked to a single inbox identifier stored in our Redis database. All incoming emails addressed to that identifier are pushed through the WebSocket to the browser in real time.

With Multi-Inbox, we extended this architecture to support multiplexed sessions. A single WebSocket connection now carries messages for up to 5 separate inbox identifiers. Each message includes a channel tag that tells the frontend which tab should display the incoming email. This is significantly more efficient than opening 5 separate WebSocket connections, which would waste server resources and degrade performance.

On the frontend, each tab maintains its own independent state: its own email address, its own inbox contents, its own expiration timer, and its own domain selection. When an email arrives on the WebSocket, the frontend router inspects the channel tag and dispatches the message to the correct tab. If the tab is not currently active, a red notification badge appears on the tab header so you know a new email has arrived.

Pro Tips for Multi-Inbox Power Users

• Timers are Independent: Each inbox has its own separate lifespan. You can configure one inbox to expire in 10 minutes for a quick verification and another to last 24 hours for a longer testing session. Expiration of one inbox does not affect the others.
• Visual Notifications: We display a red dot indicator and a subtle animation on any tab that receives a new message while you are looking at a different tab. This way you never miss an important verification code, even when you are actively working in another inbox.
• Independent Domains: Each inbox can use a different domain from our available pool. This is useful when testing how different services react to different domains, or when you want to keep particular registrations completely separated.
• Quick Copy: Each tab has its own one-click copy button. You do not need to switch between tabs to copy an email address—just right-click the tab header to copy the address directly to your clipboard.
• Session Persistence: Your Multi-Inbox configuration survives page refreshes. As long as you do not close the browser tab entirely or clear your local storage, all your inboxes and their contents will be exactly where you left them.

Privacy Considerations

A natural question arises: does Multi-Inbox compromise privacy by linking multiple identities together? The answer is no. All inbox data remains in volatile RAM and is never persisted to disk. The verification token stored in your browser is a one-way hash that cannot be used to trace back to your Discord account. We do not log which addresses you generate or what emails you receive. The Multi-Inbox feature was designed from the ground up with the same zero-knowledge principles that underpin the rest of fake.legal.

---