Adding Your Own Domain in GPTMail: MX Configuration, Public Submission, and Private Binding

Connecting your own domain to GPTMail requires configuring mail routing first, then choosing either public submission or private binding within your account. This article updates the current MX address and explains the difference between the two modes.

Content verified: November 15, 2026. Original publication date retained; for current pricing, quotas, and availability, please refer to the current descriptions at the linked pages.

Official GPTMail product image; for connecting your own domain, follow the verification process on the current page.
Official GPTMail product image; for connecting your own domain, follow the verification process on the current page. Click the image to view the original.

Decide first: public sharing, or use within your own account?

Public submission adds the domain to the public domain pool, so other users can also select this suffix; do not put your company's primary mailbox or an important business domain directly into a public temporary mailbox. If you want to manage it within your account, log in and use the private domain feature, and read the verification requirements at that entry point. The login-exclusive domain pool and a private domain you bind yourself are two different things.

Current MX address

In your domain's DNS management interface, add an MX record for the domain you want to connect. The current target is email.chatgpt.org.uk, and the email.gravityengine.cc from older articles is no longer the configuration basis for this guide. The hostname, priority, and verification prompts are subject to the GPTMail add-domain interface.

Do not directly overwrite the MX of a production domain that is actively receiving mail.Back up your existing DNS records first, confirm that no current email service depends on them, then configure and wait for DNS resolution to take effect. MX is for mail routing, not a web CNAME, and it cannot be replaced by enabling a web proxy.

Public submission procedure

  1. OpenGPTMail homepage, and go to the add public domain entry point.
  2. Enter a root domain that you have the right to configure. This entry point does not accept mail.example.com subdomain submissions like this.
  3. Configure MX as required by the page, wait for DNS to take effect, then submit for verification.
  4. Confirm the domain appears in the available list, then create a test address and send a test email that contains no private information.

The current new-domain reward depends on submission status: submitting while logged out earns a Key with 20,000 API call credits; submitting while logged in earns 200 points. Each domain is rewarded only once; resubmitting does not grant the reward again.

Why is it still unavailable after submission?

  • DNS has not yet taken effect, or the wrong domain level was modified.
  • The old MX conflicts with the new routing; you need to first confirm your email service migration plan.
  • The domain has already been submitted; resubmitting will not grant the reward again.
  • If the MX later becomes invalid, the domain will be disabled; after three consecutive failed checks, the associated API Key may also be disabled. After restoring a valid configuration, check the page status again.

Do not follow the old articles' claims that "visiting any address adds it automatically" or that messages are "permanently deleted every hour." Public temporary inboxes are not suitable for confidential email, and messages are retained for at most 24 hours.

Related entry points and sources for verification

阅读中文原文 / Read the Chinese original

上一篇 下一篇

评论与讨论

还没有评论,欢迎留下第一条讨论

有想法?一起聊聊
欢迎补充信息、提出问题或分享你的使用体验。
写下评论
comment url