ChatGPT Sites Custom Domains, and What They Do Not Cover

The short answer

Yes, where the feature is available. OpenAI's Sites guide says you can connect an apex domain or a subdomain that you already own. Sites does not register a domain for you. You change the DNS records, and the Site answers at your address.

Two conditions apply. Custom domains are not available in Enterprise workspaces at launch. And only the owner of a Site can configure one. Editors cannot.

What OpenAI documents

The public documentation is short. These are the facts it states.

• You connect an apex domain or a subdomain that you already own.
• You connect it by updating DNS records. The exact records appear in the connect flow inside ChatGPT, not in the public guide.
• The domain stays with your registrar. Nothing transfers to OpenAI.
• Custom domains are available where supported. The guide does not list availability plan by plan.
• Custom domains are not available in Enterprise workspaces at launch.
• Only the Site owner can manage custom domains, secrets, the Site name, the Site address, and ownership.

OpenAI does not publish how many domains a plan allows, or certificate details. Check the connect flow in your own account for the current limits.

The ChatGPT-hosted address

Every Site also has an address that OpenAI hosts. Since August 2026 you can choose a new ChatGPT-hosted address for an existing Site without redeploying it. That is useful when a Site outgrows the name ChatGPT gave it, and you do not want to attach a domain.

What a custom domain does not change

A custom domain changes what appears in the address bar. Four things stay the same.

Who can open the Site. The audience model does not move. A Site is either public, or limited to people who sign in with a ChatGPT account. An invited outside person must sign in with the account that received the invitation. A domain does not add a password, an email-domain check, or an expiry. See Can a ChatGPT Site be private? for each audience.

The beta limits. Every Site on your account shares one set of usage limits. When you reach one, a high-usage public Site may lose its public availability until usage drops. The Site loses it at your domain in the same way it would at the ChatGPT-hosted address.

Analytics. Sites shows unique visitors and page views over time on most plans. It does not show them for Enterprise-owned Sites. A domain does not change that.

The Enterprise gap. The plan most likely to need a branded address is the plan that cannot attach one at launch. If your team is on Enterprise, plan for the ChatGPT-hosted address for now.

Three reasons people ask, and which one a domain solves

People who search for this usually want one of three things.

1. A memorable address. status.acme.com instead of a generated name. A custom domain solves this completely.

2. A page that looks like it belongs to the company. A client opens report.acme.com and sees your domain. A custom domain solves this at the address bar. The page itself still runs on OpenAI's infrastructure under OpenAI's policies. The client still signs in with a ChatGPT account unless the Site is public.

3. Control over who opens it. Most people who ask about a domain for a client report or an internal dashboard want this one. They want the page to open for the client, or for the company, and for nobody else. A custom domain does not do this. The audience setting does, and it offers two shapes: public, or ChatGPT accounts.

If your reason is the third one, the domain is the wrong lever.

When the reason is the audience

Display is the AI docs workspace that's open to all agents and people. The publisher sets the audience by identity rather than by address. Any agent publishes an HTML or Markdown file through MCP, the CLI or the API, and you can also publish a file from the dashboard. The file gets its own URL under your organization's address on dsp.so. You choose who can open it.

• Public. Anyone, no sign-in.
• Company. Everyone at your organization. On Solo and higher plans, they sign in with the Google or Microsoft account they already use. On every plan, a one-time password sent to their email address also works.
• Private. You and the people and groups you share it with. You invite a person outside your organization by email and give them a role: Viewer, Commenter, Contributor or Editor. They sign in with a one-time password, Google or Microsoft, and do not join your organization.

An update keeps the same URL. Paid plans keep earlier versions. Reviewers comment on the page, and the next agent reads the comments through MCP. Your teammates can also select Edit and correct a line on the page. The Team plan records who opened each artifact, and when. Business keeps 365 days of audit logs.

Paid plans publish at your organization's chosen address on dsp.so, for example acme.dsp.so. Free uses a random one.

If the address matters and the audience does not, use the Sites custom domain. If the audience matters, publish the page where the audience is a setting. Ask your agent:

"Publish ./report.html to Display for everyone at my company."

Get started free – 3 gated artifacts on the Free plan, unlimited viewers, no card required.

We checked every custom-domain claim against OpenAI's Sites developer guide and help center on 22 September 2026. Sites is in beta. Availability by plan can change. Check the connect flow in your own account.

Sources and further reading

• Sites developer guide – OpenAI Learn
• Creating and managing ChatGPT Sites – OpenAI Help Center
• What's new – OpenAI Learn
• What is ChatGPT Sites? Plans, limits, and who can open one
• Can a ChatGPT Site be private?
• Plans and limits on Display