Skip to content
English
More support
Chekin website
  • There are no suggestions because the search field is empty.

Custom Domains (White Label / Branding)

Custom Domains allow you to use a branded domain for the guest experience, instead of a Chekin default URL. This feature is included in the White Label / Branding package.

Once configured, the custom domain applies automatically to all reservation-related links, including:

  • Property links

  • GuestApp reservation links

  • Custom email templates

  • Automated reservation emails

  • Any communication that redirects a guest to their reservation



Quick summary

You can choose between two options:

  1. Chekin subdomain (recommended for speed)
    Example: yourbrand.portal.chekin.xyz
    ✔ No DNS changes required
    ✔ Instant setup

  2. Custom domain (your own domain)
    Example: checkin.yourdomain.com
    ⚠ Requires DNS configuration
    ✔ Full branding and trust


Why Custom Domains Matter

  • Brand trust: Guests see your own domain instead of a generic one

  • Higher conversion: Guests are more confident opening links

  • Consistency: Same domain across emails, links, and entry points

 

Where to Configure It

Go to:

White Label / Branding → New Template → Domains


Option A — Chekin Subdomain

What it is

A subdomain under Chekin’s domain:

{subdomain}.portal.chekin.xyz

Example:

villasol.portal.chekin.xyz

How it works

  1. Choose a subdomain name

  2. The system checks availability

    • If available → it is assigned immediately

    • If already in use → you must choose another name

When to choose this option

  • You want the fastest setup

  • You don’t want to manage DNS records

  • You don’t have technical support

Option B — Custom Domain (Customer-Owned Domain)

What it is

A domain that you own and manage. We strongly recommend using a subdomain, such as:

  • portal.yourdomain.com

  • checkin.yourdomain.com

 

Custom Domain Setup (Step-by-Step)

⚠️ This option requires access to your domain’s DNS provider (Cloudflare, GoDaddy, etc.).

Overview

To activate a custom domain, two CNAME DNS records are required:

  1. SSL certificate validation (AWS Certificate Manager)

  2. Final domain activation (CloudFront distribution)

Both steps must be completed in order.


Step 1 — Enter the Domain in Chekin

  1. Go to White Label / Branding → Domains

  2. Select Custom domain

  3. Enter your domain (example: checkin.yourdomain.com)

  4. Save

You will see:

  • Status: Pending Certificate Verification

  • Action Required: Add CNAME record to validate SSL certificate


Step 2 — Add CNAME for SSL Certificate Validation

Chekin will display the DNS record required to validate your SSL certificate.

DNS Record Details

  • Type: CNAME

  • Name: _token.yourdomain.com

  • Value: _token.acm-validations.aws

The exact values are generated automatically and shown in the UI.

Important DNS Note (Very Common Issue)

Many DNS providers only expect the host name, not the full domain.

For example:

  • Correct host: _token or _token.subdomain

  • Incorrect: _token.subdomain.yourdomain.com.yourdomain.com

If the domain is duplicated, SSL validation will fail.

Step 3 — Wait for Cloud Configuration

Once the SSL CNAME record is added:

  • Status changes to Waiting for Cloud Configuration

  • This step is automatic

  • Typical duration: 5–15 minutes

No action is required during this step.

Step 4 — Add Final CNAME (Domain Activation)

After SSL validation completes, you will see:

  • Status: Pending Distribution Domain

  • Action Required: Add final CNAME record

DNS Record Details

  • Type: CNAME

  • Name: yourdomain.com (exact domain entered in Chekin)

  • Value: xxxx.cloudfront.net

Example:

test-vlad.chekinapps.xyz → d7mlg189j7s7t.cloudfront.net

After adding this record:

  • The domain activates within 5–10 minutes

 

Step 5 — Domain Active

✅ Status: Active
✅ Setup Progress: 4/4 steps completed (100%)

Your custom domain is now live and used across all reservation links.

 

Domain Status Reference

Status Meaning
Pending Certificate Verification SSL validation CNAME missing
Waiting for Cloud Configuration Internal processing (5–15 min)
Pending Distribution Domain Final CloudFront CNAME missing
Active Domain fully operational

 

Troubleshooting

Issue: Stuck on "Pending Certificate Verification"

Common causes:

  • Record is not a CNAME

  • Host/name duplicated by DNS provider

  • DNS changes applied in the wrong provider

What to check:

  • Type = CNAME

  • Name/Host is correct

  • Value matches exactly

 

Issue: Stuck on "Waiting for Cloud Configuration"

This is normal for up to 15 minutes.

If it clearly exceeds that time:

  • Confirm the SSL CNAME still exists

  • Contact support with screenshots

 

Issue: Stuck on "Pending Distribution Domain"

Cause:

  • Final CloudFront CNAME missing or incorrect

Fix:

  • Ensure the CNAME points to *.cloudfront.net



Issue: Domain Active but Not Loading / HTTPS Errors

  • Make sure you are using the new domain URL

  • Try a different browser or incognito mode

  • If the issue persists, contact support

 

Support Checklist (Before Contacting Support)

Please provide:

  • Domain entered in Chekin

  • Current domain status

  • DNS provider name

  • Screenshots of both CNAME records

  • Approximate time when DNS changes were applied



Need Help?

If you are unsure about your DNS configuration, our Support team can quickly validate it if you share a screenshot of your DNS records.