You Built It With ChatGPT. Here's How to Point Your Domain at It.
Michael Sacca•There is no such thing as "ChatGPT domain hosting." You already know that on some level, because you searched it anyway — which tells me exactly where you are. You (or someone you hired, or Claude, or your nephew) built a website with ChatGPT. The code works. It's sitting in a chat window, or in a Canvas tab, or pasted into a folder on your desktop. And now you've hit the wall everyone hits: the chat cannot see the internet, and the internet cannot see the chat. You need to get that code onto a real host and point a real domain at it.
That's a DNS-and-deploy problem, not an AI problem. Let's walk it.
(If you're still deciding where to deploy — and why the path differs depending on whether Claude, ChatGPT, or a website builder handed you the code — I covered the full decision tree in "Claude Built It, ChatGPT Coded It: The Three Paths From AI-Generated Code to a Live Domain". This post assumes you've made the call and just want the domain connected.)
Step zero: get the code out of the chat
ChatGPT builds sites in a few ways, and the export path differs:
- Canvas / plain code blocks: Copy the HTML, CSS, and JS into files on your computer. You want an
index.htmlat the root. If ChatGPT split things into multiple files, keep the same relative paths it used (styles.css,script.js) or the links break. - Single-file pages: Most ChatGPT landing pages come out as one self-contained HTML file with everything inline. That's the easiest case — one file, done.
- A framework project (Next.js, etc.): If you asked for a React app, you don't have a static site anymore — you have a project that needs a build step. For your first deployment, honestly, ask ChatGPT to rewrite it as a single static HTML page unless you specifically need the framework. It'll deploy in minutes instead of hours.
The gotcha that bites everyone: file names are case-sensitive on real servers. Index.html is not index.html. Normalize before you upload.
The three hosts people actually land on
When you search for easy hosting solutions after building with AI, three names dominate the results, and they're all fine choices. The differences matter mostly at the DNS step.
Option 1: Netlify — fastest path from folder to URL
- Go to Netlify and sign up free.
- Find Netlify Drop — literally drag your folder onto the page and it deploys.
- You get a throwaway URL like
something-random.netlify.app. - Go to Site configuration → Domain management → Add a domain, enter your domain.
For DNS, you have two choices:
- Keep your registrar's DNS (add records manually): Add an
Arecord pointing your apex domain (yourdomain.com) to Netlify's load balancer IP — Netlify shows you the exact IP in its DNS instructions, so use what it displays rather than anything hardcoded — and aCNAMEforwwwpointing at your site's Netlify subdomain. - Let Netlify manage DNS (recommended if you're not attached to your registrar): At your registrar, change the nameservers to the ones Netlify gives you (they look like
dns1.p0X.nsone.net). Then Netlify handles the A/CNAME records automatically and adds HTTPS for you.
The nameserver route is the "easy hosting" answer. One change at the registrar, everything else is automatic.
Option 2: Vercel — good if you ended up with a framework
Vercel's flow assumes you might have a build step, which matters if ChatGPT handed you a Next.js project.
- Push your project to GitHub, or use
vercelfrom the command line, or import a folder. - In the dashboard, open your project → Settings → Domains → Add, type your domain.
- Vercel tells you precisely which records to set. Typically: an
Arecord for the apex pointing at Vercel's76.76.21.21, and aCNAMEforwwwpointing atcname.vercel-dns.com.
One Vercel-specific note: if you bought your domain through Vercel, none of this applies — they wire it up for you. If your domain is elsewhere, you can also transfer DNS to Vercel's nameservers the same way as with Netlify.
Option 3: Cloudflare Pages — the "one vendor for everything" play
Cloudflare's pitch is that your domain, DNS, and hosting all live in one dashboard, which genuinely simplifies the "AI domain hosting" question.
- Move your domain's DNS to Cloudflare (free plan — Cloudflare walks you through a nameserver change at your registrar).
- Create a Pages project, upload your static files or connect a Git repo.
- Under Custom domains, add your domain. Because the domain's DNS is already in Cloudflare, it provisions the CNAME and the SSL certificate itself. This is the shortest click-path of the three — one nameserver migration, and after that every future project connects with two clicks.
"But my domain is at GoDaddy/Porkbun/Namecheap"
Your registrar and your host are different jobs. The registrar sold you the name; the host serves the files. Connecting them means one of two edits at the registrar:
| Approach | What you change | Best when |
|---|---|---|
| Add records | An A record (apex) and/or CNAME (www) | You want to keep email or other DNS records where they are |
| Change nameservers | The NS entries, to your host's nameservers | You want the host to manage everything going forward |
In GoDaddy: My Products → DNS → Manage DNS. In Namecheap: Domain List → Manage → Advanced DNS. Porkbun: Domain → DNS Records. The screens differ, the records don't.
One warning if you switch to Cloudflare: their default proxy (the orange cloud) sometimes needs to be toggled off for the initial verification with a host, then back on. If your domain stubbornly resolves to the wrong place after setup, that's the first thing to check.
The two things that always trip people up
Propagation isn't a thing you wait for anymore — mostly. Old guidance says "wait 24–48 hours." Nameserver changes genuinely can take that long, because registrars set slow TTLs on NS records. But A and CNAME record changes on a modern DNS provider usually propagate in minutes. Check with dig yourdomain.com or an online DNS checker. If it's been six hours, don't panic; if it's been six minutes, stop refreshing.
HTTPS is not automatic everywhere. Netlify, Vercel, and Cloudflare Pages all issue free SSL certificates via Let's Encrypt, but issuance happens after DNS points correctly — sometimes taking several minutes to an hour. If your site loads but shows a padlock warning, it's not broken; the cert just hasn't landed yet. Give it an hour before you file a support ticket.
What you should NOT pay for
Since you came in through a search for "ChatGPT domain hosting," let's kill the upsells. You do not need: paid hosting (free tiers of all three hosts handle a static AI-built site comfortably — though free tiers have export and hosting limits worth understanding, which I covered in "Free Website Builders Meet AI-Generated Code: What the Free Tier Costs You at Deploy Time"), premium DNS, an SSL certificate purchase, or "website hosting with AI included" bundles. Your only unavoidable cost is the domain itself, roughly $10–15/year wherever you buy it.
The whole path, compressed
- Export the code from the chat as an
index.html(plus assets). - Drag it into Netlify Drop, or deploy to Vercel/Cloudflare Pages.
- At your registrar: either add the host's A/CNAME records or switch nameservers.
- Wait for DNS, wait for the SSL cert, done.
Total hands-on time: about fifteen minutes. The chat built the site; this part was always going to be yours.