Docs menu

Use your own domain

Open your published app at a domain you own, such as example.com or shop.example.com. crisp shows the exact DNS record to add, checks it for you, and sets up the secure (https) certificate.

Updated

On this page

Every published app has its own crisp address. You can also connect a domain you own, so people open your app at your name. Your app keeps its crisp address too.

Connect a domain#

  1. Publish your app first. See Publish your app.
  2. Press Published in the top bar. Under Your domain, press Connect a domain.
  3. Type the domain, for example shop.example.com or example.com, and press Connect. For a root domain such as example.com, keep Also connect www.example.com ticked to have both.
  4. crisp shows the DNS record to add. Add it where your domain's DNS is managed: usually the company you bought the domain from, or Cloudflare if you moved it there.
  5. Keep the panel open, or come back later. crisp checks the record every few seconds and shows each step.

The record to add#

For a subdomain such as shop.example.com, add one CNAME record. Its name is the part before your domain (shop), and its value is your app's crisp address, which the panel shows with a copy button.

A root domain such as example.com cannot have a normal CNAME record. Add one of these instead:

  • ALIAS, ANAME or a CNAME at the root, pointing at your app's crisp address. Cloudflare, DNSimple, Netlify DNS and others support this. It is the better choice, because it keeps working if crisp's addresses change.
  • A records, one for each address the panel lists, if your provider has no ALIAS option. The name is @.

What each step means#

You seeWhat it means
Waiting for DNScrisp has not seen your record yet. New records usually appear within minutes. Some providers take up to an hour.
Issuing certificateThe record is right. crisp is getting the secure (https) certificate. This usually takes under a minute.
LiveYour domain opens your app, with https.
Needs a fixSomething is wrong, and the panel says what to change. For example, the record points somewhere else, or the Cloudflare proxy is on.

Let crisp add the record at Cloudflare#

If your domain's DNS is at Cloudflare, crisp can add the record for you. Press Let crisp add the record, then paste a Cloudflare API token made with the Edit zone DNS template for your domain. crisp keeps the token encrypted, never shows it again, and uses it only to add and remove the records for your domains. If a record already exists for the name, crisp shows it and asks before it replaces it.

www and the root domain#

When you connect example.com with Also connect www.example.com ticked, both names open your app. To send everyone to one address instead, which search engines prefer, add a redirect at your DNS provider. At Cloudflare, use Rules, then Redirect Rules, and the Redirect from WWW to root template. Most registrars call this "forwarding".

Remove a domain#

Press Published, then Remove domain under the domain, and confirm. Your app stops answering at that domain and keeps its crisp address. Removing a root domain also removes its www name. If crisp added the DNS record at Cloudflare, it removes that record too. Otherwise, delete the record at your DNS provider yourself.

Deleting the project removes its domains as well.

If it does not work#

  • Check that you added the record where your domain's DNS is really managed: the provider your domain's nameservers point to.
  • Check that the name and value match the panel exactly, and that there is no older record for the same name.
  • If the certificate does not come after 15 minutes and your domain has a CAA record, add one that allows letsencrypt.org.
  • A domain can be connected to one app at a time. Remove it from the other app first.

Something wrong or missing on this page? Tell us. A person reads every message.

Report a problem