Custom domains for AI-built websites: how it actually works

You asked an AI to build a website, and it did. The tool handed you a link, something like preview-3f8a2.some-tool.app, and the page loads. For a first look that is fine. To put on a business card, an invoice, a Google listing or an ad, it is not, and the reason is the address itself. This post explains what a custom domain actually is, the two mechanisms that make it work (DNS and SSL), and why owning the address is the step that turns a generated draft into a website in the full sense.

What a domain really is

A domain name is a rented, human-readable label that points at a place on the internet. yourbakery.com is not the website; it is a signpost that tells a browser where the website lives. You lease that label from a registrar, usually for a year at a time, and for as long as the lease runs, the name is exclusively yours. Nobody can take yourbakery.com while you hold it, and it moves with you if you ever change hosts.

A preview link is the opposite of all of that. It is a temporary label the tool assigns from its own pool, on the tool's domain, revocable at the tool's discretion. You do not lease it, you cannot move it, and it carries the tool's name rather than yours. That single difference, ownership of the address, is what separates a demo from a site. It is also the fifth of the five questions that decide whether a site is really online: can you point a domain you own at it?

Mechanism one: DNS, the internet's address book

DNS, the Domain Name System, is the lookup layer that translates your domain into the server that answers for it. When someone types your domain, their browser asks DNS "where does this name point?" and DNS returns an address. Connecting a custom domain to your AI-built site means writing two small records at your registrar so that answer points at your host.

• An A record for the bare domain (yourbakery.com), holding the IP address of the host that serves your site. This is the direct "the name lives here" pointer.
• A CNAME record for the www version (www.yourbakery.com), which is an alias that says "treat this the same as the main host." Some setups use a CNAME for the apex too; your host tells you exactly which records to add.

That is the whole configuration. You are not moving files or editing servers. You are updating a public directory entry so that a name you own resolves to a place that serves your pages. The one catch is time: DNS changes propagate across the internet's caches, usually within minutes but occasionally longer, which is why a freshly pointed domain can take a short while to go live everywhere.

Mechanism two: SSL, the padlock that has to be automatic

Once the name resolves, one more thing has to be true before the site is safe to share: HTTPS. The padlock in the browser bar means traffic between the visitor and the site is encrypted, and modern browsers actively warn people away from any site that lacks it. HTTPS depends on a TLS certificate, a cryptographic document that proves your domain is really served by your host.

Historically, obtaining and renewing certificates was a manual chore. That era is over. A host built for AI-generated sites issues a certificate automatically the moment your DNS records resolve, typically within a minute, using a free certificate authority, and renews it on its own before it expires. You never see a certificate file. The correct experience is that you add two DNS records, wait a moment, and the site is already loading over https:// with a valid padlock. If a platform asks you to handle certificates by hand, that is a signal it was not designed for this workflow.

Why a real domain beats a preview link, concretely

The case for a custom domain is not aesthetic. Each advantage is a concrete failure the preview link invites.

• It survives the tool. A preview link expires when the session is garbage collected or the subscription lapses. Your domain outlives any single tool, so the site you point it at can be rebuilt, moved or re-hosted without the address ever changing.
• Search engines will index it. Preview URLs are transient and are generally excluded from search. A stable domain is the thing Google can crawl, rank and send visitors to. No amount of good content earns traffic if it lives at an address that keeps changing.
• It carries trust. People read yourbakery.com as "this is the bakery." They read a random hash on a builder's domain as "this is a test." For anything transactional, that gap is the difference between a completed order and a closed tab.
• Email and branding line up. Owning the domain lets you run hello@yourbakery.com alongside the site, so the whole brand points at one name instead of scattering across a tool's subdomains.

The preview link is a genuinely useful thing for what it is: a way to see your work in progress. It is simply not the finished product, and treating it as one is the single most common way an AI website project quietly fails.

How the domain step fits the workflow

Connecting a domain is stage three of the prompt-to-production lifecycle: the AI builds the files, the files reach a host, the domain goes live, and then the site is operated over time. On a platform built for this, you do not touch a server at any point. You register or point the domain, add the two DNS records the dashboard shows you, and the certificate issues itself. If you are still deciding between this open model and an all-in-one tool that fuses building and hosting, the trade-offs are laid out in AI hosting versus website builders, and the mechanics of the whole publish step are in how AI-hosted websites work.

On AI-Hosted

AI-Hosted, powered by VibeDeploy and operated by Serso BV from infrastructure in Belgium, treats the custom domain as core rather than as a paid extra. Every plan includes custom domains and automatic HTTPS: add your domain, set two DNS records, and the certificate is live inside a minute, with no certificate handling on your side ever. There is no tier where "bring your own domain" is locked behind an upgrade, which is exactly the restriction that turns a hosted preview into a trap. More on who runs the platform is on the about page.

Plans are flat at 15, 39 or 129 euro per month including VAT, on the pricing page, and every account starts with a 14-day free trial that needs no card, long enough to build a site, point a real domain at it, and see it load with a padlock before you decide anything. Once it is live, the next question is whether it is ready for visitors, which is its own checklist.