---
title: Connect a custom domain
description: Serve your event from your own domain with DNS verification.
---

Every event gets a platform-managed address when it's created, but you can also serve it from a domain you own, such as `play.example.com` instead of the default URL. Connecting one takes two rounds of DNS work: first you prove you own the domain, then you point it at your event. The default address keeps working alongside your custom one.

Custom domains are managed at the workspace level and then attached to a specific event, so you'll work in two places: the **Domains** page in the sidebar's **Workspace** section, and the **Domains** tab inside your event's dashboard.

1. **Add your domain**

    On the workspace **Domains** page (**Your domains**), click **Add
    domain**, enter your domain (for example `play.example.com`) and click
    **Add domain**.

    Use lowercase letters, digits, dots, and hyphens only. If the save fails,
    the usual causes are a domain that's already in use on the platform, or a
    conflict with a parent or child domain you've already added (you can't
    hold both `example.com` and `play.example.com`).

2. **Prove you own it**

    Adding the domain opens its detail page, which starts as **"This domain
    still needs setup"** and lists the **Required DNS records**: a **TXT**
    record at `_site_verify.` followed by your domain, with a generated
    value. Copy the name and value with the row's copy buttons.

    Create the record at your DNS provider, then click the **Check again**
    button on the detail page. The domain then shows **Ready**, both here
    and in the status column of your domains list, where one still awaiting
    setup shows **Needs setup**. Only a **Ready** domain can be attached to
    an event in the next step.

3. **Point DNS at your event**

    Open your event's dashboard and go to its **Domains** tab. Click **Add
    domain** and pick your domain in the **Attach verified domain** dialog.
    It only lists domains that are **Ready** and not attached to another
    event, and your event must be active (fully provisioned) before you can
    attach anything.

    The **DNS setup** section then shows the routing record to create: a
    **CNAME** pointing your domain at the platform's target (shown with a
    copy button), or an **ALIAS** record if your domain is an apex like
    `example.com`. Create it at your DNS provider, then click **Check domain
    setup** in the **DNS verification** panel. The status flips from **Not
    checked** to **Verified** when the record resolves correctly, or **Not
    verified** if it isn't resolving yet. Apex setups pass as long as your
    provider's ALIAS/flattened record reaches the same place.

4. **Attach the domain**

    With DNS verified, click **Attach domain**. You'll see *"Domain
    attachment started. Your domain will be linked after setup finishes."*
    Linking runs in the background, and when it completes, the domain's row
    on your workspace Domains page gains an **Open event** link.

    Your event now answers on the custom domain. The event's original
    address stays up too, and the Domains tab lists it with a **Managed by us**
    badge, next to your own **Managed by you** domains. You can attach more
    than one custom domain to the same event, but each domain can only serve
    one event.

## Plan limits

Custom domains are counted per workspace: **1** on Hobby, **5** on Starter, **20** on Pro, and **50** on Enterprise (platform-managed event addresses don't count). At the limit, the **Add domain** button is disabled and the page shows **"Domain limit reached"** with your used/max count in parentheses, for example *"Domain limit reached (1/1)."* Your domain usage also appears on the **Usage** page.

On an attack/defence event, players can also register and sign in with a password from an attached domain. Sign-in with Google, GitHub or Athena still completes on the event's original address and brings the player back signed in.

## Detach a domain

The unlink button on an attached domain's detail page detaches it from its event. On an attack/defence event, the domain shows **Detaching** while the event stops routing and accepting sign-ins from it; it is released once that finishes, usually within a few minutes. If it stays on **Detaching**, detach again to retry. After an attack/defence event ends, its domain stays attached until the event's cleanup completes; detach it again then, and it's released straight away. On a jeopardy event, the domain is released at once, but the event can keep answering on it until the event's domains change again.

## Remove a domain

The trash button on a domain's row (or detail page) opens a delete confirmation. A domain that's attached to an event can't be deleted; detach it first, or wait for the event to be deleted. Deleting a domain removes it from your workspace; you can re-add it later, but you'll go through verification again.
