33Mail vs TMailr

33Mail creates private email aliases and forwards messages sent to them to an existing email address. An alias is created automatically when email first arrives, and users can block an alias to stop receiving its messages. With anonymous replies enabled, users can reply to forwarded mail through 33Mail; the service removes header information relating to their actual email address. Premium accounts can use a custom domain by pointing its MX record to 33Mail. The service is web-based and also lists a browser extension. Lite is free and includes 10MB monthly bandwidth, with alias creation limited to five per 30-minute period. Premium costs $1 a month and includes 50MB monthly bandwidth, 20 anonymous replies per day, one custom domain, and one additional username. Pro costs $5 a month; Enterprise costs $50 a month. Attachments up to 10MB count toward bandwidth, which is measured over a rolling 30-day window. 33Mail says it warns users who exceed their bandwidth limit and treats dropping emails as a last resort. Its terms say user data is used to provide the service and is not shared with third parties except as needed for law enforcement requests. Brothers Ian and Andrew Clarke conceived the service, which forwarded its first email in August 2010.

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.