Published in Publish and share
Custom Domains
Replace your default yourbuild.chipp.ai URL with your own custom domain like chat.yourbrand.com. Custom domains make your AI chatbot feel like a native part of your brand.
Custom domains require a Builder plan or higher.
On Cloudflare? Skip ahead to Guided setup for Cloudflare.
Why Use a Custom Domain?
| Benefit | Description |
|---|---|
| Brand consistency | Keep users on your domain |
| Trust | Users stay in your branded environment |
| Professionalism | No third-party branding in the URL |
Prerequisites
Before setting up a custom domain:
- Builder plan or higher subscription
- Own or control a domain name
- Access to your domain’s DNS settings
- A published Chipp app
Setting Up a Custom Domain
Before configuring in Chipp, add this CNAME record at your domain registrar:
| Type | Name | Value |
|---|---|---|
| CNAME | chat (or your subdomain) | fallback.chipp.ai |
After you add the domain in Chipp (Step 4), you’ll also need to add a second CNAME record (at _acme-challenge. plus your subdomain) for SSL validation. Chipp will show you the exact record to add.
We recommend using a subdomain (like chat.) rather than your root domain. This keeps your main website separate and makes DNS configuration simpler.
In the app builder, go to Launch > Share. You’ll see the Custom Domain card. Click Connect a domain.
Type your subdomain in the input field:
chat.yourbrand.comDo not include https:// or www. in your domain.
Chipp runs a quick check on the domain. If it looks parked, for sale, or unregistered, you’ll see a warning and the button changes to Add anyway. The check is advisory and does not block you.
After you add the domain, the card shows both DNS records: Route traffic to Chipp (the CNAME to fallback.chipp.ai) and Enable HTTPS (the _acme-challenge CNAME). Add both at your registrar. Your domain will not load over HTTPS until both records exist. SSL activates automatically once Cloudflare validates the records (typically 5-30 minutes). Click the refresh icon next to the domain to check its status.
Guided setup for Cloudflare
If your domain’s DNS is on Cloudflare, Chipp can add the DNS records for you. You authorize once, Chipp writes the records, and the page keeps checking until your domain is live with a valid certificate.
The same Connect custom domain button is on both publish screens: Launch > Share for a chat app, and Launch > Site > Domain & Access for a Chipp Site.
Click Connect custom domain and type a subdomain such as chat.yourbrand.com or www.yourbrand.com. Chipp shows the exact DNS records it needs right away. You can copy them and add them yourself at any point (see “Add the records yourself” below).
Root domains such as yourbrand.com cannot be connected automatically. Use a subdomain.
Cloudflare does not let a third-party app sign in and edit your DNS, so you give Chipp a token that can edit DNS for one zone only:
- In Cloudflare, open My Profile > API Tokens > Create Token.
- Pick the Edit zone DNS template.
- Under Zone Resources, choose Include > Specific zone and select your domain’s zone.
- Create the token, copy it, and paste it into Chipp.
Chipp stores the token encrypted, uses it only to read and write the records shown on the screen, and never shows it again. Click Disconnect at any time to delete it. You can also delete the token in Cloudflare.
If something is wrong, Chipp tells you which part:
| Message | What to do |
|---|---|
| Cloudflare rejected this API token | The token is mistyped, expired or deleted. Create a new one. |
| This token is not allowed to read your zones | Edit the token and add Zone > Zone > Read and Zone > DNS > Edit. |
| This token cannot see a Cloudflare zone for your domain | Edit the token so its Zone Resources include the zone that holds your domain, or use the Cloudflare account that owns it. |
| This token can read your zone but is not allowed to change DNS records | Edit the token and add Zone > DNS > Edit for this zone. |
Before it writes anything, Chipp reads the records that already exist at the exact names it needs (your subdomain, _acme-challenge. plus your subdomain, and _cf-custom-hostname. plus your subdomain). It never touches any other record.
- Records that are already correct are reused. Nothing is duplicated.
- If a different record is already at one of those names, for example an
Arecord on your subdomain, Chipp shows it and does not replace it. Tick Replace next to that record to confirm. Chipp then replaces only the records you confirmed. - Chipp does not replace records it cannot restore (such as
MXorCAA). Remove those in Cloudflare yourself. - The record Chipp removes is saved in your organization’s audit log, so you can always put it back.
Click Add records to Cloudflare. You can click it again safely: records that exist are reused.
The dialog shows one status:
| Status | Meaning |
|---|---|
| Checking DNS | Chipp is checking that your records are visible. |
| Waiting for certificate | DNS is correct. The certificate is being issued, usually within a few minutes. |
| Active | Your domain is live with a valid certificate. |
| Action needed: … | One specific step needs you, named in the message. |
Chipp keeps checking by itself until the domain is active or a step needs you. You can close the dialog: checking continues in the background, and the domain shows as active in the Custom Domain card.
Add the records yourself
The manual path is always available. Every step of the guided dialog shows the exact record type, name and value, with a copy button. Add them at any DNS provider, then use Check again. You do not need to authorize Chipp to use this path. The sections below show how to add a CNAME at common providers.
What Chipp never does
- It never buys, moves or transfers a domain.
- It never changes DNS records outside the exact names listed on the screen.
- It never writes DNS without your Cloudflare authorization, and never replaces a record without your confirmation.
DNS Configuration by Provider
Cloudflare
- Go to your domain’s DNS settings
- Click Add Record
- Select CNAME
- Name: your subdomain (e.g.,
chat) - Target:
fallback.chipp.ai - Proxy status: DNS only (gray cloud)
Disable Cloudflare’s proxy (orange cloud) for the subdomain. Use “DNS only” mode for custom domains to work correctly.
GoDaddy
- Go to My Products > DNS
- Click Add under Records
- Type: CNAME
- Name: your subdomain
- Value:
fallback.chipp.ai - TTL: 1 Hour
Namecheap
- Go to Domain List > Manage
- Click Advanced DNS
- Add new record:
- Type: CNAME
- Host: your subdomain
- Value:
fallback.chipp.ai
Google Domains / Squarespace Domains
- Go to DNS in the sidebar
- Scroll to Custom records
- Create new record:
- Name: your subdomain
- Type: CNAME
- Data:
fallback.chipp.ai
Route 53 (AWS)
- Go to Hosted Zones > your domain
- Click Create Record
- Record name: your subdomain
- Record type: CNAME
- Value:
fallback.chipp.ai
Verifying Your Setup
Check DNS Propagation
Use these tools to verify your DNS is configured:
Enter your full domain (e.g., chat.yourbrand.com) and check that the CNAME record points to fallback.chipp.ai. Also check that _acme-challenge.chat.yourbrand.com points to the target shown in the Custom Domain card.
Test Your Domain
Once DNS propagates:
- Visit your custom domain in a browser
- You should see your Chipp chatbot
- Check the SSL certificate (padlock icon)
Troubleshooting
Domain stuck on “pending”
The Custom Domain card diagnoses the problem and highlights the step to fix:
- “Step 1 DNS record is missing or wrong”: set the CNAME for your subdomain to exactly
fallback.chipp.ai - “Step 2 DNS record is missing” or “points to the wrong target”: add or fix the
_acme-challengeCNAME using the target shown in the card - Check again: open the guided dialog (Connect custom domain, or Guided setup next to the domain). It names the exact record that is missing, or shows Waiting for certificate while the certificate is issued. DNS changes usually show within minutes, and Chipp keeps checking automatically
”The domain is already registered”
This domain is already connected in Chipp. Each domain can only be used once.
”Reserved example or test domain” or “not a valid public domain name”
Chipp cannot connect example and test names, such as anything ending in example.com, example.net or example.org, or names under .test, .example, .invalid or .localhost. Enter a real domain you own, for example chat.yourcompany.com.
Domain Not Working After Adding
- Remove proxy: If using Cloudflare, disable proxy (use DNS only) on both records
- Check DNS: Verify both CNAME records are present and correct
- HTTPS required: Access via
https://nothttp://
Removing a Custom Domain
To remove a custom domain:
- Go to Launch > Share
- Click the trash icon next to your domain, then click Confirm
- Your app reverts to the default
yourbuild.chipp.aiURL
After removing, you should also delete both DNS records from your registrar.
Best Practices
Subdomain Naming
Choose a subdomain that makes sense:
| Good | Why |
|---|---|
chat.brand.com | Clear purpose |
ai.brand.com | Modern, concise |
assistant.brand.com | Descriptive |
help.brand.com | Support-focused |
Backup Access
Keep your default yourbuild.chipp.ai URL bookmarked as a backup in case of DNS issues.
Ready to build it?
Tell Chipp what you want. Start free, or book a session and build it with our team.