Skip to documentation
Link 2 Link / Docs
Documentation home
Browse documentation

Connect & automate

Custom domains

Connect a hostname you control, prove ownership and wait for active HTTPS before sharing.

Current product guide · Reviewed October 28, 2026

Start with a dedicated subdomain

Use a dedicated hostname such as go.example.com. Add the hostname only—no https://, path or port—in Domains & integrations. Choose the same personal/workspace scope as the links it will serve. You need write access to that scope and control of its DNS.

Publish the records shown in your dashboard

  1. Add the hostname. Copy the ownership TXT record shown for _li2li-verification.go.example.com, with its exact li2li=… value.
  2. Publish it at your DNS provider. Some providers expect a relative record name; check the resulting full hostname to avoid adding your domain twice.
  3. Request verification/onboarding in the dashboard. Add the displayed routing CNAME and any additional certificate or provider ownership records exactly as supplied.
  4. Keep the required records in place and wait for both hostname and SSL status to become active. Li2.li does not edit your DNS automatically.

The CNAME destination and certificate records are installation-specific. Always copy the current dashboard values; do not copy another customer’s TXT token. DNS-only records are the straightforward choice where your DNS provider offers a proxy switch.

When the domain can serve links

TXT proof alone is not sufficient. Routing requires current ownership, active provider hostname and SSL status, a fresh status check and an eligible registrant with write access to the link scope. A personal hostname cannot serve another user’s links. A workspace hostname cannot serve a different workspace’s links.

The current checks require ownership verification within 30 days and provider status checked within 30 minutes. Background reconciliation maintains status; if it cannot confirm eligibility, routing fails closed rather than serving an unverified domain. No certificate issuance-time guarantee is made.

Troubleshoot pending or unavailable domains

SymptomWhat to check
Ownership proof missingCheck full TXT name and exact value, authoritative DNS and propagation. Keep the proof record in place.
CNAME not recognizedCheck the published target and whether your provider flattened or proxied the record. Use the displayed target exactly.
Hostname active, SSL pendingReview the additional certificate records. DNS ownership and certificate readiness are separate checks.
Previously active, now unavailableCheck DNS changes, workspace membership, account eligibility and dashboard freshness/error state.
Already verified elsewhere or review requiredContact support. Do not repeatedly delete/re-add or try to claim another account’s hostname.
Quota/provider errorWait for the displayed retry/status or contact support. There is no guarantee that repeated clicks accelerate provisioning.

Remove or move a hostname

Removing a domain disables application routing immediately and queues provider deprovisioning where necessary. Remove the DNS records at your provider separately. Existing printed URLs on that hostname will stop working. Domain removal does not delete the underlying links; use the default sharing address if the links remain eligible. Ownership transfer between scopes requires review rather than a blind overwrite.

Still need a hand?

Use Help & support in your dashboard or support@li2.li. Share the action and a sanitized error, never a password, token or private reset link.