Disposable email

Mail.tm

Mail.tm logo on the cover of the review

Mail.tm keeps the mailbox available until deletion, but incoming messages have a shorter retention period: the FAQ says they are stored for 7 days. The service page promotes an “unlimited”* number of disposable addresses at no cost, while the API documentation describes free access with no paid tiers.

That distinction matters for anyone who needs to retain messages, rather than only receive them temporarily.

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
Each logo belongs to its owner and appears here only to help identify the service.
Name
Mail.tm
Category
Disposable email
Official site
mail.tm · No link provided
Facts checked

Addresses and Messages Have Separate Terms

The vendor’s homepage and FAQ, checked 2026-10-31, describe address creation, mailbox validity, and message handling.

  • Address creation: automatically created temporary addresses without registration or personal details (homepage, checked 2026-10-31).
  • Use: receiving messages and account activation codes (homepage, checked 2026-10-31).
  • Mailbox validity: remains until the user deletes it (FAQ, checked 2026-10-31).
  • Message storage: incoming messages are stored for 7 days (FAQ, checked 2026-10-31).
  • Sending: the service does not provide email sending (FAQ, checked 2026-10-31).

Free Access Has No Paid Tier

The API documentation states that API access is free, with no paid tiers.

The two statements concern different parts of the service: the homepage describes address creation, while the documentation addresses API access. For a buyer evaluating a workflow, the practical distinction is whether the requirement is disposable addresses, API access, or both.

The Inbox Shows Sender and Message Text

In the browser mailbox, received emails appear below the address with the sender, subject, and message text, according to the FAQ. The vendor says the service runs in a browser on any device and can be added to a browser home screen.

The vendor describes the service as intended for sign-ups on untrusted sites, anonymous conversations, forums, and giveaways. It also says the addresses can receive account activation codes. These are descriptions of intended use, not a substitute for checking the rules of the site where an address is used.

The diagram shows a temporary mailbox appearing and displaying received email.
Built from facts published on mail.tm; checked 2026-10-31.

Mailbox Deletion Removes Its Contents

Mailbox validity and message retention are separate conditions: the FAQ says a mailbox remains valid until deletion, while incoming messages are stored for 7 days. Deleting the mailbox erases both its address and emails, according to the FAQ.

The vendor says each mailbox has a unique, automatically generated password. Its FAQ adds that passwords are generated in the browser, stored encrypted, and cannot be reset by the service. Readers who need to recover access should clarify the password process before relying on a mailbox for anything they must keep.

REST and SSE Carry API Messages

The documentation describes Mail.tm as a temporary email API for creating disposable accounts and receiving messages through REST. It says the API follows OpenAPI v3 and requires no API key or signup to start.

The API provides available domain names; messages can be fetched through the API or received in real time using SSE. The documentation sets a general quota of 8 queries per second per IP address.

That quota is a practical constraint for API-based mailbox handling: clients need to account for requests per IP, not treat the interface as unrestricted. The documentation also describes bulk registration of disposable mailboxes for power users.

The diagram shows messages moving through the API for retrieval.
Built from facts published on docs.mail.tm; checked 2026-10-31.

Free Access Covers Browser and API Use

The API documentation states that access is free and has no paid tiers. It also says users can start without an API key or signup, reducing the initial access requirements described in the docs.

Messages can be fetched through the API or received in real time using SSE, and the API provides available domain names. For browser use, the vendor says the service runs on any device and can be added to a browser home screen. These documented paths give readers distinct ways to access incoming mail without changing the stated receiving-only scope.

Receiving Only Limits Mailbox Use

The FAQ and API documentation set boundaries on message delivery, recovery, request volume, and reuse of the interface.

  • The FAQ says incoming messages are stored for 7 days, while a mailbox remains valid until deletion.
  • The service does not provide email sending, so it is limited to receiving mail.
  • The vendor says the service cannot reset mailbox passwords.
  • The API documentation sets a general quota of 8 queries per second per IP address.
  • The documentation prohibits paid products that only wrap the API, and mirroring or proxying it under another domain.
  • API users must link back to mail.tm somewhere visible, according to the documentation.
  • The documentation prohibits using the API for illegal activity.

Several details are missing; they are listed under What we could not confirm.

The diagram shows what happens to a mailbox and its emails when deleted.
Built from facts published on mail.tm; checked 2026-10-31.

Temporary Receiving Defines the Fit

Mail.tm’s documented scope fits workflows that need temporary inboxes for receiving messages, including account activation codes. The vendor also describes anonymous conversations, forums, and giveaways as intended uses.

For API-based handling, the documentation describes message retrieval through the API or real-time delivery using SSE. This is a receiving workflow, not a two-way email service, and the stated message-retention period should suit the task.

The diagram shows a temporary mailbox receiving an account activation code.
Built from facts published on mail.tm; checked 2026-10-31.

Compare Inboxes by Retention and Sending

In general, compare disposable-email services by mailbox lifetime, message retention, and whether sending is supported. Also check API access, per-user limits, paid plans, available domains, and the provider’s privacy statements before choosing a service.

What we could not confirm

  • Company details: legal entity, address, and history.
  • Support: channels and response times.
  • Integrations: available connections and setup requirements.

Questions About Mailbox and API Terms

Does mailbox deletion happen when messages expire?

No. The FAQ says the mailbox remains valid until the user deletes it. Incoming messages are stored for 7 days, according to the FAQ. Deleting the mailbox removes both the address and its emails, according to the FAQ.

Can Mail.tm send email?

No. The FAQ states that the service does not provide email sending. Mail.tm is therefore described as a receiving service; the vendor says it can receive messages and account activation codes.

Can the service reset a mailbox password?

No. The vendor says mailbox passwords are generated in the browser, stored encrypted, and cannot be reset by the service. Each temporary mailbox also has a unique, automatically generated password, according to the vendor.

Can API users start without an API key?

Yes. The documentation says users can start without an API key or signup. It describes retrieving messages through the API or receiving them in real time using SSE.

What API quota does the documentation state?

The documentation sets a general API quota of 8 queries per second per IP address. This is the stated general quota; API users should also account for the documented conditions governing how the API may be used.

What API-use conditions does the documentation list?

The documentation requires API users to link back to mail.tm somewhere visible.

Proceed When Receiving Terms Fit

Fits if temporary receiving meets the task, the stated retention period works, and the API conditions match the intended use.

Probably not if the workflow needs outbound email or messages retained beyond the stated period.

Main risk is building around mailbox access without accounting for message expiry, the API quota, and the documented reuse restrictions.

Sources

Public pages the facts above were taken from, with the date each was read.

How we put this page together

Editorial team of Affiliate Index. The editors at Affiliate Index wrote this page from the public sources listed above, which were read on 2026-10-31. Nobody tried the service in practice. If a source changes, the page is revised.

Last updated:

Right of reply

Representatives of Mail.tm can contest this entry: write to us and attach evidence of the inaccuracy. We correct the entry or remove it once the refutation is documented. Entries are never removed or softened for payment.

Our contact for replies
No data available
Response time
No data available

Contact and right of reply · Affiliate disclosure

More write-ups filed under Disposable email

Back to the catalog