Temp Mail Generator

Your address is ready

The address sitting at the top of this page came into existence as the page loaded, and mail sent to it will already be accepted. Copy it, drop it into whichever form demanded an email, and whatever arrives shows up below without being asked for.

No account, no password, nothing to install. Prefer to pick the name yourself? Type one over the top before you use the address.

What the generator just did

Two things, in this order. It picked a name, either at random or the one you typed, and it attached a domain from the pool this site keeps in rotation.

Nothing was created in advance. There is no warehouse of ready-made addresses sitting somewhere waiting to be handed out: the address became real at the moment it was assigned to you, and the mailbox behind it was created in the same instant. That is why the process takes no time and why an address you discard costs nothing to replace.

The domain matters more than the name. The part before the at sign is yours to choose and affects almost nothing; the part after it decides whether a signup form will accept the address at all.

Mail arrives without refreshing

Nothing on this page interrogates the server about new mail. One connection stays open from the moment the address appears, and delivery travels down it unprompted, which is why the wait for a code here is measured in seconds rather than in refresh cycles.

A message is stripped before it is shown: scripts out, embedded content out, anything that would call home out. What survives is drawn in a frame walled off from the rest of the page. That is not caution for its own sake, since a routine newsletter carries enough machinery to report back that you opened it. Files travel separately and unlock with an account.

How long the address stays alive

A guest mailbox survives one day past the moment you last opened it, and generating a replacement destroys the old one at once. Not at midnight, not in an hour: at that instant, along with everything inside it.

Registering rewrites those numbers upward: a week measured from your last sign in, a month as the ceiling for any one message, files tied to the life of the message that brought them. What registering does not do is make anything recoverable. There is no archive to search, no backup to restore from, and no support procedure that reaches a mailbox after the cleanup has passed over it.

Two consequences worth knowing. Nothing guards a guest mailbox except the string itself, so whoever learns or guesses the address reads what lands in it. And an expired address returns to circulation, which means the name you used today may belong to somebody else next month.

One address per form

Here is the habit this site is built around, and it runs against what most people do: generate a new address for every form instead of protecting one.

The reasoning is mechanical rather than moral. Reuse one address across five signups and all five senders share a single inbox, so you cannot tell which of them leaked you, cannot stop one without affecting the rest, and lose all five the moment that address expires or gets blocked. Five separate addresses cost five clicks and give you five independent switches.

It also changes what a blocked domain means. If one form refuses the address, you generate another on a different domain and continue, instead of losing a mailbox that half a dozen other things depended on.

What signing up changes

Registration costs nothing and unlocks four things. There is no paid tier above it and none is planned.

You get domains that never appear on this page, and an unpublished domain survives longer before a signup form starts refusing it. You get ten mailboxes running at once rather than one, which is what makes the address-per-form habit practical. You get attachments. And your mailboxes stop being open to anyone who knows the address.

The last of those is the only one that changes the nature of the service rather than its convenience.

Receiving only, and an API with a fence around it

Addresses created here cannot send mail, and that will not change. Let anonymous visitors send and the service turns into a spam relay inside a week; the domains are refused everywhere shortly afterwards, and the receiving half dies alongside them.

Automating the receiving half is a different question, and the answer is yes. There is a public interface, the documentation and the endpoint reference live on the API page, and the key is issued in your account with a single button. What keeps it from spending the supply everyone else depends on is a fence built into the design rather than a price list. It hands out addresses on a set of domains reserved for it, which no visitor to this page is ever offered, so the burning happens where it was budgeted for. A key may create three hundred inboxes an hour, read six hundred times a minute and hold a hundred alive at once. Every inbox it makes expires twenty four hours later regardless of how busy the loop reading it has been.

Two things it gives you that a browser cannot: messages pushed down an open connection instead of a polling loop, and an endpoint that waits for the message and hands back the confirmation code already extracted. Every limit above has a specific reason, and this page argued for years that no such interface should exist at all, so the reversal is written out in full, mistakes included.

One domain sits outside all of this. The name this website runs on is not offered by default, because it is the first string anyone tests and therefore burns out ahead of the rest.

Where the address goes after you paste it

The generated address stops being your business the moment you submit the form, and most of what happens next is invisible from your side. It is also the part worth understanding, because that is where the decisions about you get made.

Four checks run between the button and the words "check your email", and three of them settle your case before any message is sent. If a form refuses an address that looks perfectly valid, the reason is usually in what counts as valid to that particular form rather than in the address itself. And once you are past the form, a single signup typically writes your address into four or five systems at once, which is why changing it in one place changes so little.

One boundary before you start. Anything that might one day need to send you a way back in - a bank, a tax portal, an employer, a courier, a registrar, a drive holding your files - should never see an address from this page. The address a recovery link arrives at must still exist on the day you need it, and this one is engineered to have stopped existing well before then.