Important before changing MX: an MX change redirects inbound email for the domain. Only do this for a domain you control and understand. The MX hostname shown below must be backed by a working SMTP receiving service; a Cloudflare Worker alone cannot accept arbitrary Internet SMTP connections just because an MX record points at it.

1. Configure the requested MX record

At your DNS provider, add the following MX record for the domain you want to apply with. Remove or adjust conflicting MX records only after you have planned the mail-routing change.

TypeMX
Name / Host@
Priority10
Mail serverprivate-smtp.mailtemporary.com.

DNS changes can take time to propagate. The record is not proof of ownership on its own; the MailTemporary operator must review domain control and service readiness before approving an application.

2. Submit your domain for approval

Only the domain and a contact email are requested here. Applications remain pending until an operator checks the domain and its routing setup. Approval does not automatically configure DNS or provision an SMTP server.

Enter the domain only, without https://, a port, or a path.

3. Wait for manual approval

Applications are reviewed manually. While the status is pending, the custom domain is not enabled for inbound storage. If approved, it becomes selectable in the same browser session that submitted the application. Keep your browser session and contact email available.

Privacy and email delivery

MailTemporary is designed for short-lived, receive-only messages. Messages expire according to the service’s current settings. Do not route a primary business or personal domain here unless you are comfortable redirecting all inbound mail for that domain and understand the retention limits. Use a subdomain dedicated to testing when possible.

Need a short-lived inbox?

Create an address for a low-risk signup or email test. Do not use temporary email for accounts you need to recover.

Open MailTemporary →