Contact

Two mailboxes are published on this page, and choosing between them matters more than anything you put in the message. One is opened first thing every morning. The other is worked through in order.

abuse@tempmailgenerator.net when an address on one of our domains, or a key issued through this site, has been aimed at you or at someone you look after.

hello@tempmailgenerator.net for a domain a form refused, a page that broke, a question about the API, a sentence in a guide that is wrong, advertising and press.

Neither of those is a generated address. Both sit on the domain we use for outbound mail, so they do not expire, nothing in them is swept by the cleanup job, and a reply thread stays readable a month later.

Abuse: what turns a report into an action

Send the message as text, with the full headers included. What you can see in a mail client is the half a forger controls for free; the headers carry the route the message actually took, the server that handed it to Cloudflare and a timestamp at every hop. Those are the only fields we can match against anything on our side.

A screenshot is fine as a supplement and useless on its own. It shows us the sender line somebody typed, which is not evidence of where the mail came from, and it cannot be searched against a recipient.

When the report checks out, the tools available to us are narrow but immediate. An inbox can be destroyed along with everything in it. A domain can be moved to the burning state, which stops it being handed to anyone new while it keeps accepting mail for addresses that already exist, so nobody in the middle of a signup loses their code. A key can be revoked, which kills every request signed with it inside a second and orphans the inboxes it created. And a domain can be retired ahead of the schedule it was on.

One thing not to send us is the attachment itself. Executable file types are refused at the door before a message ever reaches the database, thirty five extensions are on that list, and a file over five megabytes is dropped while the message it rode in on still gets delivered. Describe the file, quote its name, and leave the bytes where they are.

Mail that claims to come from us

Nothing on this service is capable of sending. There is no submission path, no relay, no forwarding rule and no outbound queue attached to any generated address, in any version of the site. A message whose sender line ends in one of our domains was composed somewhere else with that line filled in by hand.

Send it anyway, with the headers. Forgeries are worth reading because the receiving path in them tells us which domain of ours is being borrowed as a disguise, and that is a reason to retire it early rather than wait for the blocklists.

A domain a form refused

Tell us the domain you were given and the site that rejected it. That pairing is the useful part: it tells us the domain has reached somebody's disposable list and shortens its remaining life for everyone, which is exactly the signal the rotation runs on.

What it does not do is change the answer you got. We have no standing with the site that refused you and no way to make an exception on their side. The practical fix takes one click: generate again and you land on a different domain from the pool. If refusals keep coming, an account opens up a set of domains that appear nowhere on this website at all, and a name nobody can sample stays unrecognised for months instead of weeks. That is most of what registering is for.

API keys and integrations

Key problems come to the general address and they split into two kinds.

A lost key is not recoverable by anyone, including us. Only a hash of it is stored, and the last six characters are kept so you can tell one key from another in your own notes. Issue a new one in your account, which revokes the old one in the same operation, and update the secret in whatever was using it.

A key that stopped working somewhere it used to work is worth writing about. Include the last six characters, the endpoint, the error code from the response body and roughly when it started. The error codes are stable strings and they narrow the problem immediately: unauthorized means the header never arrived in the shape we accept, rate-limited means a counter tripped, limit-reached means a hundred live inboxes are already open on that key and nothing was deleted, and not-found on an inbox usually means it passed its twenty four hours rather than that it never existed. The full reference is on the API page, and the reasoning behind each ceiling is in why the API has the limits it has.

Bugs and wrong sentences

For a bug, four lines are enough: what you did, what you expected, what appeared instead, and the browser. If mail stopped arriving, add the address and the approximate minute, because the receiving path is timestamped at three points and a minute is enough to find the right one.

For a factual mistake in a guide, quote the sentence. These pages describe running code, most of the numbers in them come out of that code, and a wrong one is a defect we would rather repair than argue about. Corrections have changed pages here more than once.

Requests we have to refuse

Recovering deleted mail. There is nothing to recover from. The cleanup pass runs every ten minutes and deletes rows rather than flagging them, attachments go out of object storage in the same sweep, and no backup of either exists anywhere. An inbox that has expired is gone in the strong sense of the word.

Opening an inbox that is not yours. We do not read mailboxes on request, and the request cannot be answered indirectly either: no access log ties a person to an address, and the only address-derived data we hold is a counter in process memory that is discarded when the process restarts.

Getting a domain off somebody else's list. Those lists are maintained by other companies, the entries about our domains are correct, and an appeal from the operator of a disposable mail service is the least persuasive message such a list will receive that week.

Telling you who used an address. A guest inbox has no owner recorded against it, which is the entire point of the design. There is no name behind the string to disclose.

How long a reply takes

Every message is read by a human being; none of this is triaged by software. Abuse jumps the queue and normally gets an answer before the day is out. The rest sits for two or three working days, and longer over a holiday. Nothing here sends an automated receipt, so silence carries no information at all about whether your message landed. After a week, treat it as lost and write again rather than wait.

Before writing about mail that has not shown up, check what the sending side may have decided and give it two minutes. A silent refusal by the sender looks identical to a slow one, and generating a fresh address is usually faster than waiting for either of us to work it out.