Frequently asked questions

A temporary email address is a short-lived inbox you can use instead of your real address. You create it in the browser, receive mail in it, and it expires automatically. It is useful for one-off signups, verification codes and testing, because it keeps your primary inbox off marketing lists.

Open the homepage and an address is generated for you automatically. Press "New address" for a different one, pick a domain from the selector, or type your own prefix and press Use. Nothing needs to be installed and no account is required.

Yes. Creating addresses and receiving mail is free and does not require an account or a payment method.

No. There is no signup, no email confirmation and no password. An inbox is created instantly and you are given its access token, which is the only thing needed to reopen it.

Yes, when the sending site accepts the domain. Many sites check whether an address looks disposable and refuse it — that is the site's decision, not a delivery failure. When mail does arrive, any verification code we detect is shown in the message list so you can copy it with one click.

Yes. Type a prefix in the Custom prefix field and press "Use this address". Prefixes must be between 3 and 64 characters, use letters, numbers, dots, hyphens or underscores, and must not impersonate reserved names such as admin or postmaster. If the name is already taken you will be told immediately.

Yes, if the deployment offers more than one domain. The domain selector sits directly after the prefix field, so the address reads left to right as prefix@domain. A domain is only useful once its MX records point at this service; the selector labels one "MX pending" only when our own check has confirmed the MX is not yet in place.

Yes. Press "New address" at any time. The previous address stays valid until it expires, so you can switch back to it from your recent inboxes list.

Each inbox has a visible countdown. The default lifetime is 90 minutes and can be extended from the inbox toolbar, up to the deployment's maximum. Messages are removed on their own expiry even if the inbox is still active.

Attachment metadata is always recorded, including filename, type and size. Whether the file itself can be downloaded depends on whether the deployment has object storage configured. The message reader states clearly when only metadata was kept.

Yes, using the inbox link. The link contains the inbox access token, so treat it exactly like a password: anyone who has the link can read that inbox. Use "Copy inbox link" on the device you created it on.

The most common causes are a mistyped address, a sending site that silently blocks disposable domains, or a delay in the sender's own queue. Check the address character by character, press Refresh, and wait a few minutes. If the sender refuses disposable domains, no temporary service will work for that site.

The inbox and its messages are deleted. You cannot recover them. If you need the same address again you must create it again, and any site that already stored it will not know it is new.

No. Deleting a message removes it immediately and there is no trash folder or restore path. That is deliberate: retention is bounded by design.

Not by default in the disposable-email world, and this service is built differently on purpose. A private inbox here requires its access token. However, if you deliberately create a public share link, anyone holding that link can read the inbox — the interface warns you when it is public.

Only if they obtain your inbox token or a public link you created. Guessing an address is not enough to read a private inbox. This is the main difference from services that let anyone open any inbox by typing its address.

No. Do not use a temporary address for banking, payments, financial accounts, password recovery, government or medical records, or anything you would not want a stranger to read. Use it for low-risk signups and testing only.

Sites block disposable domains to reduce fake accounts, trial abuse and spam. They usually check a published list of disposable domains or compare the domain against known providers. Respecting that is part of using the service fairly — do not use it to circumvent a site's stated signup policy.

For low-risk accounts, yes, and it is a reasonable way to keep marketing mail away from your real inbox. For anything important — or anything you expect to need recovery access to later — use a permanent address you control.

Yes, and this is one of the strongest use cases. The REST API lets a test create an inbox, read messages and clean up, so verification flows can be exercised end to end without touching a real mailbox. See the API page for endpoints and authentication.

Yes. The API exposes inbox creation, message listing and reading, deletion, extension and public-link management under /api/v1. Inbox operations authenticate with the inbox token as a bearer credential.