SableMail public inbox
A free, receive-only inbox for staging emails, signup demos and synthetic QA. Open an address immediately. No login or account needed.
Public inbox: anyone with its name can read it. Use synthetic data only. Data & deletion details.
How to use
Choose a name or use Random Inbox. Send a test email to its @sablemail.in address, then inspect received messages here. Refreshes every 12 seconds; delivery can vary.
Public access
Names are reusable and messages are public. A random name does not make an inbox private. Messages follow a 24-hour retention policy with daily cleanup. Avoid passwords, recovery links and personal data.
Run your first test
- Choose a run address. Use Random Inbox or generate an address in the worksheet below. Names are reusable and are not reserved to you.
- Trigger a staging email. Use the complete address in your own test application. Keep all account data synthetic.
- Inspect the result. Check the exact recipient, sender, subject and expected code or staging URL. If delivery fails, verify the sender logs and the address; an empty inbox does not prove an email was sent.
- Record the outcome. Exercise your application's verification, expiry and resend behavior, then export the worksheet for your test notes.
SableMail does not send mail, verify the identity of a sender, or reproduce every mail client. For private accounts use a private mailbox or forwarding alias. Compare the options.
Email QA worksheet
Plan a staging email test and record the result
Use a synthetic account in an application you control. Generate a run address, send your staging verification message, and record each result below. This worksheet does not send emails or run security checks for you.
qa-example-run@sablemail.inOpen test inbox in new tab| Case | Expected result | Your result |
|---|---|---|
| Signup | One confirmation message; recipient and staging link match the test account. | |
| Verification | Valid code/link succeeds once; repeating it fails. | |
| Wrong code | An incorrect code fails without verifying the account. | |
| Expiry | After your application's expiry window, the code/link fails. | |
| Resend | Resend follows your application's documented invalidation rule. | |
| Formatting | Sender, subject, plain text and HTML communicate the same action. |
Every inbox is public, including randomly named inboxes. Delivery is not guaranteed. This preview does not establish Gmail/Outlook rendering or sender authentication; check those separately in private test mailboxes.
Guides and examples
Solve the next email testing problem
View all guides ?Updated 2026-10-07
What Is a Temporary Email Address and When Should You Use One?
Learn what temporary email addresses are, how they work, and the most common situations where using one can protect your privacy.
Read guide ?Updated 2026-10-07
How to Test Email Verification with SableMail in Staging
Run a controlled staging signup with synthetic data, then record wrong codes, expiry, resends, replay, and recipient isolation in a reusable test matrix.
Read guide ?Updated 2026-10-07
How to Protect Your Real Inbox from Spam and Marketing Emails
Practical strategies for keeping your personal email address clean, including when and how to use a temporary inbox to avoid unwanted marketing.
Read guide ?Updated 2026-10-07
Best Practices for QA Testing Email Workflows in 2026
An in-depth guide for software teams on how to test transactional emails, signup confirmations, OTP messages, password resets, and customer notifications more reliably.
Read guide ?Updated 2026-10-07
Digital Privacy: Reduce Email Exposure to Data Brokers
Understand how your email address acts as a long-term online identifier and learn practical ways to reduce tracking, spam, profiling, and unwanted data sharing.
Read guide ?Updated 2026-10-07
How to Inspect Suspicious Emails in a Public Inbox
Inspect fictional sender and URL examples, handle unexpected OTPs, and report public inbox abuse without exposing verification secrets.
Read guide ?Before opening an inbox
Do I need to create an account?
No. Type any inbox name, open it, and use the generated @sablemail.in address wherever you need a temporary inbox.
Can QA teams use SableMail for email testing?
Yes. It works well for non-sensitive testing of signup emails, OTPs, notification emails, verification links, and demo flows.
Are SableMail inboxes private?
No. Inboxes are public and temporary. Do not use them for private, sensitive, financial, legal, medical, or password recovery messages.
How long should I rely on a SableMail inbox?
Messages follow a 24-hour retention policy with automatic daily AWS cleanup. Use it for short-lived workflows and synthetic data only.
Report a delivery problem or suggest a guide
Share the steps and approximate time using synthetic test data. Do not send passwords or private email contents.