OTP verification
Test signup and login flows you own or are authorized to test. The site detects common verification codes and offers one-click copy from the inbox row.
Throwaway email, ready in one second.
Short-lived inboxes for QA, app development, privacy, and reducing spam. No signup. Inboxes auto-delete in 10 minutes.
No signup 10-min auto-delete Session-bound inbox Abuse prohibited
How it works
Three steps. No account, no install.
-
Generate an address
Random local-part on a fresh domain. No input needed; the page issues one on load.
-
Use it for permitted workflows
Use the address for QA, development, privacy, or low-risk signups where disposable email is allowed. Incoming mail appears within 3 seconds.
-
Auto-deletes in 10 minutes
Inbox and all messages vanish on schedule. One extension of +10 minutes available.
What you'd use it for
Built for legitimate workflows where a short-lived inbox is useful and allowed.
Software testing
Use disposable inboxes in staging, demos, CI, and QA runs without polluting team mailboxes or customer data.
Spam reduction
Protect your personal inbox when trying newsletters, trials, or low-risk services that permit disposable addresses.
Privacy
No account is required. Inboxes are bound to a session cookie and messages are purged after the short retention window, subject to abuse handling and legal obligations.
FAQ
What can I use OTPmail for?
OTPmail is intended for QA, software testing, app and website development, privacy, spam reduction, and other lawful workflows where a short-lived inbox is permitted.
What is not allowed?
Do not use OTPmail for fraud, spam, phishing, account farming, selling verified accounts, bypassing KYC or identity checks, evading security controls, or abusing third-party services.
How long do inboxes last?
Each inbox auto-deletes 10 minutes after creation. You can extend once for +10 minutes. After that, the address and messages are purged from active inbox storage with no recovery.
Is this private?
Inboxes are bound to your browser session via an HttpOnly cookie. Knowing the address alone isn't enough to read someone else's mail. Messages are short-lived, and operational data may be processed for security, abuse prevention, and legal compliance.
Why do you use a domain pool?
A managed domain pool improves reliability for testing and separates short-lived mail traffic from your personal or company inboxes. Domains can be disabled when abuse is reported.
How do you handle abuse?
Fraud, phishing, spam, KYC bypass, and account abuse are prohibited. Report abuse at [email protected] or through the abuse page; we may disable domains, block patterns, preserve relevant records, and cooperate with lawful requests.
Is there an API?
Not as a public product at v1. The browser uses cookie-bound endpoints for the homepage. Any future API will include clearer limits, abuse controls, and compliance rules.