Product features
What the inbox actually does
A private address for a signup or a code. The message shows up while you wait, the code is ready to copy, and the inbox ends when you say so. No account for the free one.
Instant address
Open Quick Inbox and copy a working mailby.app address. No account for the free inbox.
The address is tied to this browser immediately. Paste it into a signup, a code challenge, or a download gate.
- Random or custom local-part
- No signup for Free
- Session-bound from second one
Outcome A private address you can use right away.
Open free inbox →Live delivery
The message appears in the open inbox. You do not refresh and hope.
New mail shows up while the other tab is still waiting on you. If the connection drops, the inbox catches up on its own.
- SSE + poll fallback
- List and detail stay in sync
- Built for OTP timing pressure
Outcome Catch the code while the timer is still running.
OTP & link extract
The code and the useful link sit next to the message.
You copy the OTP without hunting through a footer. Developer plans can wait for that same code from a test.
- OTP codes ready to copy
- Action links over footer noise
- CI waits on Developer plans
Outcome Less scanning, faster verification.
Safe HTML reader
You can read the message without loading the sender’s tracking pixels.
The preview is cleaned and sandboxed. Remote images stay off unless you choose otherwise, so opening the mail does not phone home.
- Allowlisted HTML
- Sandboxed iframe
- Remote content blocked by default
Outcome See the message, not the surveillance.
Security & trust →Lifecycle controls
Extend the inbox if the site is slow. Delete it when you are finished.
Free mail can arrive for about an hour, then it is removed. Each free message can be up to 5 MB, attachments included. Premium keeps mail longer and accepts up to 25 MB. Delete ends access immediately instead of waiting for the clock.
- Extend receive when needed
- 5 MB free, 25 MB on Premium
- Hard delete revokes access
Outcome Temporary means temporary — on your terms.
Data retention →Recovery secret
Move the inbox to another device with a secret you paste. It is never put in the link.
The address in a screenshot is not enough to open the mail. Recovery is a secret you copy on purpose, not a URL that leaks into chat or analytics.
- Secret never in the URL
- Cross-device when you choose
- Address alone is not enough
Outcome Portable access without sticky links.
Recover an inbox →Receive-only plane
Mailby accepts mail. It does not send mail for other people.
Someone who knows the address can write to it. They cannot open it. After you delete the inbox, that address is not reused.
- No public SMTP AUTH
- Policy at RCPT
- Tombstones block reuse
Outcome Receive mail. Do not become a relay.
How it works →Developer path
Create an inbox in a test, wait for the mail, and read the code.
The API returns when the message arrives. Webhooks are signed. Local SMTP capture stays on your machine and only accepts mail for inboxes you created.
- API wait + OTP helpers
- Signed webhooks
- Local SMTP capture
Outcome Reliable email tests in CI and staging.
Developer docs →Straight answers
Features FAQ
- Do I need an account to use Mailby features?
- Quick Inbox works without an account. Sign up when you want longer retention, billing, or Developer API access.
- Can someone read my inbox if they know the address?
- No. Delivery and read access are separate. Only your session — or a recovery secret you hold — can open messages.
- How is this different from a shared temp-mail dump?
- Mailby binds inboxes to sessions, sanitizes previews, expires content on a clock, and never treats the public address as a password.
Related: How it works · Security & trust · Developers
Try it on a real OTP next
Open a free disposable inbox, paste the mailby.app address, and watch the code arrive. Account optional until you need longer retention or an API.
Summary
What is it?
Mailby temporary email features cover disposable inbox allocation, live delivery, OTP extraction, safe HTML reading, lifecycle clocks, recovery secrets, receive-only MX, and a developer email testing API.
How does it work?
Each feature is explained so you can evaluate temp mail security, OTP inbox behavior, and CI email testing tools before opening an inbox.
Why use Mailby?
Clear feature pages help buyers, search engines, and LLMs cite what Mailby disposable email actually does.
Key takeaways
- Instant disposable inbox on mailby.app
- OTP extraction and live temp mail delivery
- Receive-only plane with session authorization
- Temp mail API path for developers
FAQ
- Do I need an account to use Mailby features?
- Quick Inbox works without an account. Sign up when you want longer retention, billing, or Developer API access.
- Can someone read my inbox if they know the address?
- No. Delivery and read access are separate. Only your session — or a recovery secret you hold — can open messages.
- How is this different from a shared temp-mail dump?
- Mailby binds inboxes to sessions, sanitizes previews, expires content on a clock, and never treats the public address as a password.