Custom Domains
Connect one or more of your own domains to your Ycode site. On Ycode Cloud, custom domains are managed inside the dashboard — DNS records, SSL provisioning, ownership challenges and the Connected state are all surfaced in the same place.
Adding a Custom Domain
- Open the project dashboard and go to Settings → Domains
- Click Add domain
- Enter your domain — either an apex (
example.com) or a subdomain (www.example.com,app.example.com) - Click Add
The new domain appears in the domains list with a Pending DNS badge and the exact DNS records you need to add.
DNS Configuration
The DNS records you need are shown inline next to the domain as soon as you add it — no extra click required. The panel stays visible until the domain verifies, so you can come back and copy the values at any time.
Typical records:
- Apex domain (
example.com) — an A record pointing to Ycode’s IP - Subdomain (
www.example.com) — a CNAME record pointing to Ycode
Multi-part TLDs like co.uk, com.br or co.jp are detected automatically and the correct apex/subdomain record is shown.
Add the record at your DNS provider, then click Check now (in the inline panel) or Check status (on the domain row) to re-check verification. DNS propagation can take anywhere from a few minutes to 48 hours depending on your provider.
SSL Provisioning
Once DNS resolves, Ycode automatically provisions an SSL certificate for the domain. The domain moves through three states:
| State | Meaning |
|---|---|
| Pending DNS | Waiting for your DNS records to resolve to Ycode |
| Issuing SSL | DNS is good; the certificate is being issued |
| Connected | DNS resolves and the certificate is live — the domain serves traffic over HTTPS |
SSL provisioning happens without anyone keeping the Domains page open — a background sweep advances pending domains every few minutes. A domain only flips to Connected once HTTPS is actually live, so you can’t accidentally route visitors to a host that can’t serve TLS yet.
You don’t generate, install or renew certificates manually. Once a domain is Connected, the certificate is renewed automatically on Ycode’s end.
Ownership Challenge
If you add a domain that is already registered against another account on Ycode’s hosting provider, the domain row shows a TXT ownership challenge instead of (or alongside) the regular DNS records.
The panel gives you a _vercel TXT record to add and a Verify ownership action. Add the TXT record at your DNS provider, click Verify ownership, and the domain proceeds through Issuing SSL → Connected as usual.
Re-adding a Domain You Already Own
If you try to add a domain that’s already in your own account, Ycode highlights the existing entry with an info notice and scrolls you to it — instead of returning a dead-end “domain in use” error. Use the existing entry rather than creating a duplicate.
Setting a Primary Domain
When a project has multiple custom domains, mark one as Primary. The primary domain is the canonical URL Ycode uses for:
- The published-site link in the builder header
- Generated sitemaps and
hreflangalternates - 301 redirects from non-primary domains
Set as primary is only available once the domain is Connected, so the canonical URL is always a host that can actually serve HTTPS.
Self-Hosted Ycode
On self-hosted Ycode, custom domains are configured in your own infrastructure (Vercel project, reverse proxy, or whatever serves the published site). Set the NEXT_PUBLIC_APP_URL environment variable to the primary public URL so sitemaps and redirects use the correct host.