Mail.cx vs Mail.gw
Mail.cx
mail.cxMail.gw
mail.gwSide by side
| Figure | Mail.cx | Mail.gw |
|---|---|---|
| Price from | $0.82/mo | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| API | Yes | Yes |
| Plans published | 4 | 1 |
| Spec score · Temporary email services | 9.1 (#4) | 7.7 (#23) |
| Spec score · Temporary Email Services | 8.9 (#6) | 7.7 (#18) |
| API | The REST API supports long-polling inboxes, retrieving parsed or raw email, downloading attachments, and server-sent event delivery. | The API creates temporary email accounts and is described as intended to automate email confirmation during testing. |
| Support | The contact page says support normally responds within two business days and prioritizes security and abuse reports. | The contact page lists [email protected], Discord, and Telegram as ways to contact the service. |
| Use cases | Mail.cx targets developers, QA teams and product teams testing verification, transactional email, notifications and application integrations. | The FAQ suggests temporary email for signing up to online accounts or sharing private thoughts online. |
Plans
In their own words
Mail.cx
Mail.cx provides short-lived inboxes for developers, QA teams, and product teams checking account verification, transactional messages, notification pipelines, or application integrations. It only receives email; it does not send it. A web inbox can be opened without signup by choosing a username or generating one, and server-sent events can push arriving mail to the browser. Its REST API supports long-polling, retrieval of parsed or raw email, attachment downloads, and event delivery. API use is limited to 10 requests per second per token; long-polling allows one concurrent wait per token and 10 per address. Free messages are automatically deleted after one hour, while Pro messages are retained for 72 hours. The Free plan is free, and Pro is $9.90 a year. A separate pricing note lists paid plans from $4/mo. Mail.cx says connections use TLS and that passwords and API tokens are stored as hashes. Its terms caution that message retention and recovery are not guaranteed, and advise against relying on the service for critical, sensitive, or business-essential communications.