Mailinator review

Mailinator is a hosted email and SMS message-routing service, not a library or a server you install in your application. It provides inboxes through a web interface and an API, so an application can send test messages to Mailinator addresses and a test suite can inspect what arrived. The inbox is created when mail is sent; teams do not have to provision each temporary address first.

In a development stack, Mailinator sits between the application’s outbound email or SMS flow and the automated test that checks the result. That makes it useful for sign-up verification, password resets, receipts, OTPs and 2FA journeys. Tests can read messages, extract a link or code and assert on it. Public inboxes support quick manual checks; private domains are intended for controlled team workflows. Mailinator also offers programmable email interactions, including clicking links and sending webhooks to services such as Slack. Its homepage says load testing requires an Enterprise subscription.

The integration surface is Mailinator’s API, its web UI, email-interaction rules and webhooks. The homepage names Selenium, Cypress, Playwright and Puppeteer as automation tools, and describes tests pulling messages from the API. It does not name an API protocol or authentication scheme, so check the vendor’s documentation for endpoint details, credentials and current limits before wiring a CI job.

Mailinator’s homepage blog lists SDK updates for C# 2.0.0, Python 1.0.9, JavaScript 1.1.2 and Ruby 1.1.1. A separate blog post says Codex used Mailinator’s CLI, but the homepage does not document its commands or supported workflows. Confirm current SDK and CLI support in the vendor’s docs rather than assuming a client covers every endpoint. For other integrations, the stated options are webhooks and rules that can click message links or forward to platforms such as Slack. The vendor also describes running checks in CI on each build.

Public - Free costs $0 per month and includes unlimited public inboxes, temporary storage, 24/7 uptime monitoring and no sign-up. Verified Pro is also listed at $0 per month for one user, with unlimited private inboxes, one private domain, 10MB permanent storage and 1K emails per month. Its free price does not make it a high-volume tier.

Business is $99 monthly or $79 per month billed annually. It includes five seats, one private domain, 50MB permanent storage, 100K emails per month and up to 20 emails per second. Business Plus is $199 monthly or $159 billed annually, with 10 seats, three private domains, 100MB permanent storage, 300K emails per month and up to 100 emails per second. Enterprise starts at $699 monthly and lists custom seats, 5+ domains, 3MM+ emails per month and up to 500 emails per second.

A two-week Business free trial is listed. SMS testing is available by request for an additional, unpublished charge on Business, Business Plus and Enterprise. Ask about overages and upgrades before launch; the pricing page lists upgrades for Business and Business Plus but no overage rates.

Mailinator is presented as a hosted service accessed through its web UI and API. The vendor doesn't publish its source licence, a self-hosting option or data-export guarantees on the vendor's site available to buyers. Treat it as a hosted dependency unless the vendor confirms otherwise in writing; teams that require source access or control of message storage should ask before adopting it.

Migration risk depends on how much test code is coupled to Mailinator’s API, inbox naming and message format. Keep the inbox-reading layer behind a small internal adapter, and avoid spreading provider-specific calls through application tests. That does not remove the work of moving existing test data or replacing message interactions, but it narrows the code changes if you switch providers. Confirm export formats, retention and account-termination handling with the vendor.

The published plan limits matter when CI runs many parallel workflows: Business lists 100K emails per month and up to 20 emails per second, while Business Plus lists 300K and up to 100 emails per second. Enterprise lists 3MM+ emails per month and up to 500 emails per second. The homepage says Enterprise is required for email load testing. Treat these figures as plan ceilings, not a guarantee of delivery latency or an uptime SLA; the free plan’s 24/7 uptime monitoring is not itself an uptime commitment.

Separate public inboxes from private test domains. Messages in public inboxes are visible to others, so do not send credentials or personal data there. One Reddit thread notes that some sites block Mailinator addresses; that affects using disposable addresses for external sign-ups, though it is less relevant to controlled app tests. Before depending on the service, confirm retention, rate-limit behavior, incident support, security controls and any compliance requirements with the vendor. Add retries and timeouts so a delayed test message does not silently pass or stall CI.