Confirm delivery
Refresh the list to confirm that an email reached the inbox and see its actual arrival time. When testing verification codes, account confirmations, or notification jobs, there is no need to search through your personal inbox.
Email sandboxTest email
Test email
and email preview tool
Manage isolated addresses, live delivery, and full message inspection from one workspace.
Login verification codeAccount security · Just nowHTML
Release announcementProduct update · 2 minutes agoNotification
Please review PR #184Code collaboration · 5 minutes agoDevelopment
Confirm your test accountSignup flow · 8 minutes agoVerification code
Weekly delivery summaryEmail quality · 12 minutes agoReport
Receiving emailsRemaining --:--:--
Zoom login verification code: 482731
Zoom
Confirm this sign-in
Someone is trying to sign in to your account on Chrome (macOS), from approximately Paris, France.
482 731
Valid for 10 minutes. If you did not initiate this, do not share the verification code.
Review sign-in activityThis is an inbox demo and does not count toward your real email total.
Please review PR #184: Fix recovery email expiry
GitHub
mira-dev requested your code review
northstar-labs/inbox-kit · PR #184
Fix recovery email expiry
fix/expiry-clock mainThis change keeps the recovery email countdown accurate after local restoration.
View pull requestThis is an inbox demo and does not count toward your real email total.
Look at the essentials first
A test email is more than just “delivered”
An email sandbox puts delivery status, sender, subject, plain text, and HTML content in one inspection flow, keeping issues in the test environment instead of your real inbox.
Read the full message
Select an email to view its full content instead of a truncated preview. Real HTML emails are isolated in a restricted reader so page styles cannot interfere with the original layout.
Keep testing isolated
Disposable addresses separate trials, automated tests, and messages from unknown sources from your personal identity. When a task is complete, switch to a new address and start the next test with a clean context.
Common tasks
Put email testing back in context
One test email workspace covers short-term verification, template checks, product integration testing, and low-risk trials, keeping addresses and messages organized around the current task.
Check that welcome emails, confirmation links, and first-login codes arrive as expected.
Inspect whether headings, body structure, buttons, and plain-text fallbacks remain complete and readable.
Give your test environment an independent inbox and keep scripts out of shared team mailboxes.
Receive one-time downloads or trial notifications without exposing your long-term personal address.
Validity is more than a static number
Temporary addresses show their remaining time clearly. Extend an address while the current task is still in progress, or switch to a new one to retest signup or delivery from a clean context.
- Countdown: Know exactly how long the current address remains available.
- Extend: Keep an observation window open while you investigate.
- New address: Start over without mixing the previous round’s emails into your results.
The inbox updates automatically, with manual refresh available
The workspace checks for new messages periodically, and you can refresh it whenever you need an immediate confirmation. Once a real email arrives, demo content leaves the list automatically so it cannot be confused with real results.
- Real emails and demo placeholders stay strictly separate
- Open full details when a new message arrives
- Times are shown in your device’s local format
Choose the right address
Temporary email and forwarding aliases serve different timeframes
Temporary email is ideal for verification that starts now and ends soon. Forwarding aliases work better when you need ongoing delivery to your real inbox. Each tool has its own focused workspace.
One-time verification
Use a temporary address for signup tests, verification codes, and short-term downloads. No login is required—open the page and get started, then let the address expire when the task is done.
Ongoing testing
When you need to monitor product notifications across multiple days, use an email alias. Log in to the forwarding workspace to manage aliases and archives from the past 30 days.
Team boundaries
Assign each external service its own address to identify where messages come from. When a scenario ends, pause that entry point without affecting other tasks.
Why HTML emails need isolated previews
Email content may include its own colors, fonts, tables, and responsive rules. Placing it directly on a site page can rewrite its styling or contaminate the workspace. Temponce displays real HTML in a restricted frame with basic line-wrapping and image-width rules, keeping each email independent.
- Preserve the email’s original visual hierarchy first
- Then prevent long links and large images from breaking the reading area
- Fall back to plain-text content when HTML is unavailable
Email still hasn’t arrived? Troubleshoot in order
First confirm that the sending task reported success, then check that the recipient address is complete. Wait briefly and refresh manually. If the address has expired, switch to a new one and resend. If nothing appears, check sender logs, queue status, and bounce records instead of repeatedly sending duplicate tasks.
- Copy the address to avoid typing errors
- Check the countdown to rule out an expired address
- Review sender logs to distinguish queuing from delivery failure
Usage boundaries
Minimize identity exposure while using email normally
Test email reduces unnecessary identity exposure, but it should not be used for impersonation, harassment, bypassing service rules, or accounts that must remain recoverable long term.
Product testing, template previews, verification-code integration, public-resource downloads, and controlled short-term trials.
Banking, healthcare, government services, long-term subscriptions, or any critical account that must be recoverable by email in the future.
Do not send spam, bypass access restrictions, or register for or receive sensitive material using someone else’s identity.
Save the test evidence you actually need, remove temporary addresses, and never treat a one-time inbox as a permanent archive.
Frequently asked questions
Quick answers about test email
Learn about address validity, verification-code delivery, email previews, and privacy boundaries. For real delivery failures, also check the sender’s logs.
Can a temporary email receive verification codes?
Yes, as long as the sender accepts the address and the message is delivered normally. The code will appear in the list like any regular email. Avoid temporary addresses for critical accounts because recovery cannot be guaranteed after the address expires.
Why are two demo emails shown on the homepage?
An empty inbox uses demo messages from Zoom and GitHub to show what the list and full message view look like. They do not count toward your real email total, and the demo rows disappear automatically when the first real email arrives.
What is the difference between extending an address and switching addresses?
Extending keeps the current address and adds more time, which is useful for monitoring the same task. Switching creates a new isolated entry point for retesting a signup flow or cutting off the previous context.
Do HTML emails execute scripts directly on the page?
No. Real HTML emails are displayed in a restricted reader without script execution, and their styles are prevented from affecting the site interface.
How long does it take for an email to arrive?
Most test emails appear quickly, but sending queues, sender-side rate limits, and recipient delivery policies can cause delays. Refresh manually and check the task and bounce logs on the sending side.
Is Temponce a permanent email service?
No. The homepage provides temporary email with a countdown. For ongoing delivery, use the dedicated forwarding-alias workspace to manage aliases and archives as needed.