Skip to main content

Connecting Your Domain to TangibleXP

Every TangibleXP application comes with a temporary domain (yourapp.tangiblelaunchpad.com) for use during setup. When you're ready to go live, you'll connect your own domain.

This page covers:

  • Adding your domain in the TXP dashboard
  • Configuring your DNS records to point your domain to TXP
  • Setting your domain as the primary address for your application

We recommend Cloudflare for DNS — it's free, and it handles both standard subdomains and apex (root) domains without extra plugins or workarounds. The steps below are written for Cloudflare, but the same record types apply to any DNS provider.

Before you begin​

You'll need:

  • A domain registered with a domain registrar (e.g. Namecheap, GoDaddy, Squarespace Domains)
  • Access to your DNS settings — if you're using Cloudflare, this is your Cloudflare dashboard
  • An existing application on TangibleXP

If you're in the process of migrating an existing site to TXP, complete the migration steps before setting up your domain. Domain setup is the last step of any migration.

Step 1: Add your domain in the TXP dashboard​

Before configuring DNS, register your domain with TangibleXP so the platform knows to route traffic to your application once the DNS change takes effect.

  1. Go to app.tangiblexp.com and open your application.
  2. Click Domains in the sidebar.

TXP application sidebar with the Domains navigation item highlighted

  1. Click Add Domain.
  2. Enter the domain you want to use — for example, www.yourdomain.com or yourdomain.com — and save.

TXP Add Domain form with a domain input field

Your domain is now registered with TXP. Traffic won't route to your application yet — that happens once your DNS records are in place.

Step 2: Configure your DNS records​

How you set up DNS depends on the type of domain you're pointing at TXP:

  • Subdomain — e.g. www.yourdomain.com or learn.yourdomain.com — uses a standard CNAME record
  • Apex domain — e.g. yourdomain.com with no prefix, also called a root domain — uses Cloudflare's CNAME flattening

Both are covered below.

Subdomain (www or custom prefix)​

  1. Log in to Cloudflare and select your domain.
  2. Click DNS in the sidebar, then click Add record.
  3. Set the record type to CNAME.
  4. In the Name field, enter the subdomain prefix. For www.yourdomain.com, enter www. For learn.yourdomain.com, enter learn.
  5. In the Target field, enter lb.tangiblexp.com.
  6. Set the proxy status to DNS only (the grey cloud icon). TangibleXP already manages a Cloudflare Enterprise layer — keeping the proxy off here prevents conflicts.
  7. Click Save.

Cloudflare Add Record form showing a CNAME record for www pointing to lb.tangiblexp.com with the proxy status set to DNS only

Apex domain (root domain)​

A standard CNAME record can't be placed at the apex (yourdomain.com with no prefix) — this is a DNS limitation. Cloudflare works around it with CNAME flattening, which lets you use a CNAME at the root and handles the resolution automatically.

  1. Log in to Cloudflare and select your domain.
  2. Click DNS in the sidebar, then click Add record.
  3. Set the record type to CNAME.
  4. In the Name field, enter @. Cloudflare uses @ to represent the apex domain.
  5. In the Target field, enter lb.tangiblexp.com.
  6. Set the proxy status to DNS only (the grey cloud icon).
  7. Click Save.

Cloudflare Add Record form showing a CNAME record for the apex domain pointing to lb.tangiblexp.com

note

Using a different DNS provider? Most providers support CNAME records for subdomains. For apex domains, you'll need one that supports CNAME flattening or ALIAS/ANAME records. If your current provider doesn't offer this, migrating your DNS to Cloudflare is free and won't affect your registrar.

Step 3: Set your domain as primary​

With the domain added to TXP and your DNS records configured, set it as the primary address for your application.

  1. In your TXP dashboard, go to Domains for your application.
  2. Find the domain you added and click Set Primary Domain.
  3. Select your new domain and confirm.

TXP Domains panel with the Change Primary button next to a domain entry

Your application now serves traffic on your own domain.

Waiting for DNS to propagate​

DNS changes don't take effect instantly. Updates typically propagate within a few minutes to a few hours, though in rare cases it can take up to 24 hours. During this window, some visitors may still see the old domain or a connection error — this is normal.

To check whether your DNS change has taken effect, use whatsmydns.net: enter your domain, select CNAME, and check whether the record is resolving to lb.tangiblexp.com globally.