Written and reviewed by the team operating TempMail Cloud. Product claims are checked against our live service and our editorial standards.
A signed-in TempMail Cloud account can own multiple receive-only inboxes and open them from its mailbox list. The browser's list of 30 recent mailbox references is a convenience limit, not a 30-inbox account quota and not an automatic deletion rule.
Create the right set of inboxes
Create a random or custom address while signed in so it belongs to your account. For a group of test identities, use Bulk create email addresses, select the available domains and choose between 1 and 200 inboxes for that batch. Save the returned credentials securely.
Additional batches are available subject to service protections. This is not a promise of unlimited automated requests or approval to create accounts contrary to another website's rules.
Keep these access concepts separate
| Item | What it controls | What it does not do |
|---|---|---|
| Account login | Lists and opens owned inboxes | Reveal every original mailbox password |
| Individual mailbox credential | Opens its applicable mailbox login | Grant ownership of all account inboxes |
| Browser recent list | Offers convenient access to remembered addresses | Define every existing inbox or delete the oldest one |
| Folder | Organizes owned inboxes | Create a separate team permission boundary |
| Share link | Grants its configured read-only view | Give the recipient the account password |
At signup, the initial account and registration mailbox start with the same chosen password, but they are separate records. Change Password inside the inbox changes the mailbox password only. The unified login form treats a registered account address as an account login and still requires the account password.
Worked organization example
For a small QA project, keep a folder for regression identities and a folder for short-lived test runs. Use one stable account-owned inbox to test notices across deployments, and separate fresh inboxes for parallel signup cases. In your test tracker record the actual returned address and a non-sensitive purpose label; keep credentials in a protected store.
The current product supports up to 30 folders with names up to 40 characters. That folder limit is also separate from the browser's 30 recent addresses. Do not embed customer identifiers or passwords into either names or folder labels.
Open an older address
If an address disappears from the browser's recent list, check the signed-in account's owned inboxes. A valid owner session can open an owned mailbox without entering its individual password. If it was a guest inbox, use its saved full address and mailbox password while it remains available.
Do not create a new mailbox with a similar name and assume old messages will appear there. The domain is part of the identity. Follow inbox recovery if no saved access works.
Removal, deletion and sharing are different actions
Removing an inbox from your account detaches ownership; it does not erase the mailbox and it may remain accessible through its own credentials. Deleting a message is a separate action. Server-side mailbox deletion or restoration involves the operator's available controls and retention policy, without guaranteed recovery.
For a reviewer, use restricted inbox sharing instead of distributing your account password. Review active links when a test or collaboration ends.