Disposable email
Mail.tm
Mail.tm says it provides automatically created temporary email addresses without registration or personal details, and its FAQ says incoming messages are stored for 7 days. Its docs describe a temporary email API for creating disposable email accounts and receiving emails via REST; the FAQ says the service does not provide email sending.
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
Mailbox and API access are free
The provider and documentation describe these access conditions, checked on 2026-10-31.
- Address creation: the vendor states it costs nothing.
- API access: the documentation states there are no paid tiers.
- Browser access: the vendor says the service runs on any device.
- Email function: receiving only; the service does not send email.
Temporary addresses receive incoming mail
Mail.tm describes its mailboxes as temporary and requiring no registration. The vendor says addresses are created automatically without personal details. Its stated use cases include sign-ups on untrusted sites, anonymous conversations, forums, and giveaways.
In the inbox, received messages appear below the mailbox address with the sender, subject, and message text. The vendor also describes receiving account activation codes as a use for the service. Whether a particular site accepts a disposable address is a separate consideration; the service’s stated use cases do not establish acceptance by other sites.
Address creation and API access cost nothing
The vendor states that disposable address creation has no cost. Separately, the API documentation describes access as free and says there are no paid tiers. These are provider statements about access, not a description of every possible cost associated with a reader’s own implementation.
The two claims cover different parts of the service: creating addresses and using the API. The vendor describes bulk mailbox registration for power users, while the documentation’s pricing statement concerns API access. Buyers considering a product built around the API should check its permitted use, rather than treating free access as permission for every deployment.
Mailbox deletion removes its address and email
The vendor says a mailbox remains valid until its user deletes it, while incoming messages are stored for 7 days. It also states that deleting a mailbox erases its address and emails. These are distinct conditions: mailbox validity does not mean each message remains stored for the mailbox’s full lifetime.
Before relying on an inbox, clarify what happens to any information your workflow needs after message storage ends. In general, buyers assessing a temporary mailbox should ask how deletion is handled and whether their own records need to be retained separately. Mail.tm’s stated deletion behavior makes that distinction relevant.
REST and SSE cover message retrieval
Mail.tm’s API documentation describes creating disposable email accounts and receiving email through REST. It says the API requires no key or signup to start. The documentation also says the API provides available domain names.
For retrieval, the docs list both fetching messages through the API and receiving them in real time through SSE. They state that the API follows the OpenAPI v3 specification. The general quota is 8 queries per second per IP address, according to the API documentation.
Sending and API use have limits
- The documentation says users may not build a paid product that only wraps the API.
- The documentation prohibits mirroring or proxying the API under another domain.
- The documentation requires API users to link back to mail.tm somewhere visible.
- The documentation sets the general API quota at 8 queries per second per IP address.
- The vendor says mailbox passwords are generated in the browser, stored encrypted, and cannot be reset by the service.
Browser inboxes and API retrieval are listed
The documented features cover mailbox access, credentials, and message retrieval.
- The vendor says each temporary mailbox has its own automatically generated password.
- Mail.tm’s API documentation says access starts without an API key or signup.
- The docs describe message retrieval through the API or real-time SSE.
- The vendor says the service runs in a browser on any device and can be added to a browser home screen.
Compare inbox retention and retrieval criteria
In general, compare disposable-email services by available domains, inbox lifetime, sending capability, API access, user limits, and paid plans. Check which conditions apply to the browser inbox and which apply to API use.
Temporary sign-ups define the stated use
Mail.tm’s stated use cases include receiving messages and activation codes. The vendor also describes sign-ups on untrusted sites, anonymous conversations, forums, and giveaways as intended uses. Those descriptions do not establish whether another platform will accept a disposable address.
The vendor says users provide no personal data and sign no user agreements to use the service. The API documentation prohibits using the API for illegal activity. Use must also follow applicable platform rules and local law.
What we could not confirm
- Company details: legal entity, address, and history.
- Support: contact channels and response times.
- Integrations and setup requirements.
Questions about Mail.tm inboxes and API
Does creating an address cost anything?
The vendor states that users can create disposable addresses at no cost. The API documentation separately says API access is free and has no paid tiers. These statements concern address creation and API access, respectively.
How long does a mailbox remain valid?
The vendor says a mailbox remains valid until the user deletes it. That describes the mailbox, not the retention period for each message. The distinction matters when a workflow depends on keeping messages accessible.
How long are incoming messages stored?
The FAQ says incoming messages are stored for 7 days. This message-storage period is separate from the mailbox’s validity, which the vendor ties to user deletion.
Can Mail.tm send email?
No. The vendor says the service does not provide email sending. Its documented email function is therefore receiving messages, rather than sending outbound mail.
How does API message retrieval work?
The docs say messages can be fetched through the API or received in real time using SSE. They also state that API access requires no API key or signup to start.
What API request quota applies?
The API documentation also prohibits building a paid product that only wraps the API.
Proceed only when receiving fits
Fits if temporary receiving addresses or API-based message retrieval match the intended workflow.
Probably not if the workflow requires outbound email, which Mail.tm does not provide.
Main risk… message retention and API-use conditions may not suit workflows that require longer access or a different deployment model.
Sources
Every fact on this page traces back to a public page listed here, with the day it was read.
- mail.tm/enchecked
- mail.tm/en/faqchecked
- docs.mail.tmchecked
Notes on the making of this review
Editorial team of Payout Desk. This page rests on the public sources listed above, which Payout Desk checked on 2026-10-31. There was no hands-on testing. The page is updated when the sources change.
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. No payment changes what we publish.
- Our contact for replies
- No data available
- Response time
- No data available