Custom Domains
Instead of tracenull.cc/ab3x, your links can look like go.yourdomain.com/ab3x.
TraceNull handles the TLS certificate, the redirect logic, and the privacy layer — you just point your DNS.
How it works
When someone clicks a link on your custom domain, the request flows through TraceNull's infrastructure — identical to how tracenull.cc links work, just with your domain name on the front.
Technically: your domain's CNAME record points to tracenull.cc. When a request arrives, Caddy (our reverse proxy) recognizes the domain and routes it to TraceNull. The TLS certificate for your domain is obtained automatically via Let's Encrypt — no manual cert management needed.
The privacy protection is identical to tracenull.cc links: Referrer-Policy: no-referrer is set on every response, so the destination site never sees your domain or your visitor's origin.
tracenull.cc/ab3x and yourdomain.com/ab3x work simultaneously. The same slug resolves correctly from either domain. Short links are not domain-locked.Setup Guide
Add the domain in your Dashboard
Go to Dashboard → Custom Domains → type your domain (e.g. go.yourdomain.com) and click Add Domain.
You'll receive a verification token that looks like:
tracenull-verify-a1b2c3d4e5f6...
Add two DNS records
Log into your domain registrar (Cloudflare, Namecheap, IONOS, etc.) and add these two records. Replace go.yourdomain.com with your actual subdomain or root domain.
| Type | Name / Host | Value / Points to | TTL |
|---|---|---|---|
| CNAME | go (or @ for root) | tracenull.cc | Auto / 3600 |
| TXT | go (same name as CNAME) | tracenull-verify-your_token | Auto / 3600 |
ALIAS or ANAME record instead (same value: tracenull.cc). Cloudflare users: enable Proxy status OFF (grey cloud) for the CNAME, or use a subdomain like go. or links. to avoid conflicts with your main site.
Wait for DNS to propagate
DNS changes can take a few minutes to 48 hours depending on your registrar and TTL setting. Most registrars apply changes within 5–30 minutes.
You can check propagation using a tool like dig go.yourdomain.com CNAME in a terminal, or an online DNS checker.
Verify in Dashboard
Once DNS has propagated, go back to Dashboard → Custom Domains → click Verify DNS next to your domain.
TraceNull checks the TXT record automatically. If the record is found, the domain is marked as Verified and immediately active.
yourdomain.com/slug in the dashboard result. The TLS certificate for your domain is issued on the first request — there's a 1–3 second delay on that very first visit, then it's cached permanently.Registrar-specific Instructions
Cloudflare
DNS → Add record → Type: CNAME, Name: go, Target: tracenull.cc, Proxy status: DNS only (grey cloud). Then add a TXT record with the same name and your verification token as the content.
IONOS (1&1)
Domain Center → Manage DNS → Add record → Type: CNAME, Host name: go, Points to: tracenull.cc. (trailing dot required). TXT record: same host name, value: your verification token.
Namecheap
Advanced DNS → Add new record → Type: CNAME, Host: go, Value: tracenull.cc. TXT record: Host: go, Value: your verification token.
Strato
Domain → DNS-Einstellungen → Subdomain anlegen → Typ: CNAME, Ziel: tracenull.cc. TXT-Eintrag gleicher Subdomain mit Verification-Token als Inhalt.
All-Inkl / INWX / Hetzner DNS
Same pattern: CNAME pointing to tracenull.cc + TXT with the verification token on the same hostname. If the panel asks for a trailing dot on the CNAME target, add it: tracenull.cc.
Troubleshooting
dig TXT go.yourdomain.com in your terminal or using Google's DNS checker. The output should contain your full verification token.dig go.yourdomain.com CNAME returns tracenull.cc, then try again — the certificate will be issued within seconds.links.yourdomain.com or go.yourdomain.com). Cloudflare and some others support a special CNAME flattening feature that allows this — check your registrar's documentation.FAQ
go. or links. so it doesn't interfere with your main website.tracenull.cc. The custom domain URL just stops resolving — the underlying links are unaffected.