GPTMail Private Domains let you connect a custom domain for personal use, keep it out of the public domain list, and protect inbox access with a private passphrase.
What Is a Private Domain?
A private domain is a custom domain that you add only for your own use.
Unlike public domains, private domains do not appear in GPTMail's public domain list. Other users will not see them as selectable email domains, and they are not intended for shared public inbox usage.
This makes private domains useful when you want a temporary or lightweight inbox experience, but with a domain that belongs to you.
How It Works
When you add a private domain, GPTMail generates a dedicated MX target for that domain.
Instead of pointing your domain to the public MX target, you point its MX record to the private target generated by GPTMail. After DNS is configured, GPTMail checks the MX record. If the record matches the expected private target, the domain becomes active.
The setup flow is:
- Enter your domain.
- Set a private passphrase.
- Generate the private MX target.
- Add the MX record at your DNS provider.
- Run the MX check in GPTMail.
- Start receiving mail through that private domain.
Why Private Domains Are Different From Public Domains
Public domains are designed for general shared usage. They can be shown in public lists, used by visitors, and exposed as part of the normal GPTMail address experience.
Private domains work differently:
- They are hidden from public domain lists.
- They require a passphrase before inbox access.
- They use a separate private MX target.
- They are intended for personal use.
- They are not currently exposed through the public API.
This separation keeps the public domain pool clean while giving advanced users more control over their own domains.
Accessing a Private Domain Inbox
After the private domain is active, addresses under that domain can be opened directly.
For example, if your private domain is example.com, you can visit:
https://mail.chatgpt.org.uk/name@example.comBefore the inbox is shown, GPTMail asks for the private passphrase that was set when the domain was added.
Without the correct passphrase, the inbox remains locked.
DNS Requirements
A private domain must have an MX record pointing to its generated private target.
For example:
example.com. MX 10 your-generated-target.private-mx.chatgpt.org.uk.The exact target is generated by GPTMail and should be copied from the private domain setup page.
The private MX target is separate from the public MX target. This allows GPTMail to distinguish private-domain mail routing from public-domain mail routing.
When To Use Private Domains
Private domains are a good fit when you want:
- A personal disposable inbox on your own domain.
- A hidden domain that does not appear in the public list.
- Password-protected inbox access.
- More control over DNS and domain identity.
- A lightweight email receiving setup without creating full mailboxes.
They are especially useful for testing registrations, receiving one-time codes, separating projects, or keeping a private catch-all style inbox for a domain you control.
What Private Domains Are Not
Private domains are not full hosted email accounts. They do not replace a complete mailbox provider with outbound sending, user accounts, calendars, or long-term archival guarantees.
They are also not meant to make a domain public to every GPTMail user. If you want a domain to be shared publicly, it should be added as a public domain instead.
Private domains are intentionally scoped for personal receiving and protected inbox access.
A More Personal Temporary Inbox
Private Domains give GPTMail users a cleaner way to bring their own domain into the temporary inbox experience.
You keep the convenience of opening an address directly in the browser, while adding domain ownership, private MX routing, and passphrase protection.
For users who want more privacy and control than a shared public domain can provide, Private Domains offer a simple middle ground.