Custom domains & DNS

Custom domains increase trust — recipients see your brand in the link bar instead of a generic vendor host.

#Shared vs custom domains

Every organisation can create codes on the shared host immediately. Custom domains require plan entitlement and DNS verification.

#Add a custom domain

1. Open Domains in the dashboard.
2. Enter the hostname (usually a subdomain like go.example.com).
3. QR Hero shows the required CNAME target — create that record at your DNS provider.
4. Wait for verification. SSL certificates provision automatically via Cloudflare custom hostnames.

#DNS walkthrough

Typical steps at Cloudflare, Route53, or your registrar:

1. Create a CNAME record: go → the target shown in QR Hero (often a Cloudflare proxy hostname).
2. Disable conflicting A records on the same name.
3. If using Cloudflare, enable the orange cloud (proxied) so origin certificates validate.

Verification can take up to an hour depending on TTL. The domains table shows pending, active, or error states.

#Primary domain

Mark one verified domain as primary so new codes default to it in the editor dropdown. You can still pick other active domains per code.

#Troubleshooting

• SSL errors — confirm the hostname is proxied through Cloudflare when using Origin CA certificates.
• 404 on scan — ensure the redirect cache was rebuilt after activation; run a test scan and check code slug includes the organisation prefix.
• Empty domain dropdown — a fallback domain row must exist for your organisation; contact support if missing after migration.

#Remove a domain

Deleting a domain does not delete existing codes — they fall back to the shared host on next edit unless reassigned. Plan comms before removing production hostnames.