Disposable email
Mail.tm
Mail.tm provides temporary email addresses for receiving messages, with incoming mail stored for 7 days. The service does not send email, so its free address creation and API access cover receiving rather than two-way correspondence.
This may suit readers who need temporary inboxes or want to retrieve messages through an API, provided receiving alone fits their workflow.
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
Logos are trademarks of their respective owners and shown only to identify the service.- Name
- Mail.tm
- Category
- Disposable email
- Official site
- mail.tm · No link provided
- Facts checked
Mailboxes receive messages; sending is excluded
The vendor and documentation describe the service as follows, checked 2026-10-31.
- Registration: the vendor describes temporary mailboxes that require no registration.
- Address creation: the vendor says disposable addresses can be created at no cost.
- API access: the documentation says access is free, with no paid tiers.
- Sending: the vendor says email sending is not provided.
A temporary address leads to a readable inbox
Mail.tm’s stated use is receiving messages, including account activation codes; the vendor also lists sign-ups on untrusted sites, anonymous conversations, forums, and giveaways as intended uses. These are provider-described uses, not a guarantee that a third party will accept an address.
The vendor says each temporary mailbox has its own automatically generated password. In the FAQ’s description of the inbox, received email appears below the address, with the sender, subject, and message text visible.
That display gives a reader the basic fields needed to identify an incoming message. Check that those fields and the receiving-only scope match the task before using an address.
Free access has no listed paid tier
The vendor says disposable addresses can be created at no cost, while the documentation describes API access as free and says there are no paid tiers. The two statements cover address creation and API access respectively; they do not describe a separate paid plan.
The vendor also describes an unlimited* number of disposable addresses at no cost. Address creation and the API are therefore presented as free, but this does not change the receiving-only boundary.
For a workflow that depends on recurring access, distinguish the stated API terms from the address-creation claim and check whether the documented limits fit the expected use.
Browser access and REST API serve different routes
In the browser route, the vendor says the service runs on any device and can be added to a browser home screen. The vendor also describes automatic address creation and bulk registration of disposable mailboxes.
The API route is described in the documentation as a REST API for creating disposable email accounts and receiving email. It requires no API key or signup to start and follows the OpenAPI v3 specification. The documentation says the API provides available domain names.
After a message arrives, the documentation says it can be fetched through the API or received in real time using SSE. Check which retrieval route fits the application before building around the API.
Check these details before relying on a mailbox
These details help identify who is responsible for the service.
If a mailbox issue interrupts a workflow, the route to assistance matters.
Compare the answer with the tools and steps your workflow already uses.
Retention, sending, and API rules narrow use
The vendor states that incoming messages are stored for 7 days and that the service does not provide email sending. The documentation sets a general API quota of 8 queries per second per IP address.
The documentation bars building a paid product that only wraps the API, and separately prohibits mirroring or proxying the API under another domain. API users must also link back to mail.tm somewhere visible.
The vendor says mailbox passwords are generated in the browser, stored encrypted, and cannot be reset by the service. Several details are missing; they are listed under What we could not confirm.
Free access includes browser and API options
- The vendor describes Mail.tm as a browser service that runs on any device and can be added to a browser home screen.
- The documentation says the API can be started without an API key or signup, lowering the setup barrier for a receiving workflow.
- API users can fetch messages or receive them in real time through SSE, according to the documentation.
- The vendor describes automatic address creation and bulk registration of disposable mailboxes.
- The documentation says the API provides available domain names, so an application can retrieve that information through the API.
These features describe access and retrieval routes rather than email delivery in both directions. Check that the inbox workflow can use the browser or API route you intend.
Temporary receiving matches the stated scope
The vendor describes the service for receiving messages and account activation codes, and lists sign-ups on untrusted sites, anonymous conversations, forums, and giveaways as intended uses. Those examples reflect the provider’s stated scope, not a promise that another site will accept a temporary address.
The vendor also says users provide no personal data and sign no user agreements to use the service. For a workflow that needs only temporary receiving, compare that description with the information your process requires. Check how the workflow handles mailbox access and stored messages.
Compare disposable inboxes by retention and access
For disposable inboxes in general, compare how long an address remains active and how long messages are retained. Check whether sending is supported, whether API access is available, and what limits apply per user.
Review whether paid plans change access or retention, and whether privacy statements explain data handling specifically. For an API workflow, also compare setup requirements and the available message-retrieval methods. These criteria help distinguish a short-lived receiving inbox from a tool intended for a different mail workflow.
What we could not confirm
- Company details: legal entity, address, and operating history.
- Support: available channels and response times.
- Integrations: supported connections and setup requirements.
- Domains: available choices and how users select or change them.
- Per-user limits: restrictions beyond the stated API quota.
- Privacy: specific data-handling details beyond the vendor’s anonymity description.
Mail.tm questions about addresses and API use
Does creating an address require registration?
No, the vendor describes temporary email addresses as automatically created without registration or personal details. That description concerns address creation; it does not establish how every workflow that uses an address handles its own account requirements. Check whether the receiving task can use a temporary mailbox.
How long does a mailbox remain valid?
The vendor says a mailbox remains valid until the user deletes it. This is distinct from the storage period for incoming messages: the mailbox’s validity does not mean its messages remain available for the same period. Check the message-retention condition separately.
How long are incoming messages stored?
The vendor states that incoming messages are stored for 7 days. A mailbox may remain valid until deletion, but the stated message-storage period is separate. For any workflow that needs a message later, account for the retention period before relying on the inbox.
Can Mail.tm send email?
No. The vendor says Mail.tm does not provide email sending. The documented scope is receiving messages, including through the API. A workflow that needs outgoing correspondence therefore falls outside the service’s stated capabilities.
How can API messages be retrieved?
The documentation says messages can be fetched through the API or received in real time using SSE. The API is described as a REST API for creating disposable accounts and receiving email. Choose the retrieval method that matches the application’s message-handling workflow.
What happens to mailbox data when it is deleted?
The vendor says mailbox addresses and emails are erased when the mailbox is deleted. The vendor separately says passwords are generated in the browser, stored encrypted, and cannot be reset by the service. Check that mailbox deletion and password handling fit your access requirements.
Rely on Mail.tm only for receiving needs
Fits if temporary receiving is sufficient and the browser or documented API retrieval options match the workflow.
Probably not if the task requires sending email, which the vendor says the service does not provide.
Main risk… messages are stored for 7 days, and the documentation sets a general API quota of 8 queries per second per IP address. Check that retention and the applicable API quota fit the planned workload.
Sources
These public pages are the basis of the facts above; next to each is the date it was read.
- mail.tm/enchecked
- mail.tm/en/faqchecked
- docs.mail.tmchecked
How this page was prepared
Editorial team of Funnel Notebook. Source-based work: each fact comes from a page listed above, read on 2026-10-31 by the Funnel Notebook editors. There was no hands-on testing. The page is updated when the sources change.
Last updated:
Right of reply
Speaking for Mail.tm? If you believe the entry is inaccurate or stale, send us proof. We amend or withdraw the entry as soon as the refutation is on record. Money does not remove or soften an entry here.
- Our contact for replies
- No data available
- Response time
- No data available