Thirtel

What Thirtel is

Most disposable mail sites leave you guessing whether "temporary" actually means anything. Thirtel runs on Cloudflare Workers with Workers KV storage: when the timer expires, the storage key expires with it. No archive, no trash recovery, no quiet backup copy of your inbox.

v1 is honest about scope. You receive mail; the service does not pretend you can send from the address. That constraint is not a gap — outbound mail from shared disposable domains cannot build sender reputation, so delivery fails silently or lands in spam. Receive-only is accurate rather than aspirational.

The default TTL is thirty minutes. Transactional email is a queue. A verification message can take two to five minutes to leave a sender's infrastructure under normal load, then travels through spam filters and delivery networks. Ten-minute inboxes regularly close before slow verification mail arrives. Thirty minutes absorbs that lag without the inbox lingering long enough to accumulate follow-up marketing.

The password generator and test identity tool are browser-side companions. Nothing generated by those tools is transmitted to Thirtel's servers. They exist because signups ask for more than just an email address — a password, often a name — and reaching for a separate untrusted site mid-flow is the wrong approach.

How it works

1. We issue a random receive-only address and start a thirty-minute countdown.
2. Inbound messages are stored in Workers KV with a matching expiration TTL set at write time.
3. Your browser polls for new mail every few seconds; plain text is default, HTML is sandboxed when you request it.
4. When the TTL ends, the keys expire. No traditional long-lived inbox database. No recovery path.

The address is randomly generated, not user-chosen — this reduces the risk of guessing or enumerating inboxes. A visible countdown shows remaining time. More on the infrastructure: temporary email hub and the complete guide.

Use it for — and not for

Good fits: one-time verification codes and sign-in links, free-trial access you plan to abandon, QA and automated test flows that need a working inbox for a few minutes, newsletters and download gates you do not want on your primary address. Pair every throwaway registration with the password generator — a reused password against a site you do not trust is a credential exposed at that site's next breach.

Bad fits: banking and investment accounts, government portals, healthcare records, employer or institutional SSO, paid subscriptions where receipts and licence keys matter, and any service where you might need to prove ownership months later. A disposable inbox that has expired cannot confirm your identity. The question to ask before registering: if I needed to recover this account in six months, would I still have this address? Read when not to use temporary email.

Companion tools

Registration forms ask for more than an email. Thirtel ships two browser-side helpers for the rest of the flow.

The password generator draws randomness from crypto.getRandomValues and produces a string of your chosen length and character classes. Nothing is uploaded. Use it to give every throwaway registration a unique credential — reuse is the real risk. A trial account registered with a shared password becomes a live credential against a service you do not control if that service is breached.

The test identity tool generates synthetic names, usernames, cities, and birth years for QA and form-testing flows. The data is generated entirely client-side. Not for fraud, not for bypassing real identity checks — for filling non-sensitive form fields during development walkthroughs without using real colleagues' data. The fake identity for signups guide covers what the tool is for and where it must not go.

Common questions