OPC Mail vs TMailr
OPC Mail
opcmail.comTMailr
tmailr.comSide by side
| Figure | OPC Mail | TMailr |
|---|---|---|
| Price from | Free | $2/mo |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Web | Yes | Yes |
| iOS | Yes | — |
| API | — | Yes |
| Plans published | 1 | 6 |
| Spec score · Email Alias Services | 7.1 (#23) | 8.3 (#10) |
Plans
TMailr
- FreeFree
- Pro$2.99 a month
- API plan$9 a month
- Developer plan$9 a month
- Pay as you go$10, paid once
- Pro$24 a year
In their own words
OPC Mail
OPC Mail is an email alias service for a domain you own. After you point the domain’s MX records to Cloudflare in a one-time DNS change, any prefix at that domain works immediately, without creating aliases in advance. This lets one-person companies use separate addresses for service registrations, newsletters, online shopping, and beta testing or QA while keeping a main inbox organized. The service says it has no tracking or ads, does not sell user data, and does not use AI to read mail. OPC Mail describes itself as fully open source and links to its GitHub source code. It reports average delivery of 2–5 seconds using Cloudflare Edge and a global CDN. The Free plan costs nothing and includes unlimited aliases per domain. An iOS app checks the inbox; web access is also listed.
TMailr
TMailr combines receive-only temporary inboxes, masked forwarding aliases, email deliverability checks, and a developer sandbox on the web and through an API. Temporary inboxes use private links, receive mail only, and disappear when they expire. Free inboxes last 60 minutes by default, can be extended to 24 hours, and hold up to 50 messages; Pro inboxes are described as effectively unlimited and remain active while subscribed. Masked aliases forward messages to a real mailbox, can be paused or blocked separately, and keep the forwarding address out of TMailr pages and API responses. Deliverability tools include Gmail inbox tests, domain checks for MX, SPF, DMARC, MTA-STS, and TLS, plus header, address, and DMARC tools. Developers get test and live keys, JavaScript examples, polling, and signed webhooks. Incoming HTML is sanitized, remote images are blocked until requested, links show destinations, and attachments are virus-scanned; executable files are refused.