I operate Dayfly Mail, a free, receive-only temporary inbox for short-lived tasks. The public service receives text and HTML email. It does not send email, store attachments, or offer a public API or CLI for automated integration.
The browser workflow is small: choose a lifetime, create an inbox, read the message, and destroy the inbox when finished. No account or personal email address is required to create it.
Choose the access window before creating the inbox
The available lifetimes are 10 minutes, 1 hour, 24 hours and 3 days. The normal homepage defaults to 1 hour. You can use a random address or an available custom prefix.
There is no option to extend an existing inbox. Pick a lifetime that leaves time for the sender and the task; the chosen duration does not establish when an email will arrive. The mailbox lifetime guide explains what the countdown controls.
Expiry and cleanup are separate events
When the inbox expires, access ends. Scheduled cleanup removes expired records afterward. The countdown is an access deadline, rather than a promise that every stored copy is erased at that exact moment.
You can also manually destroy the inbox when you are finished. The public service has no recovery feature for expired or destroyed inboxes. Keep important account recovery on an address you can continue accessing.
What the public service supports
| Need | Dayfly Mail's public service |
|---|---|
| Read a text or HTML email in the browser | Supported |
| Choose an inbox lifetime before creation | Four choices; normal default is 1 hour |
| Destroy the inbox after a short task | Supported; no recovery afterward |
| Send or reply to email | Not supported |
| Store attachments | Not supported |
| Integrate through a public API or CLI | Not supported |
These limits describe the public Dayfly service. For a test suite that requires programmatic inbox access, use a setup with a supported automation interface.
Use it for a bounded task
A permitted one-off download, short confirmation or manual email check in an app you own or are authorized to test can fit this workflow. For your own app, the manual signup-email checklist separates the send request, actual arrival, message reading and verification action.
If a message is missing, start with the complete address, the current inbox and its remaining lifetime, then check the sender and whether the website accepts temporary email. The missing-email guide gives the steps.
Websites decide which addresses they accept. Use an address they permit when temporary email is rejected. For ongoing communication or password recovery, use an address you can keep accessing; an expiring inbox is unsuitable for an important long-term account. See the current FAQ for the service's features and limits.
Top comments (0)