Custom scan domain for qr prints
SmartQRCode editorial · Updated October 2026
A custom scan domain for qr is a hostname you own that the symbol encodes instead of smart-qrcode.com. That choice is baked into pixels at create time. Print only after the host is active. DNS that later drifts can 404 a carton that still looks perfect. Canva remains the one-off when you will never edit or count.
Why a custom scan domain for qr is printed in
The hostname is encoded at create time. Use an active host only. A pending dns status is not a print file. A cross-tenant scan 404 is the isolation check.
The generator writes a base URL into the image and into the stored target. That string is not a caption. It is the payload the camera will open for the life of the print. A custom scan domain for qr therefore has to be chosen before the press, the way you choose the destination itself.
Only an active host is eligible for that encoding. Pending DNS, a TXT challenge on another Vercel account, or a failed provision must not reach the plate. A lookup that cannot confirm the host should refuse rather than fall back to the platform. Fallback would hand you a file that looks branded in the wizard and encodes smart-qrcode.com in the modules.
Redirect types hop with a 302 so later destination edits still reach phones that have scanned before. The host in the modules does not move with those edits. You can change https://example.com/spring to /autumn without reprinting. You cannot change qr.brand.com to qr.brand.io without reprinting.
Paid options are $1.99, $29, $97, and $197. We do not sell an unpaid tier. Use the website URL generator for links, codes that never expire when the pack has a long shelf life, and tracked QR codes when each SKU needs its own series. Product launch placements are the usual campaign shape.
How to attach a hostname before the press run
Treat the host like a colour that cannot be reprinted cheaply.
- Pick a hostname you control, typically a subdomain such as qr.brand.com rather than the public marketing apex, unless you intend the apex to serve only scans.
- Attach it and wait for the status to read active, including certificates. The custom scan domain and SSL article names the intermediate states.
- Create the codes against that host. Confirm the encoded URL in the file, not in a browser tab of the wizard.
- Export SVG or a 300 dpi PNG or PDF at the final size. Do not screenshot /qr-preview.
- Keep four modules of quiet zone. Size the symbol at least 2 cm across for a 30 cm phone distance; larger for aisle or pavement reads.
- Proof on the real substrate. Scan with a phone on cellular, not on the office Wi-Fi that already knows the destination.
- Pause, scan, and read the status page on the customer host. Release pause before the ship date.
- Leave the old platform codes running if they are already in the field. They still resolve on smart-qrcode.com. That is intentional for existing print.
The sibling custom domain QR code host covers how the host object itself behaves once scans start.
Can you move an already-printed code onto a new host
You cannot. The camera does not consult a dashboard for the hostname. It opens whatever string is in the modules. Updating DNS for a new name leaves the old name in ink. Either keep the old host resolving for as long as those objects exist, or reprint.
This is the same permanence as any hosted URL, only more visible, because guests read the name in the padlock. White-label scanning can hide our chrome on the platform host. It cannot rename a URL that is already printed. See white label qr codes.
A provider outage still stops both names. F91 is unchanged by cosmetics. If the object must survive with no resolver, it has to be a static payload, which for this product means Wi-Fi only, or a file from Canva that encodes the final URL in the modules and cannot be edited later.
What the host gate refuses to serve
A hostname attached to the project would otherwise serve every route: marketing, create, dashboard, even operator login. The gate allowlists scan prefixes and returns 404 for the rest, without writing a session cookie on the way past. That is how a custom scan domain for qr stays a scan host instead of a clone of the site.
Unknown hosts fail closed. A name that reaches the app with no row is not treated as ours. Platform hosts are classified from a static list so a database blip cannot 404 the public site.
Cross-tenant protection is the other refusal. A short code that belongs to another account 404s on your host. Your codes 404 on theirs. A code with no domain still resolves on the platform host, which is how older print keeps working.
Domain mistakes that 404 a live pack
Printing during pending_dns encodes hope. The phone will request a host that is not serving scans yet. Wait for active.
Printing, then removing DNS, turns an active host into misconfigured. The row may still occupy an allowance slot because the hostname remains on the project. Cartons in shops start failing while the art still looks correct. Restore DNS or treat it as a reprint.
Using another tenant's host in a test scan is supposed to 404. If it 302s, something is wrong with isolation, not with your art.
Exporting the preview, or scaling a 400 px PNG to a 20 cm poster, interpolates grey into modules. The host can be perfect and the camera still fails. Send vector or a high-resolution raster at the real millimetre size.
What a sixty-second host cache means on launch day
Host lookups are cached per instance for about sixty seconds, including negative results. A name you just attached can 404 for up to a minute on an instance that already decided it was unknown. A name you just retired can keep serving for the same window. The API invalidates on the instance you talked to. Other instances catch up on their own clocks. That is why a launch war-room should scan from a fresh cellular connection after the status is active, then wait a minute and scan again from a second phone.
Do not treat the first successful scan in the office as the all-clear. Office Wi-Fi may already have a cached destination, and the office instance may be the one you just wrote. A shopper in another region hits a different instance. The print is global. The cache is not.
If a lookup fails closed, the app would rather 404 than serve the marketing site on a customer hostname. That refusal is louder than a silent fallback to smart-qrcode.com, which would encode the wrong host into the next create. Prefer a loud miss on launch morning over a quiet wrong URL in a million cartons.
Keep a written note of the encoded URL copied from the download, not from a typed memory of the hostname. People type qr.brand.com and encode qr.brand.co. The difference is one letter and a reprint.
When the platform URL is the cheaper print
If shoppers do not care whose name is in the padlock, encoding smart-qrcode.com is the default hosted path. You still get destination edits and country plus device counts. You skip DNS, certificates, and the risk of a misconfigured host after a registrar change.
If they also do not need edits or counts, skip hosting. A Canva one-off or another free static generator writes the final URL into the modules. No provider has to stay up. No custom scan domain for qr is involved. Size it, keep the quiet zone, and print.
The expensive mistake is attaching a host for a one-night poster, or skipping a host for a five-year carton that must never show our name. Match the object life to the encoding, then pick the hostname.
Questions this raises
No. The modules store the URL chosen at create time. Pointing DNS at a new hostname does not rewrite ink. You reprint, or you leave the old host resolving.
On a customer hostname the app answers scan routes and 404s marketing, create, and account paths. That stop is what keeps qr.brand.com from becoming a copy of the whole site.
When brand-on-the-padlock does not matter and a Canva static file is too rigid. Encoding smart-qrcode.com is the default hosted path. Skip a custom scan domain for qr if you will never attach DNS.
The row exists and the hostname is registered, but DNS is not yet correct. Do not export the live payload. Wait until the host is active.
No. A code whose domain does not match the request host 404s. Both directions are checked so one company cannot 302 through another company certificate.
Keep going
The tools and playbooks this post refers to, one click away.
Make the code this post is about
$1.99 for 7 days, then a paid plan. Pick a type, brand it, and edit the destination whenever you like, even after it is printed.