Temporary email for testing sign-ups and notifications
Developer and QA workflows need a real inbox that is not tied to a person. QuickInbox receives actual SMTP mail at a generated address, renders HTML in a sandboxed iframe, and wipes the data when the inbox expires — ideal for exercising registration, verification and notification flows.
What you can test with it
- Sign-up confirmation emails: trigger the flow, open the message, follow the link.
- One-time codes: read the OTP from the text part without touching a personal mailbox.
- HTML templates: inspect rendering with remote images blocked by default (toggle them on to verify layout).
- Multiple parallel flows: each browser session gets its own isolated inbox with its own session cookie.
- Expiry behaviour: verify your product handles a bounced or dead address gracefully.
Why a real receiving path matters
Mocking an inbox in tests only proves your mock works. QuickInbox accepts mail through a real provider route with signed webhooks, so the message you read is the message your mail server actually delivered — including headers, subject encoding and spam filtering side effects.
Messages are idempotent: if the provider retries a webhook, the same message is stored once, mirroring how a production inbox behaves.
Safety built into the viewer
- HTML is sanitized before storage: scripts, frames, forms and event handlers are stripped.
- The viewer renders content in an iframe with scripts, form submission and top navigation disabled.
- Remote images stay off until you explicitly allow them, so tracking pixels do not fire during routine tests.
- Inboxes expire quickly, so test data does not linger.
Limits to be aware of
The first version stores text and HTML only — attachments are dropped. Inboxes last 10 minutes by default, so generate the address right before running the flow. Some services block disposable domains; those tests need a different sending domain.