The Custom Domain Service maps your domain (for example explorer.yourchain.example) to your OpenScan.AI deployment and keeps TLS certificates issued and renewed — so users reach the explorer on your brand’s domain, not ours.
How It Works
- You create a DNS record pointing your domain at the deployment’s ingress address.
- The service detects the domain, verifies DNS, and provisions a certificate automatically.
- Incoming requests for your domain are routed to your explorer instance with your branding applied.
Setup
- Choose the domain — a dedicated subdomain is recommended.
- Create the DNS record:
explorer.yourchain.example. CNAME ingress.openscan.ai.(Self-hosted deployments point at their own reverse proxy instead — see TLS / HTTPS Setup.)
- Register the domain in your deployment configuration or with the OpenScan.AI team for hosted instances.
- Verify — once DNS propagates, the certificate is issued and
https://explorer.yourchain.exampleserves your explorer.
Behavior and Limits
- One primary domain per explorer instance; additional aliases can redirect to it.
- Certificate issuance and renewal are automatic; check the service’s logs if a domain shows certificate errors.
- DNS changes can take minutes to hours to propagate — plan launches accordingly.
Troubleshooting
| Symptom | Likely cause |
|---|---|
| Certificate error | DNS not pointing at the ingress yet, or CAA records blocking issuance |
| Default branding shown | Domain not registered in deployment configuration |
| Intermittent failures | Conflicting A and CNAME records on the same name |
For hosted instances, the OpenScan.AI team handles this end-to-end — just tell us the domain via the contact form.