Contact

Two addresses; the right one gets a faster answer.

abuse@crazymailing.com when an address or a domain of ours has been turned on you, or on somebody else.

hello@crazymailing.com for everything else: a burned domain, a bug, a wrong fact in an article, advertising, press.

Neither of those can be taken over by a visitor, incidentally. The address generator refuses a list of names that receive mail about the domain itself: abuse, admin, administrator, billing, contact, dmarc, help, hello, hostmaster, info, legal, mail, mailer-daemon, no-reply, noc, noreply, partners, postmaster, press, root, sales, security, spam, support, sysadmin, webmaster. Without that list a stranger could claim the address printed on this page and read the mail people send us, which is a hole worth closing before it is found rather than after.

Reporting abuse

Send the full message with its complete headers, pasted as text.

A screenshot is the part that was easiest to forge, and the part that carries no evidence. The headers carry the delivery chain: each relay stamps its own Received line on top of the previous one, so the list reads bottom to top from origin to your mailbox, and the Authentication-Results line records whether SPF and DKIM passed at the receiving end. That is the material we can act on. If you have never opened them, the walkthrough here takes a few minutes and is worth doing once.

Two cases behave completely differently, and the headers are what tells them apart.

A message wearing one of our domains in the From line was forged somewhere else. Addresses issued here receive only. The service has no send path at all, not even a throttled one, so nothing you ever receive originated on our infrastructure. The Received chain will show the machine that actually injected the message, and an SPF failure against our domain is usually sitting right there in the results header.

Mail sent to one of our addresses is something we can act on. We can block a sender. If a pattern shows up across a domain, we can move that domain out of circulation early.

Include the recipient address, because domains are the unit we act on and we need to know which one you were using.

A domain that stopped working

Tell us which domain you used and which site rejected it.

A rejection almost always means the domain has reached a public blocklist, and that is not reversible by us. What it does tell us is that the domain is spent, which brings its retirement forward. Every mail domain carries a status, and retirement happens in two steps rather than one: a burning domain stops being offered for new addresses while continuing to accept mail on every address already created from it, so nobody loses a message mid-signup. Only later does it stop resolving altogether.

Nine public domains are in rotation while this is written. If one refuses to work, pick a different one from the front page before writing to us: it costs you ten seconds and it works, whereas the report only helps the next person. Registered accounts draw from a separate set that is never printed on any page, which reaches the lists considerably later. Why the lists exist and who compiles them is covered in the blocklist guide.

A bug or a mistake on a page

Four things in order: the steps you took, the result you were expecting, the result you got, and the browser you got it in.

Add the address you were using and the time to the nearest minute. That last part matters more here than on most services, because we cannot look you up afterwards: there are no access logs and no IP column anywhere in the database, so a report of "it broke yesterday" leaves us with nothing to search. A precise address and time we can match against a mailbox record while it still exists, which for a guest mailbox means within twenty four hours.

If a guide states something wrong, paste the offending sentence back to us. Claims about the service get checked against the running code before anything is edited, so an exact quotation reaches a decision in minutes while a general objection turns into a hunt through twenty eight pages.

What we cannot do

Bring back a mailbox or a message once it is gone. No archive exists and no backup either, so there is no source to recover from, regardless of who asks or why. Expiry is a real deletion: the sweeper removes the database rows in batches, the attached files leave object storage in the same pass, and the cascade takes messages away with the mailbox and attachments away with the message. Nothing gets flagged as deleted and quietly kept.

Tell you who used an address. We do not store IP addresses and keep no access logs, so there is nothing to hand over. We also will not open a mailbox that is not yours, including one belonging to someone who wronged you, and that answer does not change with the sympathy of the story.

Pull a domain back off a blocklist we do not own. Those lists are other people's property, maintained by people whose entire job is finding domains like ours. A delisting request from a disposable mail service goes nowhere, for reasons that are not hard to guess, and nobody would notify us if one somehow succeeded.

Make a website accept a throwaway address. That is the site's decision, taken with a check that is working exactly as designed. What we can do is explain how the check works so the refusal stops being mysterious.

Deliver a message that was never sent. A sender that refuses disposable domains usually declines silently. Nothing arrives at our servers, nothing appears in your inbox, and from your side it is indistinguishable from a slow service. There is no queue for us to inspect and no delay for us to shorten.

Release a reserved name. The list above is not negotiable, including for people who want it for a good reason.

Before you write

A large share of the mail we get already has an answer on this site, usually a more complete one than a reply would be. The disclaimer covers the five complaints that account for nearly everything: the rejected address, the message that never arrived, the mailbox someone else opened, the account lost to an expired address, and the scam that turned up in an inbox. If your question is one of those five, start there.

How fast we reply

A person reads every message. Abuse reports jump the queue and usually get an answer the same day; the rest takes several working days.

There is no automatic acknowledgement, and its absence is deliberate rather than an oversight: an auto-reply sent to a forged sender address is a small favour to whoever forged it, and a confirmation that a human mailbox is behind the address. If a week passes without a word from us, treat the message as lost in transit and send it once more.

One thing worth adding, because it comes up: mail you send us lands in an ordinary permanent mailbox, not in one of these. It is read by the same people who decide which domain gets retired next, and it is kept for as long as the matter needs. Corrections are welcome in particular. We would rather change a wrong sentence than defend it against the person who caught it, and several paragraphs across the guides exist in their current form because a reader pushed back on the previous one.