Help Center

White-label Custom Domain with CNAME and HTTPS

Back to Website Contact Support
Signmitra
screen pairing getting started playlist timing calendar sync device offline pair tv screen signmitra offline playback create schedule playlist account setup create playlist
Partners

White-label Custom Domain with CNAME and HTTPS

Connect a partner-owned hostname to SignMitra using CNAME, verify DNS and complete secure HTTPS provisioning.

Share Email
Overview

A white-label partner can use a hostname such as signage.partnerdomain.com without moving SignMitra hosting. The hostname points to the SignMitra tenant endpoint and is provisioned securely on the platform.

Who should use this guide

Use this guide when the partner controls its DNS and wants customers to access the branded platform from its own domain.

Important points

  • Enter only a hostname, not https://, a path or query string.
  • Create a CNAME record from the chosen hostname to partner.signmitra.com with a temporary TTL such as 300 seconds.
  • Do not proxy the record through another CDN during initial verification unless explicitly supported.
  • After DNS resolves correctly, SignMitra must provision the exact host in Plesk/routing and issue a valid SSL certificate.
  • Keep the normal SignMitra login available until the dashboard reports the custom domain as Live.
Important: DNS verification alone does not guarantee HTTPS. Do not send the custom address to customers until both DNS and certificate status are successful.
Step by Step Guide
Step 1: Choose the hostname

Use a dedicated subdomain such as signage.example.com or cms.example.com. Avoid the root domain if it already hosts the partner website.

Step 2: Save it in the partner profile

Open the white-label partner domain settings, enter the hostname only and save the configuration.

Step 3: Create the DNS record

At the partner DNS provider, create CNAME signage (or the selected label) pointing to partner.signmitra.com. Use a low TTL while configuring.

Step 4: Wait for public DNS

Allow DNS propagation, then confirm the public CNAME resolves to the required target. Local browser cache may take longer than authoritative DNS.

Step 5: Run Verify DNS & HTTPS

Use the partner dashboard verification action. Review DNS, routing and certificate statuses instead of relying only on a browser redirect.

Step 6: Complete platform provisioning

After DNS is valid, SignMitra provisions the host alias/routing and SSL certificate. Re-run verification until the status is Live.

Step 7: Test the branded domain

Open the domain in a private browser window, verify HTTPS, login, password recovery, assets, API calls and logout on desktop and mobile.

Frequently Asked Questions
What should the CNAME point to?
Point the selected partner hostname to partner.signmitra.com unless the partner dashboard displays a different assigned target.
No. Enter only signage.example.com. SignMitra controls the protocol and application routes.
The DNS record is correct, but the exact hostname still needs platform routing and a valid SSL certificate. Wait for or request SignMitra provisioning, then verify again.
Normally no. SignMitra provisions and renews the certificate for the verified hostname on its infrastructure.
A subdomain is recommended because standard CNAME records at the root can conflict with website and mail DNS.
Was this article helpful?
Related Articles
  • No related articles.
Search Other Topics
Still need help?

Our team can help you with setup, device pairing, scheduling, and billing.

Contact Support Book a Demo
© 2026 Help Center.