--- title: "ChatGPT Sites Custom Domains, and What They Do Not Cover" slug: /blog/chatgpt-sites-custom-domain publishedAt: "2026-09-22" updatedAt: "2026-09-22" author: ott priority: P1 keyword: chatgpt sites custom domain secondary_keywords: chatgpt site own domain, codex sites custom domain, chatgpt sites dns, chatgpt sites enterprise custom domain, chatgpt site address word_count_target: 1800 funnel_stage: Problem-aware schema: FAQPage, Article description: "Yes, a ChatGPT Site can use a domain you own, on plans where the feature is available and not in Enterprise workspaces at launch. What OpenAI documents, what a custom domain does not change, and which of the three reasons people ask it actually solves." --- # ChatGPT Sites Custom Domains, and What They Do Not Cover > **TL;DR:** A ChatGPT Site can use a domain or subdomain you already own. You update the DNS records at your registrar, and the domain stays registered where it is. The feature is available on some plans and not in Enterprise workspaces at launch. Only the Site owner can manage it. A custom domain changes the address. It does not change who can open the Site, and it does not lift the beta limits. --- ## 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?](/blog/chatgpt-site-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. > **Info:** **Address and audience are separate settings.** The domain answers "where is it?" The audience answers "who can open it?" Sites lets you change either one. It does not let a domain do the audience's job. --- ## 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.dev](/) hosts the page, and the publisher sets the audience by identity rather than by address. Your agent publishes an HTML or Markdown file from the command line, from MCP, or from a browser upload. 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 the Pro plan 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 you invite by email. An invited person outside your organization enters the one-time password sent to that address. They create no account. 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. A reviewer with edit permission can correct a line in the page in the browser. The Pro plan records who opened each artifact and keeps 90 days of audit logs. Two honest limits, because this post is about domains. A custom domain on display.dev is an Enterprise capability, scoped in the contract. Solo and Pro artifacts live at your organization's address on `dsp.so`. And display.dev hosts the page as a file. It does not run a Site's database or server code. 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. ```bash dsp publish ./report.html --visibility company ``` **[Publish your first page free](https://app.display.dev)** – 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](https://learn.chatgpt.com/docs/sites) - [Creating and managing ChatGPT Sites – OpenAI Help Center](https://help.openai.com/en/articles/20001339-creating-and-managing-chatgpt-sites) - [What's new – OpenAI Learn](https://learn.chatgpt.com/docs/whats-new) - [What is ChatGPT Sites? Plans, limits, and who can open one](/blog/what-is-chatgpt-sites) - [Can a ChatGPT Site be private?](/blog/chatgpt-site-private) - [Plans and limits on display.dev](/docs/limits) --- ## FAQ **Can a ChatGPT Site have a custom domain?** Yes, on plans where the feature is available. You connect an apex domain or a subdomain you already own by updating its DNS records. Custom domains are not available in Enterprise workspaces at launch. **Does OpenAI register the domain for me?** No. You must already own the domain and be able to change its DNS records. The domain stays with your registrar. **Which DNS records does a ChatGPT Site need?** OpenAI's public guide does not list them. The records appear in the connect flow inside ChatGPT when you attach the domain. **Can an Enterprise workspace use a custom domain for a Site?** Not at launch. OpenAI's documentation says custom domains are unavailable in Enterprise workspaces. Enterprise Sites use the ChatGPT-hosted address. **Does a custom domain make my Site private?** No. The audience setting decides who can open a Site. A Site is public, or it opens for people who sign in with a ChatGPT account. A domain changes the address only. **Can I change a Site's ChatGPT-hosted address without a domain?** Yes. Since August 2026 you can choose a new ChatGPT-hosted address for an existing Site without redeploying it. **Does display.dev offer custom domains?** On the Enterprise plan, scoped in the contract. Solo and Pro artifacts live at your organization's address on `dsp.so`. On every plan you choose who can open each artifact: the public, everyone at your company, or invited people.