Temporary email for transactional email testing
Updated 5 November 2026.
Manually inspect receipts, booking confirmations and status emails from an application you own, using sandbox events and dummy orders.
Generate a sandbox event, not a real purchase
Use your application’s approved development or staging environment and the payment provider’s test mode where appropriate. Set the temporary address as the recipient on the test customer record. Trigger a known test event and note the order or event identifier. An inbox does not turn a live checkout into a sandbox or remove charges.
Check the details the customer would rely on
Compare the message with the underlying dummy order: item names, quantity, total, currency, tax treatment shown by your application, status and reference number. Check that links lead to the intended staging site rather than an unexpected live destination. For a booking, also inspect the time and timezone shown. Delivery of a message does not validate the correctness of those business values.
Inspect more than the attractive HTML version
Compare plain text and formatted mail, inspect a supported attachment if one was expected, and download the original .eml for encoding or header investigation. An image blocked by default is not necessarily a failed attachment. See saving files and original messages for the differences.
Test duplicates and retries in your own application
Use controlled events to check whether retries cause unwanted duplicate notifications. Keep a unique identifier per run and compare it against your application’s logs. An inbox showing two emails does not explain whether the event was emitted twice, a mail job retried or a template was sent through two paths. Diagnose that in the system you control.
Know the boundary of a manual inbox test
1hemail provides manual receiving and has no supported public automation API. It does not certify delivery to every mailbox provider or check your entire purchase flow. For CI/CD workflows, Mailinator’s official guide describes an API-based approach. Evaluate the provider’s current permissions and limits before integration.
Keep test evidence safely
Save only dummy data, redact access links from shared reports and finish before inbox expiry. Do not register a real customer’s billing address with a disposable inbox. For ongoing automated monitoring or accounting records, use a lasting mailbox and your application’s own logging. The password reset testing guide covers a different workflow involving private reset tokens.