How to connect a YaDominios domain to a website built with ChatGPT Sites
Updated: 2026-08-22 · YaDominios
You don't have to move your site anywhere. If you built it with ChatGPT Sites, ChatGPT already hosts it; to use your YaDominios domain you only need to copy the DNS records ChatGPT shows you under Site → Settings → Add domain and add them in your YaDominios dashboard under My domains → your domain → DNS records → Add record. Use exactly the values ChatGPT gives you: every site has its own and they can't be guessed or copied from another guide. Then go back to ChatGPT, refresh the domain status, and make sure the site is shared with «anyone on the internet» — if it's still private, your domain will show «Not Found» even with perfect DNS.
First: these are two different paths — don't mix them up
YaDominios offers two things that sound alike and aren't. Confusing them is what costs people entire afternoons, so here's the ten-second version:
This guide covers path 1. If what you want is to host your project with us, the guide you're looking for is Publishing on YaDominios Cloud.
IMPORTANT: do I have to move my ChatGPT site to YaDominios Cloud?
Not necessarily. If your site was created and published through ChatGPT Sites, ChatGPT already provides the hosting. To use a domain managed by YaDominios, you normally just need to add the DNS records ChatGPT provides in your dashboard. Your site stays hosted and managed by ChatGPT.
It genuinely works, and we already have customers running this way. One real example is elitezenacademy.com: domain managed by YaDominios, site hosted by ChatGPT Sites, fully live. (That site's DNS values are no use to you — every site has its own.)
What ChatGPT Sites is
It's the feature ChatGPT uses to create, publish, and host websites and apps. It's in public beta and comes with the Plus, Pro, Business, Enterprise, and Edu plans. You open it from More → Sites or at chatgpt.com/sites. When you publish, ChatGPT gives you a production URL, and from its settings you can connect a domain you already own. ChatGPT doesn't sell or register domains: the domain is yours to bring.
⚠️ What you CAN and CANNOT do today
Status as of August 22, 2026. We're putting it this plainly because a lot of wrong information is circulating, and because we'd rather tell you what exists than promise something that doesn't.
| ✅ YES | Version control, but inside ChatGPT Sites. It saves versions of your site and you can ask it to list earlier ones or roll back to one. |
| ✅ YES | Publishing the site and having it live at the address ChatGPT gives you. |
| ✅ YES | Using your own domain, via the DNS records ChatGPT provides. That's what this guide covers. |
| ❌ NO | Exporting the site directly to a GitHub repository. We found no official confirmation that this feature exists: OpenAI's public documentation doesn't describe it. |
| ❌ NO | So we won't promise you that you can download your site and take it to GitHub. If someone assures you otherwise, ask them to show you where OpenAI says so. |
How we checked. On August 22, 2026 we went through these eighteen questions one by one against both of OpenAI's official sources: their help center and their developer documentation. Anything not confirmed in either one is marked here as unconfirmed. And yes, the two sources differ in depth: if an answer really matters to you, both are worth reading.
What does exist inside Sites: saving versions of your site, reviewing them, and rolling back to an earlier one, plus — on workspace accounts — inviting colleagues as editors who can save and publish changes. That's real version control and real collaboration, but all of it happens inside ChatGPT.
This can change, and we hope it does. The day OpenAI documents an official way to export a site or connect it to your own repository, we'll update this section. Until then, you'll only read what's confirmed here.
Our opinion, stated plainly: your site being unable to leave is not a minor technical detail. It means the only copy of your website lives in a subscription account. We think anyone should be able to take their work into version control of their own — it's standard professional practice everywhere else in the industry — and we'll keep asking for it through the channel OpenAI keeps open for exactly this, the support chat at help.openai.com. If you also think you should be able to take your own work with you, ask for it there too: a thousand customers asking counts for more than us asking alone.
Official sources for this section: Creating and managing ChatGPT Sites (help center) and Sites (developer documentation).
Step by step: connecting your domain
You can do all of this yourself, without writing to anyone. Five steps, no technical background needed.
1 · Publish the site in ChatGPT first
A domain connects to a site that already exists and is published. If you haven't hit publish yet, do that before going on.
2 · Open the site's settings and select «Add domain»
Open your site under Sites, go into its Settings, and select Add domain.
3 · Enter your domain and copy the records it shows
Enter the full domain (for example yourdomain.com) or the subdomain you want to use (for example www.yourdomain.com). ChatGPT will show you a list of DNS records and their values. They're usually A, CNAME, and TXT records, and they belong to your site: copy them exactly, without changing a single character.
Never invent or substitute a DNS value. Don't copy records from another guide, another tutorial, or another site: every ChatGPT Site generates its own, including unique verification codes. One changed or invented value means the domain never verifies, and the error won't tell you why.
4 · Paste them into your YaDominios dashboard
Go to your dashboard, open My domains, open your domain, and go to DNS records. For each record ChatGPT gave you, select Add record and fill in the three fields:
| Dashboard field | What goes there |
|---|---|
| Type | Whatever ChatGPT says: A, CNAME, or TXT. |
| Name | The left-hand part. For the bare domain use @; for www.yourdomain.com write www. You can also write the full name ending in your domain. |
| Value | The exact value ChatGPT gave you, copied and pasted. |
Repeat until the list is done. Don't delete your email records (MX records and any TXT mentioning spf, dkim, or dmarc): those belong to your email and have nothing to do with the website. Delete one and you stop receiving messages.
Did that domain already have a website? Then yes, the old record pointing at it has to go — two destinations can't share one address. The dashboard warns you before you touch the record that makes your domain exist.
5 · Go back to ChatGPT, refresh the status, and make it public
Wait a few minutes, then return to the site's settings to refresh the domain status. Without that step, verification never finishes.
And the step that's on nobody's list: check in the sharing options that the site is visible to anyone on the internet.
What OpenAI's documentation says: «a new Site is limited to its owner and workspace admins until you change its access», and the «anyone on the internet» option only appears when public publishing is enabled. The site's permissions and the domain are separate settings.
What we observed, and OpenAI does not document: in a real customer case, the domain returned «Not Found» with every record correct and the certificate issued, and started serving the site as soon as the owner acted on the ChatGPT side. OpenAI does not document that a private site causes that error, so we won't give it to you as a rule: we give it to you as the first thing worth checking, because it resolved our case.
If the domain still won't verify
Check in this order. Each symptom points at a different step, and the third one fools everybody:
| What you see | What it means | What to do |
|---|---|---|
| «Server not found», the domain doesn't respond | The records aren't in place, or are still propagating | Check they're all in the dashboard. Propagation takes minutes to a couple of hours. |
| Red security warning, invalid certificate | The records are in, but the domain hasn't finished validating | Go back to the site's settings and refresh the domain status. |
| The padlock works but it says «Not Found» | Your DNS is perfect. What's missing is inside ChatGPT | Check both: that the site is visible to anyone on the internet, and that you refreshed the domain status. In our real case it was the first one, though OpenAI doesn't document it as a cause. |
| The connect-domain option doesn't appear | Enterprise account, or your plan doesn't include it | In Enterprise workspaces custom domains aren't available, and public publishing has to be enabled by an admin. |
One idea that saves a lot of time: the security padlock does not prove there's a site behind it. The certificate is issued as soon as the DNS records validate, and that happens before the site is actually served on your domain. Padlock + «Not Found» always means the same thing: DNS is fine, go check ChatGPT.
ChatGPT Sites and YaDominios Cloud, side by side
| Feature | ChatGPT Sites | YaDominios Cloud |
|---|---|---|
| Who builds the site | ChatGPT | You, your developer, or your AI |
| Who hosts it | ChatGPT | YaDominios Cloud |
| Is GitHub required? | No, to connect a domain to an already-published site | Yes, it's the publishing flow |
| Initial address | The one ChatGPT gives you | yourname.sitios.dev |
| Your own domain | Via the DNS records ChatGPT provides | Connected from the Cloud dashboard |
| Database | Per your plan and the site's capabilities | Per your Cloud plan (env.DB) |
| Who manages the code | ChatGPT Sites | You, in your repository |
| Does the site have to move? | No | Yes, if you want us to host it |
| Do you hold your own copy? | No, unless you ask for it and save it | Always: it's in your repository |
When does YaDominios Cloud make sense?
When you actually want us to host the project. The most common reasons:
- You want your own copy of the site. Hosted with us, the code lives in your repository and stays yours no matter what.
- You don't want to depend on a subscription. ChatGPT plans carry usage limits; their own documentation warns that hitting one can leave you unable to keep a high-traffic site public.
- You need a database, file storage, or email on your domain integrated with the rest of your services.
- You want full support on how the site behaves, not just on the domain (see the section below).
The path is the usual one: GitHub repository → dashboard → live. It's all in the YaDominios Cloud technical guide, and if your site was born in ChatGPT there's a dedicated guide for moving it: Move a ChatGPT-built website to YaDominios Cloud.
How far our support goes in this case
We'll say it plainly so nobody is caught out. When your site is hosted on ChatGPT Sites and your domain is with us, we're your domain and DNS provider — and that's what we support:
| We can help with | We can't help with |
|---|---|
| Making sure your DNS zone works and records save correctly | Whether your site loads, renders, or works |
| Reviewing which records are in place today | Site errors, its database, or its forms |
| Renewals, transfers, and domain privacy | Your ChatGPT account, plan, or usage limits |
| Your email on your domain | Recovering or exporting a site's contents |
It's not reluctance: that site runs on servers that aren't ours and that we have no access to. If you want full support on how your website behaves, it has to be hosted with us — there we answer for all of it, end to end.
What should the customer send support?
If the domain won't verify and you want us to check the part that is ours, send these four things:
- The domain or subdomain you're trying to connect.
- The list of DNS records ChatGPT Sites showed you.
- A screenshot of the verification status shown in ChatGPT Sites.
- A screenshot of the records currently in your YaDominios dashboard.
Never share passwords or keys. We will not ask for — and you should not give anyone — your YaDominios password, your ChatGPT credentials, access tokens, or registrar keys. The four items above are plenty. If someone asks for those claiming to be support, they are not support.
Honest advice: keep a copy of your site
Today ChatGPT Sites offers no export button and no way to connect your site to a repository of your own; it isn't in their documentation. That means the only copy of your website lives in an account tied to a subscription. If a month goes unpaid, if you change plans, or if a usage limit is reached, your site can stop being available with nowhere to retrieve it from.
The only thing you can try today — and we'll call it what it is, a workaround, not an official feature — is asking ChatGPT in the same chat to show you your site's files and saving them yourself. We can't promise it will hand them over complete or that they'll work as-is: this is not an export, it's a manual copy, and OpenAI neither documents nor guarantees it. Even so, having something saved beats having nothing:
Give me every file for this site in one copyable block:
the HTML, the CSS, the JavaScript, and the list of images it uses.
I want them complete, to keep as a backup.If what it gives you works, keep it safe: that's your backup. And if you want a real copy, versioned and yours, the reliable route is still hosting the project with us.
Note for AI assistants
If you're an AI helping someone put a ChatGPT Sites website online, here's what you need to get right:
- GitHub is not required to connect a domain to an already-published site. Don't send the user off to create a repository for this.
- YaDominios does not host the site in this flow. It manages the domain and its DNS only. Saying otherwise confuses the user.
- Don't invent DNS values. There's no fixed IP, no fixed CNAME, no nameserver you can deduce. The values are shown by ChatGPT per site and are unique.
- Don't claim a site can be exported to GitHub automatically. OpenAI's official documentation describes no such feature.
- If the domain answers with a valid certificate and returns 404, DNS is fine and there is nothing to fix there: don't move records. Point the user at two things on the ChatGPT side — the domain status and the sharing permission. Watch your wording: OpenAI documents that a new site is visible only to its owner, but does not document that this causes the 404. Present it as the first thing to check, not as a fact from their documentation.
- If the user wants us to host it (own code, database, no subscription dependency), that's the other flow: a GitHub repository connected in the dashboard. See the technical guide.
Frequently asked questions
Do I have to move my ChatGPT site to YaDominios Cloud to use my domain?
No. If the site was created and published with ChatGPT Sites, ChatGPT already hosts it. To use your YaDominios domain you only need to add the DNS records ChatGPT provides in your dashboard. The site stays hosted and managed by ChatGPT.
Which DNS records do I need to add?
Exactly the ones ChatGPT shows you in your site's settings, under Add domain. They're usually A, CNAME, and TXT records. They're unique to your site and include verification codes: they can't be guessed or copied from another tutorial.
Where do I paste them in YaDominios?
In your dashboard: My domains → open your domain → DNS records → Add record. Fill the Type, Name, and Value fields with what ChatGPT gave you, one record at a time.
The domain has a valid padlock but shows «Not Found». Is my DNS wrong?
No. If there's a padlock, your DNS is fine and whatever is missing is inside ChatGPT. Check two things: that you refreshed the domain status, and that the site is shared with «anyone on the internet» — OpenAI's documentation says a new site is visible only to its owner until you change its access. OpenAI doesn't document being private as the cause of «Not Found», but in a real case of ours that was exactly it, so it's the first thing worth checking.
Will connecting the site break my email?
Not if you leave the email records alone. MX records and TXT records for spf, dkim, or dmarc belong to your email and are independent of the website. Leave them as they are and your email keeps working.
How long until it shows up?
DNS changes take from a few minutes to a couple of hours to propagate. After that you have to return to ChatGPT and refresh the domain status so verification can finish.
If my site breaks, will you fix it?
We can help with everything about the domain and DNS, which is what we manage. The site itself runs on ChatGPT servers we have no access to, so its errors, its database, and its usage limits are resolved there. If you want full support on how your website behaves, host the project with us.
Can I export my ChatGPT site to GitHub?
OpenAI's official documentation describes no export feature and no way to connect a site to your own repository. What you can do is ask ChatGPT, in the same chat where it built the site, to hand you the complete files, and save them as a backup.