> ## 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 and DNS > Connect a branded domain to your Agentsy AI Experience, configure DNS safely, and troubleshoot domain and HTTPS issues. # Custom Domains and DNS A custom domain lets visitors access your Agentsy AI Experience through a web address associated with your brand—for example, `ask.example.com` instead of an Agentsy-provided subdomain. This guide explains how to prepare a domain, configure the DNS records provided for your experience, check HTTPS, and resolve common problems. > [!NOTE] > > The exact setup controls and DNS values depend on your Agentsy configuration and DNS provider. Always use the hostname and record values displayed in your Agentsy domain setup or supplied by Agentsy support. Do not copy example values from another customer's setup. ## Before you begin Make sure you have: * An Agentsy AI Experience that you can administer. * A domain you own or have permission to configure. * Access to the domain's authoritative DNS provider (which may differ from the company where you purchased the domain). * A preferred hostname, such as `assistant.example.com` or `ask.example.com`. * Time to verify the change before sharing the new link publicly. > [!TIP] > > A dedicated subdomain is often the simplest choice. It allows your main website at `example.com` to remain unchanged while your AI Experience lives at `ask.example.com`. ## 1. Choose the domain you want visitors to use There are two common approaches: | Address | Typical use | Consideration | | - | - | - | | `ask.example.com` | Dedicated AI Experience | Usually easier to configure without affecting your main website. | | `example.com` | AI Experience on the root domain | May require additional DNS or hosting changes and could replace an existing website. Confirm support before proceeding. | Choose a name that is easy to recognize, spell, and share. For an existing business website, a subdomain is generally the safer starting point. ## 2. Find your Agentsy domain configuration 1. Sign in to Agentsy and open the relevant AI Experience or its administrative settings. 2. Look for the available **domain**, **website**, or **branding** configuration. 3. Enter or confirm the custom hostname you want to connect, if that option is available. 4. Copy the DNS instructions shown for that hostname, including the **record type**, **name/host**, and **target/value**. 5. Keep the configuration available while you update your DNS provider. If you cannot find a custom-domain option, check whether it is available for your account and contact Agentsy support for the correct setup instructions. > [!WARNING] > > Do not guess the target hostname, IP address, or verification record. An incorrect record can prevent your AI Experience from loading or disrupt another service using that hostname. ## 3. Add the required DNS record Open the DNS management panel for your domain and create or update **only the records required by your Agentsy setup**. A DNS record commonly contains these fields: | Field | Meaning | | - | - | | Type | The record type, such as `CNAME`, `A`, or `TXT`, as specified in your setup. | | Name / Host | The hostname or label to configure. Some providers use `ask` for `ask.example.com`; others expect the full hostname. | | Value / Target | The exact destination or verification value supplied for your Agentsy configuration. | | TTL | How long resolvers may cache the record. The provider default is often suitable unless the instructions say otherwise. | For example, if you are connecting `ask.example.com`, your provider might ask you to enter `ask` in the **Name** field. This is an illustration of hostname formatting, **not** an Agentsy DNS target. ### Avoid conflicting records Before saving: * Check whether the chosen hostname already has an `A`, `AAAA`, or `CNAME` record. * Do not add a conflicting `CNAME` alongside other records at the same hostname. * Do not delete unrelated email records such as `MX`, `SPF`, `DKIM`, or `DMARC`. * If your DNS provider offers proxying or traffic acceleration, follow the Agentsy-specific instructions for whether it should be enabled. > [!WARNING] > > Changing the root domain or removing existing DNS records can interrupt your main website, email, or other services. If you're unsure which records are safe to change, consult the person managing your domain before proceeding. ## 4. Verify the connection After saving the DNS record: 1. Return to the relevant domain settings in Agentsy. 2. Use any available **verify**, **check**, or **connect** action, if provided. 3. Allow time for DNS changes to propagate. Timing varies by provider, cached records, and configuration. 4. Open the custom hostname in a private browsing window. 5. Confirm that it loads the **correct AI Experience**, not another website or a domain-provider parking page. If Agentsy doesn't offer a visible verification action, follow the instructions given in the setup flow or contact support to confirm the domain status. ## 5. Check HTTPS and SSL A public AI Experience should load over **HTTPS** so information sent between a visitor's browser and the website is encrypted in transit. When the domain is connected, test `https://your-hostname` and check that: * The browser does not display a certificate or privacy warning. * The address bar shows the expected hostname. * The landing page, registration or sign-in flow, and chat experience work. * Links and redirects stay on the intended domain where appropriate. > [!NOTE] > > DNS resolution and HTTPS certificate readiness are separate steps. A domain may resolve before its certificate is ready. Certificate provisioning and renewal behavior depend on the configured hosting and domain setup; don't assume they are complete until HTTPS works in your browser. ## 6. Test the complete visitor journey A successful DNS lookup is only the first check. Test the experience as a new visitor: * Open the custom-domain URL on desktop and mobile. * Confirm your branding, page content, and call-to-action buttons appear correctly. * Test guest access, registration, or invitation requirements according to your access configuration. * Start a test conversation and check that the assistant responds as expected. * Test any scheduling or human-handoff links. * Check links from your main website, emails, and social profiles. For additional launch guidance, see [Publish Your AI Experience](/share-and-grow/publish-your-ai-experience) and [Share Your AI Website](/share-and-grow/share-your-ai-website). ## Troubleshooting | Problem | What to check | | - | - | | Domain does not resolve | Confirm the record was saved at the authoritative DNS provider, with the correct host and target. Allow for DNS caching. | | Domain opens the wrong website | Look for an existing record, redirect, or hosting configuration associated with the same hostname. | | Domain verification is pending | Recheck the exact record values and whether your provider automatically appends the domain name. | | Browser shows an HTTPS warning | Confirm the domain is correctly connected and allow for certificate setup. Do not promote the link until HTTPS works. | | Domain works for some visitors but not others | Cached DNS records may differ. Recheck later and compare using another network. | | Redirect loop or unexpected sign-in page | Check the configured domain and access settings, then report the exact redirect sequence to support. | | Main website or email stopped working | Review any root-domain, `MX`, or other records changed during setup; involve your DNS administrator promptly. | ### What to send to support If the problem continues, include: * The custom hostname you are connecting. * Your DNS provider's name. * The record **type** and **host** you configured, plus the non-sensitive target value where appropriate. * Any verification or browser error message. * The approximate time you made the change. * Whether the problem occurs on both desktop and mobile. Never send account passwords, private keys, or other credentials in a support message. ## Custom-domain launch checklist * [ ] I own or am authorized to manage the domain. * [ ] I selected a hostname that does not conflict with an existing service. * [ ] I used the exact DNS values from my Agentsy configuration. * [ ] I verified that the domain loads the intended AI Experience. * [ ] HTTPS works without browser security warnings. * [ ] Registration, guest access, chat, and handoff links work as expected. * [ ] I updated the links I plan to share with visitors. ## Related guides * [Custom Domains](/branding-and-website/custom-domains) * [Publish Your AI Experience](/share-and-grow/publish-your-ai-experience) * [Share Your AI Website](/share-and-grow/share-your-ai-website) * [Public and Private Access](/create-and-configure/public-and-private-access) * [Domain and SSL Issues](/troubleshooting-and-support/domain-and-ssl-issues) > [!TIP] > > Your custom domain is ready to share when it reliably opens the correct AI Experience, HTTPS works, and the complete visitor journey has been tested. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.