Custom Domain Shortener Setup｜Branded Link CNAME
Last updated: 2026-06
Binding your own domain in 連 takes three steps: add your domain in the dashboard, prove ownership with a single DNS TXT record, then CNAME the domain to link.luvai.net, where Cloudflare for SaaS issues the SSL certificate automatically. Your branded short link (for example go.yourbrand.com) is then live. This page breaks down each step and explains why, after Taiwan's NCC SMS rule, a custom branded domain is more compliant than a free public shortener.
What is a branded short link, and why use your own domain?
A branded short link swaps the shortener's domain for your own (for example go.yourbrand.com) instead of sharing a third-party public domain. Before anyone clicks, they see your brand, which builds more trust.
In 連, your short links, click data and audience data all live in your own Cloudflare D1, not a third-party cloud. Paired with a custom domain, the whole redirect chain sits under your brand and your infrastructure.
Three steps to bind a custom domain (add → TXT verify → CNAME)
Step 1: Add the domain you want to use in the 連 dashboard, for example go.yourbrand.com.
Step 2: Following the dashboard instructions, add a DNS TXT record at your DNS provider to prove you own the domain.
Step 3: Point the domain to link.luvai.net with a CNAME record. Once done, Cloudflare for SaaS issues the SSL certificate for your domain automatically, and your branded short link starts working.
NCC SMS rule: why a free public shortener no longer complies
Taiwan's NCC SMS-whitelist rule, effective 2025/11/18, requires enterprise SMS to use an enterprise-owned domain. That means a free public shortener no longer complies.
Switching to a custom branded domain meets this requirement. Once you bind your own domain in 連 (for example go.yourbrand.com), the short links in your enterprise SMS use your own domain.
One-time setup before going live (an honest note)
To make a custom domain actually go live, the operator first needs a one-time setup: enable Cloudflare for SaaS and set a CF API token.
This is a one-time action. After it's done, adding and binding domains stays the three-step flow above. If it isn't enabled yet, handle this first before doing TXT verification and the CNAME.
FAQ
What steps are needed to bind a custom domain?
Three steps. First, add your domain in the 連 dashboard (for example go.yourbrand.com). Next, add a DNS TXT record at your DNS provider to prove domain ownership. Finally, point the domain to link.luvai.net with a CNAME record. After that, Cloudflare for SaaS issues the SSL certificate automatically and your branded short link goes live. The flow is just add, verify, point — follow the dashboard instructions.
Why does the NCC SMS rule require a custom domain?
Taiwan's NCC SMS-whitelist rule took effect on 2025/11/18 and requires enterprise SMS to use an enterprise-owned domain, so a free public shortener no longer complies. A custom branded domain meets the requirement. Once you bind your own domain in 連, the short links in your enterprise SMS use your own domain, keeping you on the right side of the rule.
Do I have to handle the SSL certificate myself?
No manual certificate request is needed. Once you've added the domain, verified it with the DNS TXT record, and pointed it to link.luvai.net via CNAME, the SSL certificate is issued for your domain automatically by Cloudflare for SaaS. You just get the DNS settings right, and the certificate is handled for you.
Where is my click and audience data stored?
In your own Cloudflare D1, not a third-party cloud. Your short links, click records and audience data all sit on your own infrastructure. Paired with a custom branded domain, the entire redirect chain belongs to your own brand and account.