← Back to workspace · All guides
Use a dedicated subdomain such as go.example.com for branded QR links. Domain registration and DNS hosting remain with your own provider.
Use Pro and a domain you control. You need permission to edit its DNS records. Do not replace your main website’s DNS records.
Check current plans and signup offersOpen Settings & billing and the custom-domain section. Enter a subdomain such as go.example.com, then connect it.
At your DNS provider, create the TXT record shown by FutureQR: name _futureqr-verify on your subdomain, value futureqr-verify= followed by the token for your request. The token is unique to your account and this request, so it cannot be reused by anyone else. Choose Check again. A request ends after 3 days without the record and never blocks the domain’s real owner.
Once verified, create the CNAME record shown by FutureQR. Its target is customers.futureqr.app. Use the exact host and value displayed; remove conflicting records only for that dedicated subdomain. Choose Check again. Nothing is served on the domain, and you should not distribute the address, until the dashboard confirms the hostname and certificate are live. DNS propagation can take time.
Check that new downloads and exported code links use your branded hostname, then scan a downloaded QR without signing in. Keep the TXT record in place: FutureQR checks it daily, emails you if it goes missing, and pauses the domain only after 3 days of failed checks, until the record is back and you choose Check again. A DNS outage on our side never counts against you.
Read the domain-removal warning and type the required hostname to confirm. Existing printed QR images retain their encoded hostname; changing the dashboard does not rewrite paper. Keep the domain and DNS functioning while those prints remain in use.
The dashboard reports the domain live, HTTPS works and a branded QR opens the correct destination.
If the TXT check says the record was not found, compare its exact name and value with your provider and wait a few minutes. If verification is pending, compare the exact CNAME with your provider and use Check again. If the domain is paused, put the TXT record back and use Check again. Do not treat a pending DNS record as a live certificate. If a printed branded code fails, inspect its encoded hostname first.