About InboxBurn

Privacy-first temporary email — built for everyone.

Our Mission

We believe privacy is a right, not a privilege. InboxBurn gives you a disposable inbox in seconds, with no registration and no data sold to third parties. Public pages show Google AdSense ads (see our Privacy Policy). We use privacy-safe aggregate analytics and never send inbox content or access tokens to analytics.

Why InboxBurn?

Many temp mail services are slow to load, cluttered, or unclear about what they log. We built InboxBurn to be fast, clean, and genuinely private — open API, multiple custom domains, and email forwarding included.

What we offer

  • ✓Instant inbox — no registration
  • ✓Custom email prefix
  • ✓Up to 3 simultaneous addresses
  • ✓Adjustable expiry (10 min – 7 days, default 24h)
  • ✓Email forwarding to your real inbox
  • ✓7 languages supported
  • ✓Open REST API with docs
  • ✓Privacy tools (password gen, breach checker, email validator)

Contact

Questions, bug reports or partnership enquiries:

[email protected]

InboxBurn is operated by InboxBurn Ltd.

How InboxBurn works and who runs it

Who InboxBurn is for

InboxBurn serves two groups with the same infrastructure. The first is anyone who wants to keep their main address private: you need to confirm a sign-up, download a document that sits behind an email form or try a service once, and you would rather not receive its marketing for years. The second is developers and QA teams who need real, working addresses in automated tests, for example to check that a registration email arrives, that a one-time code is correct or that a password-reset link works.

Both groups get the same thing: an address that genuinely receives mail from the internet and stays readable for a limited time.

What happens to a message, step by step

  1. You create an address on the home page or through the API. The server generates a random access token for that inbox, returns it to you and stores only a SHA-256 hash of it.
  2. A sender’s mail server looks up the MX records of the InboxBurn domain and delivers the message to our mail server over SMTP.
  3. The mail server hands the message to a parser. It checks that the recipient inbox exists, removes scripts, embedded frames, forms and event handlers from the HTML, scores the message for common phishing signals, drops oversized or executable attachments and scans the remaining attachments for malware.
  4. The message is saved and your open page is notified, so it appears without reloading. API users can poll, listen on a WebSocket or receive a signed webhook instead.
  5. Whoever presents the inbox token can read the inbox until it expires. The address alone does not reveal the messages.
  6. When the inbox expires, public access ends. Message bodies are moved to an archive that only administrators can open, and attachments are removed. There is currently no automatic deletion schedule for that archive, so expiry should not be understood as permanent erasure.

How the service is funded

The web inbox is free to use. Two sources pay for servers, domains and development: advertising and paid API plans. Public pages show Google AdSense ads, as described in the Privacy Policy. Developers and companies that need higher volumes, webhooks, forwarding or team features pay for an API plan; the plans and their limits are listed on the pricing page. Inbox contents and access tokens are not sent to analytics, and we do not sell inbox data to third parties.

Responsible use

A temporary address is a privacy tool, not a way to cause harm. Please do not use InboxBurn to:

  • create accounts in bulk to abuse free trials, referral programmes, votes or giveaways;
  • send spam, harass people or commit fraud;
  • receive anything you cannot afford to lose or that must stay confidential, such as banking, medical or account-recovery mail for important accounts;
  • test systems you do not own or are not authorised to test.

Limits that protect the service

Creating inboxes without an API key is limited per network, and sustained bursts trigger a temporary cooldown. Mail from specific senders can be rejected when it would make the service unusable for others, and messages that look like phishing are quarantined instead of displayed. These measures keep the shared domains working for everyone; developers who need higher volumes should use an API key, which replaces the per-network limits with a monthly quota.

Who operates InboxBurn and how to reach us

InboxBurn is operated by InboxBurn Ltd. Write to [email protected] for bug reports, security findings, abuse reports, partnership enquiries and questions about API plans; you can also use the feedback button on the site. When you report a problem, include the page or API endpoint, the approximate time and, for API errors, the request_id from the response. It lets us find the exact request without you sending inbox tokens, API keys or other secrets, which you should never include in a message.

Frequently Asked Questions