SPONSORED
Service Components & Health Checks

System Status & Architecture

The components behind TEMP MAIL, what each one does, and how to verify current service health yourself.

Check Current Service Health

We don't publish static uptime percentages on this page, because a hardcoded number can't reflect live conditions. Instead, you can verify the service directly in seconds:

  • Generator check — load the homepage and confirm a fresh address is issued immediately with a working 15-second inbox refresh.
  • Mail delivery check — copy your address, trigger a verification email from any sign-up form, and confirm it arrives in the inbox stream.
  • API check — developers can call POST /api/generate-email from the API documentation and confirm a valid JSON response.
  • Report an issue — if any check fails for you, tell us through the contact page with the page URL and timestamp so the infrastructure team can investigate.

Core Infrastructure Components

Each component below plays a specific role in delivering disposable inbox sessions. These descriptions explain what the system is designed to do; for step-by-step help when something misbehaves, see the troubleshooting guide.

Inbound MX Routers

Mail Receiving

Receives incoming SMTP packets from external email senders and routes them to active recipient sessions.

Verify by: Sending a test OTP

Client Polling & Sync

Inbox Refresh

Asynchronous browser polling engine delivering inbox refresh and automated OTP extraction.

Refresh cycle: Every 15 seconds

Message Purge Process

Data Minimization

Expired messages are dropped automatically so inbox contents are not retained indefinitely — see the privacy policy for retention details.

Retention window: 7 days

REST API Gateway

Developer Access

Developer API endpoints powering automated QA tests, Playwright scripts, and third-party widgets.

Verify by: Calling the API docs

How We Handle Incidents

Reports Go Straight to the Infrastructure Team

Rather than maintaining a hand-written incident log that could drift from reality, we route every delivery or availability report from the contact page and troubleshooting guide directly to the team operating the service. If you experienced a delay or outage, tell us the page URL and timestamp and we will investigate the specific request path you used.

Known Limitations Are Documented Up Front

Disposable inboxes are intentionally ephemeral: messages are automatically deleted after 7 days, and senders that block or filter disposable domains may never deliver. These are documented characteristics of the service rather than incidents — read the FAQ and safety guide for the full picture before relying on the tool for time-critical mail.

Infrastructure & Reliability Design

Stateless Session Design

Inbox sessions live in the browser and are recreated on demand, so there is no heavy per-user server state to migrate during deploys and no long-lived account database to breach.

External Mail Routing Provider

Inbound mail is accepted through our upstream mail routing provider and forwarded to the active session. Delivery speed therefore depends on both our polling interval and the sender's own sending infrastructure — see the API documentation for how messages are fetched.

Minimal Data Footprint

Because sessions are ephemeral and messages expire, the architecture naturally limits how much data exists at any time. The security standards page explains what is and is not stored in more detail.

Notice an unexpected delivery delay or network anomaly?

Troubleshooting Guide Contact Infrastructure Team