1. Add your domain
Open the URL shortener on the home page, expand Pro Settings and choose Custom Domain. Enter a subdomain you own, for example go.yourbrand.com, and click Add domain.
PRO FEATURE
Replace sli.ink/ with your own brand. Short links you create on a custom domain keep the full ShortLi feature set — passwords, expiry, geo-routing and analytics — while looking completely like you.
You only do the DNS part once. After that, every new link can use your domain in a single click.
Open the URL shortener on the home page, expand Pro Settings and choose Custom Domain. Enter a subdomain you own, for example go.yourbrand.com, and click Add domain.
In your DNS provider, create a CNAME record for your subdomain that points to sli.ink. Proxying the record (Cloudflare's orange cloud, Fastly and similar) is the recommended default so visitors always get a valid certificate. If verification does not pass with the proxy on, switch the record to DNS-only (grey cloud) and click Verify again — the CNAME becomes visible in DNS and is checked directly. Avoid using your bare apex domain (like yourbrand.com) — a subdomain is the simplest and most reliable option. See the note below.
Add a TXT record named _shortli-verify.yourbrand.com with the value shortli-verify=<your token>. The exact name and value are shown next to your pending domain after you add it. This prevents anyone else from claiming a domain they do not control.
Back in Pro Settings, click Verify on the pending domain. Once DNS has propagated (usually a few minutes), the domain turns verified. Select it for any new short link.
Pick your verified domain in the Custom Domain section, choose a slug, and create the link exactly like a normal one. Every feature — passwords, expiry, geo-routing and analytics — keeps working, and your short link is returned with your own domain.
The recommended setup is to front your custom domain with a TLS-terminating proxy. Your provider proxies the record and serves a valid certificate for your domain to visitors, so short links open without any browser warning. Cloudflare's free plan does this out of the box, and Fastly, CloudFront, Bunny and similar work too. Keep the CNAME proxied (orange cloud).
For the proxy-to-origin connection, set the SSL/TLS encryption mode to Full and not Full (strict). Full (strict) makes the proxy validate the certificate on our origin against your domain, which we do not issue, and links then fail with HTTP 526 Invalid SSL Certificate.
A proxied record hides the CNAME from public DNS, so during verification we confirm routing by reaching a ShortLi marker through your domain instead. Some proxies front the origin with bot protection, which answers that check with a challenge; we recognise the challenge as proof the record is proxied, so you do not need to disable anything.
If verification still does not pass, switch the record to DNS-only (grey cloud) and click Verify again: the CNAME becomes visible in DNS and is checked directly. Cloudflare often still serves the edge certificate for the hostname, so links keep working — leave it DNS-only, or switch back to proxied once verified.
For a domain such as go.yourbrand.com, add these two records at your DNS provider:
| Type | Name / Host | Value / Target |
|---|---|---|
| CNAME | go.yourbrand.com | sli.ink |
| TXT | _shortli-verify.go.yourbrand.com | shortli-verify=<your token> |
The exact TXT value is shown next to your pending domain after you add it on the home page — it is unique to your account and proves you own the domain.
Custom domains are a Pro feature. You need an active Pro subscription to add a domain and to attach it to links.
Yes. Slugs are unique per domain, so go.yourbrand.com/launch and links.yourbrand.com/launch can coexist, and either can also exist as sli.ink/launch.
The CNAME points your domain at ShortLi so redirects resolve, while the TXT record proves you control the domain. Requiring both keeps someone else from attaching a domain they do not own.
Often a few minutes, but propagation can take longer depending on your DNS provider and TTL settings. If verification fails, wait a little and click Verify again.
A subdomain (like go.yourbrand.com) is recommended because CNAME records are only valid on subdomains. If you must use an apex domain you will need an ALIAS/ANAME or a provider-specific flattening feature.
Set the SSL/TLS encryption mode to Full (not Full (strict)). Full (strict) makes Cloudflare validate the certificate on the ShortLi origin against your domain; we do not issue certificates for customer domains, so the check fails with 526. Use Full instead.
Proxying is the recommended default: front the domain with a TLS-terminating proxy such as Cloudflare (free plan works), Fastly or CloudFront, and keep the record proxied (orange cloud). A proxied record hides the CNAME from public DNS, so we confirm routing by reaching a ShortLi marker through your domain instead. If verification does not pass while proxied, switch the record to DNS-only (grey cloud) and verify again — the CNAME becomes visible in DNS and is checked directly, and Cloudflare still serves the certificate for the hostname. You can switch back to proxied afterwards.
A domain that still has links attached cannot be removed. Delete or move those links first, then remove the domain.
Upgrade to Pro, add your domain, and start sharing short links that carry your own name.