Disposable email
Mailsac
Mailsac receives application email at disposable test addresses or a customer’s domain, then lets teams read that mail through an API. Anyone can read public @mailsac.com inboxes, so they are unsuitable for sensitive test data; a free account includes a private address, while paid plans add custom test domains that only the team can read.
This is most relevant to developers and QA teams checking application email; it should not be treated as personal mail storage.
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.
- Name
- Mailsac
- Category
- Disposable email
- Official site
- mailsac.com · No link provided
- Facts checked
Public addresses sit beside private testing
Mailsac’s homepage, pricing page, and documentation describe these service details, checked on 2026-10-31.
- Service type: disposable-first email testing service and API (documentation, checked 2026-10-31).
- Public receiving: any @mailsac.com address can receive test mail without an inbox being created first (homepage, checked 2026-10-31).
- Free account: includes an API key, 1 private address, and 1,500 operations per month (pricing page, checked 2026-10-31).
- Mail options: public disposable email and mixed public-private testing (documentation, checked 2026-10-31).
Test addresses receive application email
Mailsac frames its service around developers and QA teams testing application email during software development. The provider says it accepts nearly all email, functioning like a fake SMTP server for test workflows.
The documentation covers custom domains and private email addresses, while the provider describes receiving test messages at a customer’s own domain and reading them through an API. Public addresses are a separate option: their inboxes are readable by anyone, unlike team-readable custom test domains on paid plans.
For individual developers, the provider says API keys can replace account and billing logins; usage is tracked by API key, domain, and enhanced address.
REST and event interfaces expose test mail
A test message can be received at an address and read through Mailsac’s REST API; the provider says this works in automated tests across programming languages and CI systems. The documentation also lists REST APIs, WebSockets, and Webhooks for fetching and managing email.
Mailsac describes REST, WebSockets, and Webhooks as integration routes for testing pipelines. For private email, the Enterprise page lists SMTP, HTTP/JSON, WebHooks, and Web Sockets as sending and receiving interfaces. These are documented access paths, not a promise that every workflow uses the same connection method.
Mail can also be routed to Slack or checked through POP3, according to the documentation. The pricing page counts an operation as an email received, an API call, or a forward or push. That definition matters when estimating usage: receiving a message and then retrieving or forwarding it can involve different operation types.
Paid tiers add domains and operations
The pricing page lists Indie at $18 monthly or $169 billed yearly, Business at $89 monthly or $840 billed yearly, and Business+ at $199 monthly or $1,900 billed yearly. Its Enterprise listing gives $799 monthly or $7,500 billed yearly.
The provider says paid plans start at $18 per month and add custom test domains readable only by the team. Enterprise pricing is based on monthly operations, including received emails, API calls, and pushes; its Enterprise page lists annual pricing of $7,500 per year for up to 2 million monthly operations.
Enterprise month-to-month billing is by card, has a 3-month minimum, and can be canceled after that minimum, according to the pricing page. The Enterprise page says plans include 25 users, with additional users priced at $24 per user per year. Dedicated instances are optional on annual plans and quoted on request.
Enterprise billing also supports quotes, purchase orders, ACH payments, and consolidated multi-account billing, according to the provider. Phone or video support costs $800 per four-hour block, with the first two hours per year free, according to the Enterprise page.
Check retention before relying on test mail
Before routing application messages through a testing service, ask what retention window the workflow requires and whether messages remain available for that period. A useful answer should match the team’s test cycle, including time needed to inspect failures.
Ask how the provider handles the traffic pattern your test suite creates, including throttling and the message types or domains you plan to use. Clarify what the provider counts as an operation across receipt, retrieval, forwarding, and push events.
For workflows with more than one user, ask how addresses and usage limits are allocated per user. Also request the scope of security controls and audit materials relevant to the data your tests contain.
Public mail and service terms narrow reliance
Public @mailsac.com inboxes can be read by anyone, and the homepage advises using made-up data. The provider also subjects these public addresses to throttling. These conditions make public receiving a poor place for test messages containing real personal or business information.
The terms allow Mailsac to block or delete mail without notice or reason, including data retained by paid users. They also provide no assurance about email retention or acceptance, and state that no customer has an SLA. This limits how much a team should rely on the service for tests that require predictable receipt or continued access.
API and SMTP traffic may be throttled even for paying customers. The terms therefore leave a reliability constraint beyond the public inboxes themselves. Operation counts reset on the first day of each month in UTC, and the provider says it emails customers at 80% of their operation limit and when they exceed it; service pauses after 125%.
Support routing can also depend on the plan: users without Business, Business+, or Enterprise are asked to post API integration questions to the forum, and support email questions may be redirected there. The terms say purchases are final and refunds are generally not given. Several details are missing; they are listed under What we could not confirm.
API access covers several testing workflows
The documented interfaces cover both automated retrieval and event-driven handling of test mail.
- The provider says its REST API can read test email in automated tests across programming languages and CI systems.
- Mailsac lists REST, WebSockets, and Webhooks for testing-pipeline integration.
- The documentation also describes routing mail to Slack and checking it through POP3.
- The provider lists SMTP, HTTP/JSON, WebHooks, and Web Sockets for sending and receiving private email.
- SAML single sign-on is listed for Business, Business+, and Enterprise plans.
- Enterprise materials offer access to security documentation, information assurance policies, and third-party audit results.
These options address different parts of a test workflow, from retrieving messages in code to routing them elsewhere. The provider also says its system uses security, encryption, and DevOps practices; those are vendor statements, not independent verification.
Private addresses suit controlled test data
Mailsac’s free offering may suit personal, non-business evaluation, which the terms say may require account registration. Business operations require a paid recurring commercial subscription, except for temporary evaluation trials.
Public receiving suits tests that use made-up data, since anyone can read those inboxes. For workflows needing team-readable custom test domains, the provider describes paid plans as the relevant option.
Custom forwarding requires reserving the address first, according to the provider. Treat that as a separate condition from public receiving when mapping a workflow; private addressing does not change the service terms on retention or receipt.
Compare email tools by privacy and access
A category comparison should distinguish public inboxes from private addresses, then check retention terms and whether outbound sending is supported. Also compare API access, per-user limits, and billing conditions; those determine whether a tool fits an isolated test or a shared team workflow.
What we could not confirm
- Available domains: complete domain list and usage conditions
- Inbox lifetime: message retention period or deletion schedule
- Outbound sending: availability, scope, and limits
- Per-user limits: address and usage allowances
- Private-mail retention: schedule for private addresses and custom domains
- Delivery behavior: handling of particular message types and domains
- Security scope: specific controls, encryption details, and audit coverage
- Evaluation trials: duration, eligibility, and usage terms
Questions about Mailsac’s public and private mail
Is a Mailsac inbox private?
A Mailsac public @mailsac.com inbox is not private: anyone can read it, and the homepage advises using made-up data. The provider describes private addresses and team-readable custom test domains as separate options, with custom domains associated with paid plans.
Does a free account include API access?
The provider says a free account includes an API key and one private address, alongside a monthly operation allowance. API keys are also described as a way for individual developers to use the API without account and billing logins.
What does Mailsac require for SSO?
Mailsac lists SAML single sign-on on Business, Business+, and Enterprise plans. The provider says users must be added by email address for SSO, so teams should account for that requirement when planning access.
When does custom forwarding apply?
Custom forwarding features require the address to be reserved first, according to the provider. The pricing page says operation counts reset on the first day of each month in UTC.
How does plan cancellation work?
The provider says customers can cancel from the Billing page, with the plan remaining active until the paid period ends. Month-to-month plans are billed by card and have a minimum commitment, according to the Enterprise page.
Which support route applies to API questions?
Users without Business, Business+, or Enterprise are asked to post API integration questions to the forum. The documentation directs feature discussions to its community forum and says the team tries to respond to forum requests within a day. The support page places responses during USA West Coast Pacific Time business hours.
Choose by privacy and reliability requirements
Probably not if continued message retention, acceptance, or an SLA is essential: the terms do not assure retention or receipt and state there is no SLA.
Main risk… teams may build tests around mail that can be blocked or deleted, while purchases are generally final.
Sources
Each fact above comes from one of these public pages; the date shows when it was read.
How this page was prepared
Editorial team of Account Academy. This page rests on the public sources listed above, which Account Academy checked on 2026-10-31. The service was not tested hands-on by the editors. Any change in the sources leads to an update here.
Last updated:
Right of reply
Do you represent Mailsac and see an error or outdated information here? Write to us with evidence. Once the correction is documented, we fix the entry or take it down. Entries are never removed or softened for payment.
- Our contact for replies
- No data available
- Response time
- No data available