What "fake" actually means here
The name is a little misleading, so it is worth being precise. The address generated at the top of this page is not fake in any technical sense. It is a real mailbox on a real domain with valid MX records, and it will accept mail from any sender in the world.
What makes it fake is that it is not tied to you and is not meant to last. You use it, read what arrives, and discard it. Nothing about the address is invalid, which is exactly why it works where a made-up address like asdf@asdf.com does not: made-up addresses bounce, and most signup forms check for that.
When a disposable address is the right tool
- Testing your own software. Building registration, password reset, or role-change flows means running them repeatedly. Each run wants a clean address, and a personal inbox becomes useless within a day of that.
- One-time downloads and content gates. A whitepaper or sample file behind an email form, where you want the file and not the six-month drip campaign that follows.
- Receiving a one-time code. A service you will use once and have no ongoing relationship with.
- Limiting your footprint. A distinct address per service means a breach at one company cannot be correlated against your other accounts.
When it is the wrong tool
Being clear about this saves people from losing accounts, which is the most common way disposable addresses cause real harm.
- Anything you might need to recover. If the address is gone and you have forgotten the password, the account is gone too. No support team can help, because you cannot prove ownership of an inbox that no longer exists.
- Banking, government, healthcare, or work accounts. Not just unwise, often a breach of the provider's terms.
- Anything confidential. Messages sit on infrastructure we do not operate, and a disposable inbox is a convenience rather than a secure channel.
- Getting around a site that blocks disposable addresses. That block is a deliberate choice by the operator. Use a mailbox on a domain you control instead.
How to use the generator
- An address is generated as soon as this page loads. Copy it from the widget above.
- Paste it into whatever form is asking for an email.
- Watch the live inbox. Messages usually arrive within a few seconds, and the page updates without a refresh.
- Open the message to read a code or follow a link.
Pressing New replaces the address with a fresh one. Your browser forgets the old mailbox at that point, and because the address and its access token are what identify it, there is no way to get back to it. Copy anything you still need first.
Why the address survives a refresh
The current address, its generated password, and its access token are held in your browser's local storage. That is why reloading the page, or coming back later in the same browser, returns you to the same inbox rather than a new one. It also means the inbox does not follow you to a different browser or device, and clearing site data discards it permanently.
How long the messages themselves stay readable is not something we control. Delivery runs on our upstream provider's infrastructure, and retention is theirs to decide. Treat any disposable inbox as short-lived by default.
Why a generated address sometimes gets rejected
Sooner or later a form will refuse the address with a message like "disposable email addresses are not allowed". This is not a fault in the address. Sites check the domain against public blocklists of known disposable providers, and any long-lived disposable domain eventually lands on one.
Generating a new address will often produce a different domain, since they come from a rotating pool. But if a service has deliberately decided not to accept disposable mail, that is a legitimate product decision, and the right response is a mailbox on a domain you own. There is a fuller explanation of how detection works in why temp mail gets blocked.
Automating it
If you are generating addresses by hand to test the same flow repeatedly, automate it instead. The email testing guide has complete Playwright and Cypress examples.