Custom Domains and Certificates — SimtoLink IoT Cloud Platform

CNAME · HTTPS · Automatic renewal · Your own brand

1. Scenario Overview

White-label operations swap the logo and colors, but the domain and certificate a visitor sees are what make the brand feel like their own. On the SimtoLink IoT Cloud Platform, a customer points portal.customer.com at the platform edge with a CNAME. The platform requests and renews a Let's Encrypt or commercial DV/OV certificate. The admin console and the end-user portal can each sit on their own hostname. Configure this with the user self-service platform and online payment integration, including the payment callback domain, so checkout still completes after the white-label cutover.

The same checks used across SaaS apply. Prove domain ownership with a DNS TXT record or a file check. Retry renewal several times before the certificate expires, and alert if it still fails. Enforce HTTPS, and send HSTS.

CNAMESelf-service binding
HTTPSAutomatic certificates
RenewalAlert before expiry
Security headersHSTS/CSP

2. Core capabilities

Domain onboarding wizard

Step through adding the CNAME and TXT records at the DNS provider. The platform checks whether the names have resolved. When a conflicting record or a long TTL gets in the way, it suggests a fix.

Certificate policy

Let the platform hold the certificate, or upload one you already own. A wildcard certificate covers several subdomains. The notes also cover how to place the certificate when a CDN or WAF sits in front.

One domain on every client

H5 pages, pages embedded in a WeChat Mini Program, and in-app WebViews share one authorized domain. That meets whitelist rules such as the WeChat JS-SDK.

Monitoring

Watch the days left on the certificate and detect DNS changes. When something breaks, escalate with SLA and technical support.

3. Domains, certificates, and the visual theme

Visual branding is covered in Brand assets and themes. Domains and certificates handle trust and the name shown in the address bar. Together they are the white-label experience.

4. Where teams use it

  • A brand domain on the white-label portal: An MVNO binds the user self-service site to iot.customer.com. HTTPS is renewed without a manual step. The address bar shows the customer's domain, not a SimtoLink hostname, which is what builds trust.
  • WeChat Mini Program and H5 on one authorized domain: Add the custom domain to the WeChat JS-SDK whitelist. The H5 top-up page and the page inside the Mini Program share that hostname, so white-labeling does not drop payment callbacks or trip WeChat's security checks.
  • Private cloud on the enterprise network: For an on-premises deployment, use an internal domain and the customer's own CA. Finance and government buyers often need control of the domain and MLPS (等保) compliance. Customers can upload a self-signed certificate.

5. How to put it in place

Before production cutover, run payment and login callbacks end to end on a staging domain. Lock down the certificate private key, and do not send it in a plain email.

6. What changes for the brand

A custom domain and certificate raise brand trust: the address bar shows the customer's name, not the SaaS vendor behind the portal. Automatic issuance and renewal remove the expired-certificate outage, and HSTS plus security headers give security and compliance reviews something concrete to check. Tie the hostname to payment callbacks and the WeChat domain whitelist so the core flows still work after white-labeling.


Ready to serve the portal on a domain your customers already trust?

Talk with a SimtoLink specialist about CNAME cutover, certificate renewal, and a tailored IoT SIM management platform — including preferential pricing.

Request a consultation