---
title: "Your own domain"
description: "Run your seat maps and checkout on a subdomain you own, free, with two DNS records added in one visit. The certificate is automatic, and every state is shown."
---

Put your [ticket site](/sell/ticket-site/) on an address you own, such as
`tickets.yourclub.com`: your event pages, with the seat map and checkout, open
there. First choose your name in **Settings › Branded links**: the domain
serves your pages only once the name is set. Then you add two DNS records in
one visit, and the certificate is automatic. Most domains are live within a few minutes. Your
`seatlayer.events` address keeps selling while you wait, and links to it keep
working after you move.

Use a subdomain, not your main website address. A club can have up to 5 domains.
It needs no code, and the domain is free: no monthly fee on top of the $0.50 a ticket.

## What opens on your domain

| Page | Where it opens |
|---|---|
| Each event's page, with the seat map and checkout | Your domain |
| A home page that lists your events | Your domain, once you publish a Website |
| The tickets page, and the ticket link in emails | Your domain, while it is served; otherwise your `seatlayer.events` address |
| A season's page, from the season links in your dashboard | Your domain, while it is served; otherwise your `seatlayer.events` address |
| A run of dates | Its Share link is the next date's event page. That page and the run's own page open on your domain, while it is served. |
| Renewal pages | `app.seatlayer.io` |
| Guests' personal links | Your `seatlayer.events` address, also after your domain is served |

## Where buyers land after paying

A buyer who checks out on your domain pays on your gateway's payment page, then
comes back with the booking confirmed:

| What they paid for | Where they come back |
|---|---|
| A single event, a season or a run of dates, bought on your domain, with Stripe, PayPal, Mollie, Tap or Checkout.com | The same page on your domain |
| A single event, a season or a run of dates, with any other gateway | The same page on `app.seatlayer.io` |
| Seats through a guest link | The guest's page on your `seatlayer.events` address |
| A renewal, or seats through a private access link | `app.seatlayer.io` |

Every page above shows your logo and colour, and none of them shows a
SeatLayer logo or badge. Ticket links sent before your domain was served keep
opening where they were sent. Emails go out in your name, with your reply-to
([Emails in your name](/sell/club-email/)), sent from a SeatLayer mail address.

## Add the domain

<Steps>
  <Step title="Choose your name">
    Open **Settings › Branded links** and choose your name, such as
    `wrenmoorfc`. It also gives you `wrenmoorfc.seatlayer.events`. Skip this if
    you have already chosen one.
  </Step>
  <Step title="Enter your subdomain">
    Open **Settings › Ticket site › Your address**, enter it, such as
    `tickets.yourclub.com`, and choose **Add domain**. Nothing is reserved
    yet: the page shows the two records to add.
  </Step>
  <Step title="Add both records at your domain host">
    ```text
    tickets.yourclub.com             CNAME  sites.seatlayer.events
    _seatlayer.tickets.yourclub.com  TXT    seatlayer-verify=…
    ```
    Copy the TXT value from the page. It is unique to your account and that
    domain, and it shows the domain is yours.
  </Step>
  <Step title="Connect">
    Choose **I've added them, connect**. SeatLayer checks **Record found**,
    **Secure certificate** and **Live for customers**. While the page is open
    it reads the domain again every minute, and it also reads it again on its
    own after you leave.
  </Step>
</Steps>

## At your domain host

| Setting | What to use |
|---|---|
| Proxy | If your DNS is on Cloudflare, set the CNAME record to **DNS only** (grey cloud), not Proxied. |
| TTL | Auto is fine. If your host asks for a number, use 300 (5 minutes). |
| Name | Some hosts add your domain to the name for you. There, enter only the part before it: `tickets` and `_seatlayer.tickets`. |

Keep the `_seatlayer` record for as long as you use the domain. SeatLayer
reads it again every few hours, and stops serving the domain if it is gone.

## If connecting takes longer

- **"We can't see the _seatlayer record yet."** A new record can take up to
  30 minutes to show. DNS resolvers remember a "no such record" answer for a
  while, so a record added a minute ago may not be visible yet. The page tries
  again every minute while it is open.
- **Still "Setting up" after 15 minutes.** Under the records, the page lists
  one more TXT record, named `_cf-custom-hostname.tickets.yourclub.com`, for
  this case only. Add it too, then choose **Check now**.

## What each state means

| State | What it means | What to do |
|---|---|---|
| Setting up | We are waiting to see your records, or the certificate is on its way. | Nothing. It is read again on its own. |
| Needs a fix: points somewhere else | The CNAME record points somewhere other than `sites.seatlayer.events`. | Make it exactly the record on the page, then choose **Check now**. |
| Needs a fix: certificate blocked | Your domain's CAA record blocks the certificate. | Allow Cloudflare's certificate authorities in your CAA record. |
| Connected | The domain works, and event pages open there. It has no home page yet. | Publish a Website to give it one. |
| Live | Customers are on your domain. | Nothing. |

If a live domain stops working, for example because the `_seatlayer` record
was removed, the domain is no longer served and your admins get an email.
Your `seatlayer.events` address still works. Ticket links sent on the domain do
not open while it is not served; tickets still scan at the door.

## Remove a domain

Choose **Remove**, then **Remove domain**. Customers go back to your
`seatlayer.events` address. Links on the domain stop opening, including ticket
links already sent to customers, and adding the domain again does not bring
them back. Tickets still scan at the door.