Last updated: July 2026
Short answer
Use PoofMail for low-risk, short-lived email tasks. Do not use a temporary inbox for accounts, messages, or recovery flows where losing access would cause real harm.
What temporary inboxes are good for
- one-off downloads and low-risk signup confirmations;
- newsletter tests and inbox-clutter reduction;
- manual QA checks for email delivery;
- situations where the message does not need to be saved long term.
What temporary inboxes are not for
- banking, healthcare, legal, tax, school, work, or government accounts;
- password recovery, two-factor recovery, or identity verification you may need later;
- paid subscriptions, stored-payment accounts, or customer-support relationships;
- private documents, secrets, recovery codes, API keys, or long-term records.
Delivery limits
Some websites block temporary email domains. Some messages may be delayed, filtered, rejected, or unavailable after expiry. PoofMail should be treated as a convenience tool, not durable delivery infrastructure.
Privacy limits
Temporary inboxes are not secret vaults. During the current rollout, generated inbox reads use a browser-held read token, so keep the browser session open and do not share it. Do not send passwords, recovery codes, private documents, API keys, financial details, or sensitive personal information to a temporary address.
Current app status
PoofMail's app can generate addresses and refresh the D1-backed inbox on the production custom domains. Scheduled readiness smoke and operational contact forwarding are in place.
Use a durable inbox when stakes are high
If an account matters, use a secure email account you control, a password manager, strong two-factor authentication, and a recovery plan you can access later.