> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.mythos.new/publishing/custom-domains/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.mythos.new/_mcp/server. # Custom domains > Connect a domain you already own to a published Mythos project and follow its DNS and HTTPS status from the workspace. A custom domain lets people open your published site at an address you own, such as `www.yourbrand.com`. The project also keeps its Mythos `*.r21.dev` address. > **Note** > > Mythos connects domains you already own. It does not register or sell domain > names. ## Before you start You need: * a Mythos project with a completed Build; * an active **Pro or Business** subscription; * permission to manage publication for the project; * a domain registered with a DNS provider; * permission to change that domain's DNS records. If the controls are unavailable, ask a workspace owner or admin to review your project and publishing access. A paid plan does not grant permissions by itself. See [People and permissions](/features/people-and-permissions). You can prepare the domain before the first publish. It begins serving the site only after the project is published and the domain shows **Connected**. ## Connect a domain #### Open Domains In the project workspace, select **More → Domains**. You can also start from **Add domain** in the Publish panel. #### Enter the hostname Under **Custom domains**, select **Connect domain** and enter the exact address you want to use, such as `www.yourbrand.com`. #### Add the ownership TXT record Mythos first shows one TXT record named `_mythos-challenge.`. Sign in to your DNS provider and copy its exact name and value. This record proves control of this connection; do not add `https://` or a page path. #### Verify domain ownership Return to Mythos and select **Check**. Mythos waits for the exact public TXT value before creating the Cloudflare hostname. DNS changes are not always immediate, so you may need to wait and check again. #### Add the connection records After ownership is verified, Mythos replaces the ownership instruction with the CNAME and any HTTPS validation records required for this domain. Copy every displayed name and value exactly. #### Check DNS and wait for HTTPS Select **Check** again after the connection records are public. Mythos then prepares HTTPS. The domain is ready to share when its status becomes **Connected**. Disconnecting and reconnecting the same hostname creates a fresh ownership TXT challenge. A TXT value from an earlier connection cannot verify the new connection. ## Understand the status | Status | What to do | | ----------------------- | ---------------------------------------------------------------------------- | | Verify domain ownership | Add the one displayed TXT record, then select **Check**. | | Add DNS records | Add or correct the displayed CNAME and HTTPS validation records. | | Checking DNS | Wait while Mythos checks the public DNS configuration. | | Issuing certificate | DNS is valid; wait for HTTPS to finish. | | Connected | The domain is ready and will serve the project while it is published. | | Needs attention | Read the message, correct the displayed records, and select **Check** again. | If you connect more than one domain, select **Make primary** on the address you want to present as the main custom domain. ## Domain and publishing behavior * The project must remain published for either the custom domain or its `*.r21.dev` address to work. * Updating the published site updates every connected domain for that project. * Changing the Mythos subdomain does not disconnect your custom domains. * Unpublishing the project stops the site on all of its addresses. Custom domains are paused on Free; the published Mythos URL remains available. Review your [plan](/introduction/credits-and-usage) before changing a subscription that serves a live domain. ## Disconnect a domain Use **Disconnect** beside the hostname in **More → Domains** at any stage. This removes the domain from the Mythos project, but it does not change or delete records at your DNS provider. Remove those records there if you no longer need them. > **Warning** > > Disconnecting a domain breaks links that use that address. Confirm that > another working URL is available before removing a domain that visitors > already use. ## Troubleshooting #### Domain ownership is still not verified Compare the one displayed TXT name and value with the public DNS record. The name must match `_mythos-challenge.` exactly. If you disconnected and reconnected the domain, remove the earlier challenge and use the fresh value shown by the current connection. #### DNS is still not verified After ownership verification, compare every displayed connection record with your public DNS. Some providers automatically append the root domain to a name, and some require ALIAS, ANAME, or CNAME flattening for the root domain. DNS changes can also take time to appear publicly. #### DNS is valid, but HTTPS is not ready Certificate setup starts after DNS verification and may take longer. Leave the records in place and select **Check** again later. #### The domain is connected but the site does not open Confirm that the Mythos project is currently published. A connected domain does not serve a private or unpublished project. ## Related * [Publish your site](/publishing/publish) — put the project online and update it later. * [SEO & AI search](/publishing/seo) — review how search engines can understand the live site. > Learn how to turn an idea into a working app, improve it in Mythos, and publish it when it is ready.