Custom domain is not working
If your custom domain is not working, check that you are using a dedicated subdomain. QRSurge expects a CNAME record pointing to domains.qrsurge.com.
Check the domain in QRSurge
Open Custom domains and review the domain status:
VerifyingConnectedUnreachableDisconnected
If the domain is disconnected, reconnect it or choose a different connected domain for new dynamic QR codes.
Use a subdomain, not your main website domain
QRSurge currently supports custom subdomains, such as go.yourbrand.com, qr.yourbrand.com, or links.yourbrand.com.
Do not use your main website domain, such as yourbrand.com, because it most likely already points to your website. You can use www.yourbrand.com only if it is not already pointing to a live page.
Check the DNS record type
For subdomains such as go.yourbrand.com or qr.yourbrand.com, add a CNAME record:
- Record type - CNAME
- Name / Host - the subdomain label, such as
go - Value / Target -
domains.qrsurge.com - Proxy status - DNS only
Some DNS providers expect the full hostname, such as go.yourbrand.com, in the Name / Host field.
Turn off proxying
If your DNS provider supports proxying, set the QRSurge DNS record to DNS-only. Proxied records can prevent QRSurge from verifying and serving the custom domain correctly.
In Cloudflare, this usually means the cloud should be gray, not orange, for the QRSurge record.
Remove conflicting records
Duplicate or conflicting DNS records can keep the domain from resolving correctly. Check for existing A, AAAA, or CNAME records using the same host.
Only one service should control the subdomain you want QRSurge to use.
Wait for DNS and SSL
DNS changes can work quickly, but they may take 24-48 hours to fully propagate. SSL setup can also take time after DNS is correct.
Use the refresh or verification controls in Custom domains after updating DNS.