DocsBuild07
Branded subdomains, your name on every link.
Publish paid-plan links at a single-level address such as brand.lixrl.com/go while keeping a canonical lixrl.com fallback.
Availability and limits
| Plan | Branded subdomains |
|---|---|
| Free | Cannot claim or activate subdomains |
| Pro | One branded subdomain |
| Business | Three branded subdomains |
| Enterprise | Arranged separately |
Labels are 3–32 lowercase letters, numbers, or interior hyphens with no additional dots.
Setup
- Open Dashboard → Subdomains.
- Claim an available label. Claims are atomic; another account cannot hold the same live hostname.
- Select Verify route. Lixrl checks wildcard DNS, TLS, the redirect Worker, and the claim token over HTTPS.
- Make the verified hostname your default or map individual existing links to branded codes.
No DNS changes
API workflow
# Claim
curl -X POST https://lixrl.com/api/subdomains \
-H "Authorization: Bearer elu_YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"label":"brand"}'
# Verify wildcard routing and TLS
curl -X POST https://lixrl.com/api/subdomains/42/verify \
-H "Authorization: Bearer elu_YOUR_API_KEY"
# Map an owned fallback link to a domain-specific code
curl -X POST https://lixrl.com/api/subdomains/42/links \
-H "Authorization: Bearer elu_YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url_code":"a1b2c3","short_code":"launch"}'Routing and isolation
Branded links are resolved by hostname and code. The same code can belong to different verified subdomains. D1 checks ownership, plan status, domain state, and link state before a cached redirect is used; cache keys include both the domain ID and its revision.
Destination safety checks, expiry, bot filtering, click analytics, QR destinations, and API ownership rules remain the same as canonical links.
Removal, downgrade, and recovery
Removing a claim or losing the paid entitlement disables branded routing and increments its route revision immediately. Canonical lixrl.com/code links continue to work. A renewed account must verify and reactivate a suspended claim explicitly.
A failed verification normally means wildcard DNS, certificate issuance, or the router deployment is not ready. Wait for propagation, retry verification, and check the production deployment logs. Removed names require a fresh claim and verification before reuse.