> ## Documentation Index > Fetch the complete documentation index at: https://help.agentsy.pro/llms.txt > Use this file to discover all available pages before exploring further. # Custom Domains > Connect your own domain or subdomain to your Agentsy AI Experience, verify DNS, and troubleshoot common connection issues. # Custom Domains Your AI Experience can live at a branded web address, making it easier for visitors to recognize and trust your business. For example, instead of sharing an Agentsy-hosted address, you may choose a subdomain such as `ask.example.com` or `advisor.example.com`. A custom domain changes **where visitors access your experience**. It does not change the assistant's instructions, knowledge, or access permissions. > [!NOTE] > > Custom-domain availability and setup options may depend on your Agentsy plan and account configuration. Check the options shown in your workspace before changing DNS records. ## Before you begin Make sure you have: * An AI Experience configured in Agentsy. * A domain you own or are authorized to manage. * Access to the domain's DNS settings through your registrar or DNS provider. * The exact DNS record details provided by Agentsy for your custom domain. If someone else manages your organization's DNS, you can share the required record details with them. ## Choose your domain address A **subdomain** is often the simplest option for a dedicated AI Experience: | Address | Example use | | - | - | | `ask.example.com` | A public expert assistant | | `advisor.example.com` | A branded advisory experience | | `help.example.com` | A support-focused experience | You may also want to use a root domain such as `example.com`. Root-domain setup can require different DNS records and may not be supported by every configuration. Confirm what Agentsy offers before making changes. > [!TIP] > > Choose a short, memorable address that reflects the experience's purpose. A subdomain also lets you keep your existing main website unchanged. ## Step 1: Add the domain in Agentsy 1. Sign in to your Agentsy workspace. 2. Open the AI Experience you want to publish under your domain. 3. Locate its website or domain configuration options. 4. Enter the domain or subdomain you want to connect. 5. Save the configuration and review the DNS instructions displayed for your domain. > [!WARNING] > > Use the **exact record type, host/name, and target/value shown by Agentsy**. Do not copy DNS targets from another customer's setup or use a guessed IP address. ## Step 2: Configure DNS with your provider Open the DNS management page for your domain. Depending on the instructions shown in Agentsy, you may need to add or update a record such as a `CNAME`, `A`, or another verification record. For each record, check the following fields: | Field | What it means | | - | - | | **Type** | The DNS record type required by Agentsy | | **Name / Host** | The domain label to configure, such as `ask` for `ask.example.com` | | **Target / Value** | The destination or verification value supplied by Agentsy | | **TTL** | How long DNS resolvers may cache the record; use your provider's default unless instructed otherwise | DNS providers label these fields differently. Some ask for only the subdomain label (`ask`), while others accept the complete hostname (`ask.example.com`). Follow your provider's format. Before saving, check for an existing record with the same name that might conflict with the new record. Avoid deleting unrelated DNS records used by your main website, email, or other services. ## Step 3: Verify the connection After saving the DNS changes: 1. Return to the domain settings in Agentsy. 2. Check the domain's connection or verification status, if available. 3. Allow time for DNS changes to become visible across networks. 4. Open the new address in a private browsing window. 5. Confirm it displays the correct AI Experience. DNS changes may appear quickly, but propagation and caching can sometimes take longer. A domain that does not work immediately is not necessarily misconfigured. ## Step 4: Confirm HTTPS is working Visitors should access your AI Experience over **HTTPS**, which encrypts traffic between their browser and the website. Once your domain is connected, test: * The page opens using `https://`. * The browser does not display a certificate or security warning. * Images, styles, and other assets load correctly. * The AI Experience's sign-in, registration, and chat flows work on the custom domain. > [!NOTE] > > Certificate provisioning and activation may take additional time after DNS verification. If HTTPS is not ready, avoid sharing the domain publicly until it is working correctly. ## Step 5: Test the complete visitor journey A domain can resolve successfully while parts of the experience still need attention. Test the following before launch: * [ ] The custom address opens the intended AI Experience. * [ ] The website logo and navigation lead to the correct public pages. * [ ] Calls to action open the expected destination. * [ ] Guest chat works if enabled. * [ ] Registration and sign-in work as expected. * [ ] The assistant can receive and answer messages. * [ ] Public or invite-only access rules remain correct. * [ ] The experience works on mobile and desktop. * [ ] HTTPS works without browser warnings. > [!TIP] > > Test in a private browsing window so an existing administrator session does not hide issues that a new visitor might encounter. ## Troubleshooting | Problem | What to check | | - | - | | **Domain is not resolving** | Confirm the DNS record name and value match Agentsy's instructions. Allow time for DNS propagation. | | **Wrong website appears** | Look for conflicting records, redirects, or an old hosting configuration for the same hostname. | | **Domain remains unverified** | Check whether the required verification record exists and is publicly visible. | | **HTTPS or certificate warning** | Confirm DNS is correct and allow time for certificate provisioning; contact support if the issue persists. | | **Registration redirects unexpectedly** | Test the complete authentication flow and confirm the correct public-domain routing. | | **Domain works for you but not others** | Check DNS caching, provider settings, and propagation across networks. | | **Website loads but chat fails** | Test in a private window and review the assistant's configuration and access settings. | ### If you use Cloudflare or another DNS proxy Some DNS providers offer proxying, redirect rules, or additional security settings. These can affect verification or routing. If Agentsy provides provider-specific instructions, follow those instructions rather than assuming a proxy should be enabled or disabled. ## Changing or removing a custom domain Before changing a domain already used by visitors: 1. Plan where existing links should lead. 2. Configure and test the replacement address. 3. Update links in emails, websites, social profiles, and marketing materials. 4. Remove or change old DNS records only when you understand what they support. Avoid switching a live domain without testing, especially when users rely on registration links or saved bookmarks. ## When to contact support Contact Agentsy support if the DNS records match the provided instructions but the domain still cannot be verified, if HTTPS remains unavailable, or if visitors are redirected to the wrong tenant or sign-in page. Include your custom hostname, the issue you're seeing, and any relevant error message. **Do not share passwords, API keys, or other secrets.** ## Related guides * [Customize Your AI Website](/branding-and-website/customize-your-ai-website) * [Logo and Brand Colors](/branding-and-website/logo-and-brand-colors) * [Public and Private Access](/create-and-configure/public-and-private-access) * [Guest Chat and Registration](/create-and-configure/guest-chat-and-registration) * [Domain and SSL Issues](/troubleshooting-and-support/domain-and-ssl-issues) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.