Disposable email
Mail.tm
The vendor says received emails appear below the mailbox address with the sender, subject, and message text. The vendor states that incoming messages are stored for 7 days. The vendor also states that the service does not provide email sending. That makes the retention window and receiving-only scope important if a workflow depends on keeping messages or replying to them.
For media buyers assessing disposable inboxes, the practical question is whether temporary receiving fits the workflow without requiring longer storage or outgoing mail.
Editorial review based on public sources, without hands-on testing; facts checked on 2026-10-31.
This page contains no partner link to this service.
- Logo
Service logos remain the property of their owners; we use them for identification only.- Name
- Mail.tm
- Category
- Disposable email
- Official site
- mail.tm · No link provided
- Facts checked
Mailboxes receive mail, not replies
The provider’s homepage, FAQ, and API documentation describe the following, checked on 2026-10-31.
- Purpose: temporary email addresses for receiving messages (provider homepage and FAQ, checked 2026-10-31).
- Inbox display: sender, subject, and message text (provider FAQ, checked 2026-10-31).
- Sending: no email-sending function (provider FAQ, checked 2026-10-31).
Temporary addresses feed a simple inbox
Mail.tm describes its addresses as temporary and says they can receive messages and account activation codes. The provider lists sign-ups on untrusted sites, anonymous conversations, forums, and giveaways as intended uses. Those are descriptions of intended use, not evidence that every site accepts messages from these addresses.
In the browser inbox, received emails appear below the mailbox address with the sender, subject, and message text. The provider also describes the mailbox as anonymous and says registration is not required. That wording describes the service’s stated setup; it does not establish the scope of its data handling.
Free access covers addresses and API
The provider makes separate no-cost statements for disposable addresses and API access; the statements cover different parts of the service. The API documentation states that API access is free and has no paid tiers.
The docs state that users may not build a paid product that only wraps the API.
The API creates and retrieves mailboxes
Mail.tm documents a temporary-email API for creating disposable accounts and receiving email through REST. The documentation says access can start without an API key or signup, and that the API follows the OpenAPI v3 specification.
The docs state that the API provides available domain names. They also state that messages can be fetched through the API or received in real time using SSE.
Check identity, support, and setup first
Before relying on a disposable-email provider in a working process, ask which legal entity operates the service and how long it has operated. Those details help clarify who is responsible for the service and how to assess its continuity.
Ask which support channels are available and what response times to expect. Also clarify whether the intended integrations have documented setup requirements, since an API or browser inbox alone does not describe how it fits into a particular workflow.
Browser and API routes cover receiving
- The provider says the service runs in a browser on any device and can be added to a browser home screen.
- The browser inbox displays each received email’s sender, subject, and message text.
- The API documentation says access can start without an API key or signup.
- The API supports message retrieval and real-time delivery through SSE.
Retention and API rules narrow use
The provider says incoming messages are stored for 7 days, while mailbox validity lasts until the user deletes the mailbox. These are separate conditions: mailbox validity does not mean messages remain available for the same period. The provider also says deleting a mailbox erases its address and emails.
The API has usage conditions beyond retrieving messages. Its documentation prohibits paid products that only wrap the API and mirroring or proxying it under another domain. API users must also link back to mail.tm somewhere visible.
The documentation sets a general API quota of 8 queries per second per IP address. That quota matters when planning repeated or concurrent requests. Several details are missing; they are listed under What we could not confirm.
Short-lived receiving defines the fit
Mail.tm fits workflows that need a temporary address to receive messages or activation codes, as the provider describes those uses. Its stated use cases also include sign-ups, forums, giveaways, and anonymous conversations.
It is a weaker fit when the workflow needs outgoing email or messages retained beyond the stated storage period. Before using it in a process, map when messages must be retrieved and whether the mailbox will remain available for the required period.
Compare inboxes by retention and access
When comparing disposable-email services, check domain options, inbox lifetime, sending capability, API access, and per-user limits. These criteria distinguish a receiving-only inbox from a tool that supports a broader workflow.
Also compare paid-plan terms and the scope of each provider’s privacy statements. Ask how long messages persist, what happens when an address is deleted, and which access methods are covered by the stated terms.
What we could not confirm
- Company details: legal entity, address, and operating history.
- Support: available channels and expected response times.
- Integrations: supported connections and setup requirements.
- Mailbox domains: user selection or control options.
- Address limits: per-user caps and other rate limits.
- Data handling: privacy details beyond the anonymity description.
- Paid offerings: plans beyond the API pricing statement.
Mailbox and API conditions in brief
How long does a mailbox remain valid?
The provider says a mailbox remains valid until the user deletes it. That validity period is distinct from message retention: the FAQ gives a separate storage window for incoming messages. Deleting the mailbox also erases its address and emails, according to the provider.
How long are incoming messages stored?
The provider’s FAQ says incoming messages are stored for 7 days. That is the stated message-retention period, even though a mailbox can remain valid until the user deletes it. Workflows that need later access should account for this difference when deciding when to retrieve messages.
Can the service send email?
No. The provider says Mail.tm does not provide email sending, so its documented email function is receiving rather than replying or sending new messages. If a workflow requires outgoing mail, that requirement falls outside the service’s stated scope.
What does API access require to start?
The API documentation says access requires no API key or signup to start. It also describes fetching messages through the API and receiving them in real time using SSE. The documentation provides available domain names through the API.
Can a mailbox password be recovered?
The provider says mailbox passwords are generated in the browser and stored encrypted, and that the service cannot reset them. This makes password handling an operational consideration: users should understand the provider’s stated recovery limitation before relying on mailbox access.
What API request quota does the documentation specify?
The documentation gives a general API quota of 8 queries per second per IP address. Confirm that the planned request pattern fits the documented condition before building around repeated API calls.
Rely on it only for receiving needs
Fits if… the workflow needs temporary incoming mail and API-based retrieval within the documented usage conditions.
Probably not if… the process needs outgoing email or requires incoming messages to remain stored beyond the provider’s stated period.
Main risk… relying on a mailbox for later access without planning around message retention and the API’s documented conditions.
Sources
The facts above were taken from the public pages listed here, and each entry shows the date it was read.
- mail.tm/en/faqchecked
- mail.tm/enchecked
- docs.mail.tmchecked
How we put this page together
Editorial team of Stack Shelf. Prepared by the editorial team of Stack Shelf from the public sources listed above; the facts were checked on 2026-10-31. Nobody tried the service in practice. We revise the text whenever those sources are updated.
Last updated:
Right of reply
If you represent Mail.tm and think this entry is inaccurate or out of date, write to us and attach evidence. After the refutation is documented, the entry is corrected or removed. Entries are not removed or toned down in exchange for money.
- Our contact for replies
- No data available
- Response time
- No data available