Skip to main content
A custom domain replaces the standard Biqli hostname with a domain you control, such as go.example.com. It gives links and Biolinks a branded, recognizable URL. Connecting a domain has two parts. Biqli first confirms that it is available inside Biqli, then gives you the DNS records to add at your DNS provider. After DNS is detected, Biqli provisions HTTPS automatically. A domain moves through pending DNS, pending SSL, provisioning SSL, active, or SSL failed states. Do not publish its links until it is active.
Custom domains dashboard placeholder

​
Domain lifecycle

  1. Biqli checks that the hostname is available inside the application.
  2. The workspace creates the domain and receives exact DNS instructions.
  3. You add the records at the authoritative DNS provider.
  4. Biqli detects DNS and begins HTTPS certificate provisioning.
  5. The domain becomes active and can serve public resources.
Domain availability in Biqli is different from domain registration. You must already own or control DNS for the hostname. Biqli does not purchase it from a registrar.

​
What the domain can control

An active custom domain can be selected for supported short links and Biolinks. Domain settings also control behavior for the bare hostname, expired URLs, and unknown paths, plus a supported custom favicon. Do not publish URLs while DNS or SSL is pending. Test the hostname over HTTPS and test at least one resource before replacing an existing campaign domain.