ccnames.dev

cnames.dev / for / link in bio and short links

Custom domains for link-in-bio & short links

Let users bring vanity domains to your link-in-bio or short-link product, with automatic SSL and fast edge redirects.

The problem

Link-in-bio pages and URL shorteners live or die on brand: creators and businesses want links.creator.com or go.brand.com, not a shared subdomain. Each vanity domain needs a certificate and a fast redirect/serve path — and you may be adding hundreds of them a week.

How it plugs in

Point each vanity domain at your origin with one API call. Because cnames.dev terminates TLS at the edge and forwards the real client IP and country, your click analytics and geo features keep working behind the custom domain.

await fetch("https://api.cnames.dev/v1/domains", {
  method: "POST",
  headers: { Authorization: "Bearer sk_live_...", "Content-Type": "application/json" },
  body: JSON.stringify({ domain: "go.brand.com", origin_id: "org_shortener" }),
});
// Your origin receives X-Client-IP and X-Country for accurate analytics.

Why it fits

Add it this afternoon. Register your first customer domain with one API call — free for 25 domains. Start free · Docs · More use cases

Frequently asked questions

What is a vanity domain here?

A short, branded domain a user brings to your product — e.g. links.creator.com for a link-in-bio page, or go.brand.com for a URL shortener — served with automatic SSL.

Do short links need anything special?

They need fast edge redirects and SSL on the custom domain. cnames.dev terminates TLS at the edge and forwards the real client IP and geo to your origin so your analytics stay accurate.

Can each user have many vanity domains?

Yes. Register as many as you like via the API; per-tenant quotas keep usage predictable and billing simple at ~$0.05/domain.