URL Shortener Custom Domain: Access vs. Real Ownership

Hands plugging a network cable into the back of a server rack.

Written by

fastreader@pm.me

in

A url shortener custom domain is really two different products wearing the same name: one where a hosted service lets you point your domain at their system and charges monthly for the privilege, and one where you own the domain, the server, and the redirect logic outright. The distinction that matters isn't whether a plan "supports" custom domains — nearly all do above the free tier — it's whether your links still work if you stop paying.

TL;DR:

  • "Custom domain support" and "custom domain ownership" are different things — most hosted plans gate the feature behind a paid tier but keep the redirect logic on their servers, not yours.
  • At the DNS level, a custom domain almost always means pointing a CNAME record at the shortener's infrastructure, a change that can take minutes to apply and up to 48 hours to fully propagate.
  • Pew Research Center found that 38% of webpages from 2013 are no longer accessible — link rot is a documented, measurable problem, not an abstract fear.
  • Self-hosting removes per-domain fees and domain caps entirely, because the server and database are yours, not rented.
  • Password protection, A/B split testing, and logo-embedded QR codes are worth checking for separately — custom domain support doesn't guarantee any of them.

Table of Contents

URL Shortener Custom Domain Support: Access vs. Ownership

Almost every hosted link shortener above its free tier will let you "add a custom domain." That phrase does a lot of quiet work. What it usually means is that the company's servers will answer requests for yourdomain.com and redirect them according to rules stored in their database, under their account, on their infrastructure. You're not hosting a shortener with a custom domain — you're renting a slot on theirs.

That distinction only becomes visible at the worst possible moment: when you cancel, when they raise prices, or when they get acquired and quietly sunset the product. The domain is still yours in the registrar sense, but every short link pointing through it stops resolving the second the underlying service goes dark. If you've printed that domain on packaging, business cards, or a QR code on a storefront window, you don't get to fix it by Tuesday. For a full rundown of what's actually possible without that dependency, see the real options for shortening a URL with your own domain.

Pro Tip: Before you commit to any plan advertising custom domain support, ask what happens to existing short links if you downgrade to a lower tier mid-contract — not just if you cancel outright. Several services disable custom domain redirects immediately on downgrade, which breaks live links with zero warning.

What Happens at the DNS Level When You Point a Domain at a Shortener

A person examining a wall of network patch panels and cables in a data center.

Setting up a custom domain isn't magic — it's one DNS record. You create a CNAME entry, typically for a subdomain like links.yourbrand.com rather than your root domain, pointing at the hostname the shortener gives you. The IETF's original DNS specification, RFC 1035, defines exactly how CNAME records work: they're an alias telling the internet "this name is really that other name, go look there instead." Every custom-domain shortener on the market, hosted or self-hosted, is built on this 40-year-old standard.

Once the CNAME is in place, you need a valid SSL certificate for that subdomain, or browsers will flag every short link as insecure before the redirect even fires. Hosted services usually issue this automatically through Let's Encrypt, the free certificate authority that also underpins most self-hosted setups. If you're running your own server, you'll issue that certificate yourself — it takes one command, not a support ticket.

1 CNAME record. That's the entire DNS footprint required to put your brand on every short link you create.

DNS changes propagate at different speeds depending on your registrar and the TTL (time-to-live) value on the record, but plan for up to 48 hours before you can guarantee every resolver worldwide sees the update, even though most see it within minutes.

The Real Cost of Custom Domains on Hosted Plans

Survey the pricing pages of hosted shorteners competing for this exact search term and a pattern shows up fast: custom domain support rarely appears on the free or entry-level plan, and when it does unlock, it's usually capped — one domain included, additional domains billed separately, with no path to unlimited without jumping to an enterprise tier.

Model Custom domain included? Typical domain cap What happens if you cancel
Free hosted shortener Rarely 0 Links already broken under a Bitly-style prefix
Paid hosted shortener Usually, mid-tier up 1–5, extra domains cost more Redirects stop resolving immediately
Self-hosted shortener Always, no extra fee Unlimited Nothing — the server keeps running

That last column is the one competitors' comparison pages tend to skip, because it's not a feature difference, it's a dependency difference. You can have identical custom domain functionality on two plans and still face completely different risk if the vendor relationship ends.

Self-Hosted vs. Hosted: Who Actually Controls the Domain

Two people shaking hands over a desk with a small padlock placed between them.

With a hosted shortener, "custom domain" means you're borrowing their redirect engine. With a self-hosted shortener, the redirect engine is a piece of software sitting on a server you pay for, and the custom domain points directly at that server — no intermediary company in the chain at all. If you want to compare the open-source options that make this possible without buying a commercial license, this comparison of open-source link shortener trade-offs lays out what each one actually requires in server skill and maintenance time.

The trade-off is real and worth saying plainly: self-hosting means you're responsible for uptime, backups, and security patches that a hosted vendor would otherwise handle. If you don't want to touch a terminal, a well-run hosted service is a legitimate choice. But if you're already paying a recurring fee specifically to avoid vendor lock-in on your own branded domain, you've picked the harder path for a reason that a subscription doesn't actually solve — you're still locked in, just to a nicer dashboard.

Setting Up a Custom Domain: CNAME, SSL, and the Steps People Skip

Whether you're configuring a hosted plan or your own server, the sequence is close to identical:

  1. Choose a subdomain, not your root domain. go.yourbrand.com or links.yourbrand.com keeps your main site's DNS untouched and isolates risk if the shortener misbehaves.
  2. Add the CNAME record at your DNS provider. Point it at the hostname your shortener (hosted or self-hosted) specifies.
  3. Issue or confirm the SSL certificate for that exact subdomain before you publish a single link.
  4. Lower the TTL on the record 24 hours before go-live if you're migrating from an existing shortener, so the eventual cutover resolves fast instead of leaving stale links serving the old destination for two days.
  5. Test a redirect end to end, including on mobile data, not just on your office Wi-Fi where cached DNS can hide a broken config.

People skip step four constantly. If your current TTL is set to 24 hours and you don't lower it in advance, your migration window stretches to a full day of inconsistent behavior — some visitors get the new redirect, some get the old one, depending purely on when their resolver last cached the record.

When a Custom Domain Isn't Enough: Protection, Testing, and QR Codes

A domain you control is the foundation, but it's not the whole feature set a growing link program actually needs. If you're sharing sensitive destinations — investor decks, internal docs, client proposals — look for password-protected links so the custom domain doesn't just look branded, it actually gates who gets through.

If you're running paid traffic or testing landing pages, confirm the shortener supports A/B split testing on individual links, so one short URL can route a percentage of clicks to variant B without you managing two separate links in your ad platform. And if your short links end up on packaging, signage, or print, a plain black-and-white QR code undersells the brand you just paid to put on that domain — styled, logo-embedded QR code generators solve that specific gap, and it's worth comparing the free tools fairly before assuming you need a paid add-on for it.

Five Mistakes That Break Custom Domain Redirects

  • Pointing the CNAME at an apex domain. DNS standards generally don't allow a CNAME record on a root domain alongside other required records (like MX for email) — use a subdomain and avoid the conflict entirely.
  • Forgetting the SSL certificate renews automatically. Let's Encrypt certificates expire every 90 days; if your self-hosted setup doesn't auto-renew, links silently start throwing security warnings three months after launch.
  • Mixing 301 and 302 redirects without meaning to. Google's own guidance on redirects explains that a 301 tells search engines and browsers the move is permanent, while a 302 signals temporary — using the wrong one for a permanent brand domain can affect how search engines treat the destination page.
  • Skipping the TTL lowering step before a migration, leaving a mixed-resolution window where different visitors land on different destinations for up to 48 hours.
  • Assuming the domain registrar and the DNS host are the same company. ICANN requires registrars to let you manage DNS yourself or delegate it, but plenty of people edit records in the wrong dashboard and wonder why nothing changes.

Link rot isn't theoretical, either. Pew Research Center found that 38% of webpages from 2013 are no longer accessible today — a reminder that whatever system sits behind your custom domain needs to survive longer than the average web service does.

38%. That's the share of 2013-era webpages Pew Research Center found gone by 2024 — the baseline risk any shortener you pick has to beat.

A pair of hands holding a single brass key in an office.

Kortli is a self-hosted link shortener you install on your own Linux server for a one-time payment, not a recurring plan. Custom domains come with no per-domain fee and no cap — point as many branded subdomains at it as you need, because the redirect logic lives on your server, not ours. It also includes password-protected links, A/B split testing, logo-embedded QR codes, and click analytics that never leave your infrastructure.

The honest caveat: you'll need basic comfort with a Linux server and DNS, the same comfort any self-hosted tool assumes. If you'd rather never touch a terminal, a hosted plan with a monthly fee is the more forgiving choice — just go in knowing what happens to your links the day you stop paying it. Check the spec sheet on our pricing page against your actual domain count before you decide either way.

Frequently Asked Questions

Can I use a custom domain with a free URL shortener plan?

Almost never. Most hosted shorteners restrict custom domain support to paid tiers, often the second or third pricing level, because the feature requires them to issue an SSL certificate and manage DNS routing on your behalf. Free plans typically only offer the service's own shared domain.

Do I need a new domain, or can I use a subdomain of my existing website?

A subdomain is the standard approach — something like go.yourbrand.com or links.yourbrand.com — because it isolates the DNS change from your main site's root domain records, including email (MX) configuration. You rarely need to buy a separate domain just for short links.

How long does it take for a custom domain to start working after I add the DNS record?

The CNAME change itself can take effect within minutes, but full global propagation depends on your TTL setting and can take up to 48 hours. Lowering the TTL a day before a planned migration shortens that window considerably.

In almost every case, the redirects stop resolving immediately, even though you still own the domain name itself at your registrar. The redirect rules lived on the vendor's server, not yours, so canceling removes the thing actually doing the work.

Is self-hosting a URL shortener harder than using a hosted service?

It requires comfort with a Linux server, DNS records, and basic SSL certificate management — skills a hosted plan abstracts away for you. In exchange, you avoid per-domain fees, domain caps, and the risk of links breaking if a vendor changes its pricing or shuts down.

Yes, the two features are independent — a password-protected link can sit on your branded custom domain exactly like any other short link. Not every shortener supports both together, though, so it's worth confirming before you commit to a platform.

Sources

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *