Temporary Email for Developers
Every application sends email eventually, and every developer eventually needs a mailbox that receives it. tempail.co provides working temporary inboxes — no mail server to stand up.
Inbox
Send an email to your new address — it will appear here automatically.
What developers can use it for
- End-to-end testing of signup and confirmation flows
- Verifying that links and codes in emails render correctly
- QA against a fresh address for every test run
- Manual checks of marketing and transactional email templates
How to test with it
Manual testing
Open tempail.co, copy the address, and use it as the destination in your test. Read the rendered message body right in the browser to confirm formatting and links.
Automated testing
The site is backed by a small JSON API wrapping the Mail.tm service, so scripts can request a new address and poll for messages programmatically instead of managing an SMTP server.
CI/CD and staging
Use a separate test inbox for each run, correlate the message with that run, and set a bounded wait for delivery. Closing a browser session is not a cleanup guarantee; follow the provider’s retention and deletion procedures.
A reproducible verification test
- Use an application or staging environment you own or are authorized to test.
- Create a separate test inbox and record a non-sensitive run identifier.
- Trigger one signup or verification email and wait with a bounded timeout; delivery can be delayed.
- Check the intended recipient, expected subject, and destination host before opening a verification link.
- Exercise the expected success state, then test expired or reused verification links in your own application.
- Keep credentials, real customer messages, and verification tokens out of shared test reports.
Why not a permanent mailbox?
Dedicated test inboxes collect hundreds of messages across runs, making it hard to tell which email belongs to which test. A fresh temporary address for every run keeps results isolated and honest.
And because there is no server to maintain, email testing stays a five-second step instead of a project of its own.
For developers, the value of a temporary email is not anonymity — it is isolation. A fresh working mailbox for every test run makes email verification flows something you can actually check, without infrastructure.
Use tempail.co responsibly
tempail.co is a privacy and testing tool. It must not be used for spam, fraud, harassment, identity abuse, or any unlawful activity. Read our Responsible Use Policy before using the service.
Frequently asked questions about Developers
Is there an API I can call from my tests?
The site uses a small JSON API around the Mail.tm service to create addresses and fetch messages. Your test suite can do the same via Mail.tm's public endpoints.
Does a temporary address receive mail from any sender?
It receives mail from any sender that can reach the provider's domain. Mail from any ordinary service that accepts email will be delivered.
How long does an address last during automated tests?
The address lives as long as the mailbox is active. For automated flows, create a fresh address per run and read messages promptly.
Can I test attachments?
Incoming messages are fetched from the provider and shown in the browser, so you can inspect delivered content — including attached files — as part of the flow.