Custom Temporary Email Address

Choose the part before the @ and the domain it lives on, and understand the one privacy trade-off that comes with a memorable address.

Updated

Create Temporary Email Now →

Why choose your own address

Randomly generated addresses are the safest default, but there are good reasons to pick a name. A support agent may need to read the address back over the phone. A QA engineer may want addresses that identify the test run, such as checkout-run-142. Someone signing up for several trials in one afternoon may prefer prefixes that say which service each inbox was for. And a few sign-up forms reject usernames that look machine-generated.

On InboxBurn you can open the custom address panel next to the current address, type a prefix, pick one of the available receiving domains and create the inbox. It behaves like any other inbox: you choose its lifetime, it gets its own private token, and it occupies one of the three address tabs.

Naming rules

  • Prefixes are converted to lowercase.
  • Allowed characters are a to z, 0 to 9, dot, underscore, plus and hyphen. Other characters are removed rather than rejected, so check the final address before you use it.
  • The prefix is limited to 64 characters, which is also the limit for the local part in the email standards.
  • The domain must be one of InboxBurn's active receiving domains.
  • If the same address is currently active for someone else, creation fails with a conflict and you need to choose another name.

The trade-off: names can be reused after expiry

A custom address is unique only while its inbox is active. When it expires, the name becomes available again, and anyone can create an inbox with the same prefix on the same domain. They would not see your old messages, because messages belong to the expired session and access is tied to a token they do not have. But they would receive anything sent to that address from then on.

This matters if a service keeps sending mail to the address. Imagine you used alex.trial@ on some domain for a free trial, the inbox expired, and months later somebody else creates the same address and clicks 'forgot password' on that service. The reset mail goes to them. Random addresses make this practically impossible; memorable ones make it easy.

Use custom prefixes for throwaway sign-ups and test runs, not for any account you might return to. If you must use a readable name, add a random suffix such as alex.trial.7q4m so it cannot be guessed.

What the address does not protect

Knowing an address is never enough to read its inbox on InboxBurn while it is active; reading requires the token issued when it was created. But an address is not a secret either. Senders, the sites you give it to and anyone who sees your screen will know it, and anyone can send mail to it. Do not choose a prefix that contains your full name, employer or a password hint. A custom address is a label, not an identity.

Choosing a domain

Some websites block particular disposable domains. The domain picker lists every receiving domain that is currently active, and healthy domains with low measured delivery latency are listed first. If a sign-up form refuses one domain, keep your prefix and try another. If every domain is refused, the site has decided not to accept temporary addresses at all.

Plus signs in the prefix are stored as part of the address. Unlike some personal mail providers, InboxBurn does not treat alex+shop and alex as the same inbox; each is a separate address that has to be created on its own.

Creating custom inboxes through the API

Test suites often want predictable addresses so that logs and screenshots are easy to read. The custom endpoint takes a prefix, a domain and an optional lifetime in milliseconds (minimum 10 minutes, maximum 7 days, default 24 hours). The response contains the final address, the domain, the private token and the expiry time. A 409 response means that exact address is already active. Always include something unique, such as a CI run ID, so parallel jobs never collide.

Create a custom inbox (curl)bash
# List active receiving domains
curl -s https://api.inboxburn.com/api/domains

# Create checkout-run-142@<domain> for one hour
curl -s -X POST https://api.inboxburn.com/api/generate/custom \
  -H "Authorization: Bearer $INBOXBURN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"prefix":"checkout-run-142","domain":"<domain from the list>","expiry":3600000}'

# => {"address":"checkout-run-142@...","domain":"...","token":"...","expires_at":"..."}
Read the inbox with its tokenbash
curl -s "https://api.inboxburn.com/api/inbox/checkout-run-142@<domain>" \
  -H "X-Inbox-Token: $INBOX_TOKEN"

Good patterns

  • Prefix per purpose: newsletter-oct, beta-waitlist, conference-slides.
  • Prefix per test run: signup-<ci run id>-<worker index>.
  • Short lifetime for anything you will not revisit, so the name stops receiving mail soon.
  • Store the token where you can find it again (the browser history list does this for you), because an inbox without its token cannot be read.

Features

✓Choose the prefix and the receiving domain
✓Lowercase letters, digits, dot, underscore, plus and hyphen
✓Same lifetimes as random inboxes: 10 minutes to 7 days
✓Private token per inbox, even for readable names
✓Conflict check while an address is active
✓Available in the web app and through the API

Ready to try?

Create a private temporary inbox in under a second. No registration needed.

Get Started — It's Free →

Frequently Asked Questions