moemail.app valid

MoeMail

MoeMail is a cute, fast, open-source temporary (disposable) email service built on Next.js and the Cloudflare stack. It generates throwaway email addresses that receive mail in real time, protecting your real inbox from spam and tracking. It offers a full OpenAPI (REST API) with API keys and webhooks for developers and automation testing, and its interface is available in seven languages.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T21:31:17.994Z. Cached copy · Source on moemail.app

# MoeMail

> MoeMail is a cute, fast, open-source temporary (disposable) email service built on Next.js and the Cloudflare stack. It generates throwaway email addresses that receive mail in real time, protecting your real inbox from spam and tracking. It offers a full OpenAPI (REST API) with API keys and webhooks for developers and automation testing, and its interface is available in seven languages.

## Key facts

- Create random or custom temporary email addresses instantly; mail arrives in real time.
- Mailboxes auto-expire; messages are deleted after expiration to protect privacy.
- Registration is required to securely manage your mailboxes.
- Email and mailbox sharing via share links.
- Full OpenAPI / RESTful API with API-key auth and webhook notifications.
- Open source and self-hostable for free on Cloudflare.

## Core pages

- [Home](https://moemail.app/en): What MoeMail is and how it works.
- [About](https://moemail.app/en/about): Background on the service and SoftMoe Studio.
- [Blog](https://moemail.app/en/blog): Guides and articles about temporary email and privacy.
- [10 Minute Mail](https://moemail.app/zh-TW/10-minute-mail): Short-lived inbox landing page, available only in Traditional Chinese, Japanese (`/ja/10-minute-mail`) and German (`/de/10-minute-mail`).
- [Disposable Email Checker](https://moemail.app/en/tools/disposable-email-checker): Free tool — look up whether a domain belongs to a disposable email provider, with two confidence levels and ready verdicts for 20 common domains.
- [Privacy Policy](https://moemail.app/en/privacy): How data is handled.
- [Terms of Service](https://moemail.app/en/terms): Usage terms.

## Email testing for developers

A reference section on testing email flows end to end with real, receivable inboxes. Start at the hub, which groups every page below.

- [Email Testing for Developers: The Complete Guide](https://moemail.app/en/email-testing): The hub.
- [Playwright Email Testing](https://moemail.app/en/email-testing/playwright): End-to-end tutorial.
- [Cypress Email Testing](https://moemail.app/en/email-testing/cypress): Verify emails in E2E tests.
- [Selenium Email Testing](https://moemail.app/en/email-testing/selenium)
- [Automate Email-Verification Testing](https://moemail.app/en/email-testing/verification): Across Playwright, Cypress and Selenium.
- [Testing Password-Reset Email Flows](https://moemail.app/en/email-testing/password-reset)
- [Automate OTP & 2FA Login Testing](https://moemail.app/en/email-testing/otp-2fa)
- [Testing Magic-Link / Passwordless Login](https://moemail.app/en/email-testing/magic-link)
- [Receive Email Programmatically in Node.js](https://moemail.app/en/email-testing/nodejs)
- [Receive Email with Python](https://moemail.app/en/email-testing/python)
- [Disposable Email API: A Developer's Guide](https://moemail.app/en/email-testing/api)
- [Receiving Inbound Email via Webhooks](https://moemail.app/en/email-testing/webhooks)
- [Email Testing in CI/CD (GitHub Actions)](http
…

Machine-readable: GET /v1/resolve?q=moemail.app · GET /v1/domain/moemail.app · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for moemail.app:
1. POST https://agentwebmap.com/v1/sites/moemail.app/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://moemail.app/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/moemail.app/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/moemail.app).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.