Private Temp Mail Domains
Private domains are the premium feature that serious teams expect from a disposable email API. TempMailGrab supports bring-your-own-domain workflows so QA, security, and automation teams can receive temporary mail on a domain they control.
Your Temporary Email Address
Waiting for mail...
- No signup
- 24-hour inbox
- OTP auto-detect
- Zero tracking
- Android · Chrome · Firefox
- Developer API
Why private domains matter
Shared disposable domains are useful for quick public testing, but they are also easy for signup forms to block. A private domain gives your team a cleaner testing surface: the domain belongs to you, the addresses are created programmatically, and incoming mail is still parsed, stored temporarily, and deleted by policy.
What TempMailGrab provides
- BYOD API endpoints: register a custom domain, receive DNS requirements, and verify MX/TXT routing from the API.
- Private inbox ownership: API-created inboxes are tied to your account key, not public mailbox names.
- OTP and link extraction: messages expose
extracted_otpandextracted_linksfields for test automation. - Signed webhooks: receive pushed email events with HMAC signatures instead of polling forever.
- Configurable TTL: API inboxes can be short-lived for fast tests or longer-lived for multi-step QA workflows.
Best use cases
| Team | Private-domain workflow |
|---|---|
| QA automation | Create one inbox per Playwright or Cypress test and read the OTP as structured JSON. |
| SaaS engineering | Route staging signup mail into disposable inboxes without reusing shared test accounts. |
| Security testing | Run account-recovery and email-verification tests without exposing staff inboxes. |
| Agencies | Separate client test mail by domain while keeping cleanup automatic. |
How setup works
- Create a developer account from the dashboard.
- Generate an API key.
- Call
POST /api/v1/byodwith the domain you control. - Add the required DNS records at your DNS host.
- Call
POST /api/v1/byod/:domain/verifyand begin creating inboxes.
Related developer links
- API documentation
- Email testing API
- Playwright temporary email API
- Cypress temporary email API
- Premium plans
Last verified: . Private-domain setup requires a domain you control and correct DNS routing. Disposable-address acceptance still depends on the service receiving the signup.
Automate inboxes with the API
Prefer to script it? Generate disposable inboxes and read auto-parsed OTPs & verification links programmatically — built for QA, test automation, and bots. The same private inboxes, over a clean REST API.
# 1. Create a private inbox
curl -X POST https://tempmailgrab.com/api/v1/inbox \
-H "Authorization: Bearer $TMG_API_KEY"
# → { "id": "inb_…", "address": "a1b2c3d4e5f6@tempmailgrab.com" }
# 2. Poll for mail — the OTP + verification links are auto-extracted
curl https://tempmailgrab.com/api/v1/inbox/$ID/messages \
-H "Authorization: Bearer $TMG_API_KEY"
# → { "messages": [{ "extracted_otp": "123456", "extracted_links": [ … ] }] }Related guides
Frequently Asked Questions
Can I use my own domain with TempMailGrab?
Yes. Bring-your-own-domain support is exposed through the developer API: register the domain, add the required DNS records, then verify it before creating inboxes.
Do private domains avoid every disposable-email blocklist?
No. A private domain gives you more control and avoids shared public-domain reputation, but any receiving service can still choose to block disposable or newly observed domains.
Are private-domain inboxes public?
No. API-created inboxes are tied to your account key. They are not public mailbox names that anyone can open by guessing the address.