A custom domain does two jobs. It puts your brand in the link people see, and it is what makes CTA overlays possible at all — the overlay is served from the link's own domain, so that domain has to be yours.
Step 1 — add the domain in Visib
Go to Customization in the dashboard and type the domain you want to use, for example go.yourbrand.com or yourbrand.com. Visib then shows you the exact record to create.
Step 2 — create one DNS record
Which record depends on whether you are using a root domain or a subdomain.
| Domain | Type | Name | Value |
|---|---|---|---|
Root — yourbrand.com | A | @ | 76.76.21.21 |
Subdomain — go.yourbrand.com | CNAME | go | cname.visib.link |
Cloudflare
DNS → Records → Add record. Create the record from the table, then set the proxy status to DNS only (grey cloud). With the orange cloud on, Cloudflare terminates TLS itself and the certificate cannot be issued.
GoDaddy
My Products → DNS → Add. Choose the type, put go (or @) in Name and the value from the table. Leave TTL on the default.
Namecheap
Domain List → Manage → Advanced DNS → Add New Record. Namecheap calls the name field Host: go for a subdomain, @ for the root.
Vercel, Netlify, Route 53, Google Domains
Same record, different form. Every one of these accepts a plain A or CNAME entry — pick the type, enter the name and the value, save.
Step 3 — verify
Back in Customization, press Verify. Visib checks two separate things: that the domain points at us, and that the DNS is actually resolving live. Both have to pass before the domain goes green, and SSL is issued right after.
When it does not work
- Verify keeps failing. DNS has not propagated yet. Check with
dig go.yourbrand.comand try again in a few minutes. - Cloudflare users: the orange cloud is on. Switch the record to DNS only.
- An old record is in the way. A previous A, CNAME or ALIAS on the same name wins. Delete it first.
- The certificate is stuck. A CAA record on the domain can block issuance. Either remove it or add one that allows Let's Encrypt.
